A network architect wants a server to have the ability to retain network availability even if one of the network switches it is connected to goes down. Which of the following should the architect implement on the server to achieve this goal?
The network architect should implement NIC teaming on the server to achieve network availability even if one of the network switches it is connected to goes down. NIC teaming is the process of aggregating multiple network connections into a single virtual interface for redundancy and increased throughput. If one of the network switches goes down, the server can still use the other network connections to maintain network availability. RAID provides redundancy for storage, not for network availability. UPS provides power backup to devices in case of power outages. Load balancing distributes incoming traffic across multiple servers to optimize resource utilization, but it does not guarantee network availability in case of switch failure.
- NIC teaming allows the server to communicate with multiple switches using one logical port, thus achieving redundancy.
- RAID provides redundancy for storage systems, not network systems like switches and routers.
- Load balancing achieves load balancing not redundancy in case of an outage.
- UPS provides backup power to connected devices in the event of a power outage. No power outage was mentioned, UPS provides fault tolerance rather than redundancy.
D. Load Balancing is wrong because the question ask for what should be implemented at the SERVER and not SWITCH. Load balancing at Switch (i.e. having multiple switches) makes sense to increase redundancy at the switch level, and this has already been stated in the question. Load Balancing at the server level requires more than one server (which is not the case here) to distribute processing load and to improve performance, and to provide server redundancy.
NIC teaming is the right answer for this scenario as the question is asking what can be implemented on the single server. NIC teaming allows multiple network interface cards to be "Teamed" and each interface card is connected to different switches. This allows for switch redundancy which is what the question is asking for.
If a server has multiple network interface cards (NICs) connecting it to a switch or router, it will have multiple addresses, one for each NIC. NIC teaming is an alternative means of connecting used by servers that have multiple network interface cards and wish to enjoy the benefits of load balancing, fault tolerance, and failover without requiring added infrastructure to do it. When NIC teaming is used, the OS combines the NICs into a virtual NIC from the OS perspective. If one or more of the connections have traffic issues or connectivity issues, the other NICs can carry the load. Using NIC teaming allows your server to have redundancy and increased bandwidth, even in the event any of your physical adapters or cabling fails.
EXAM TIP NIC teaming groups multiple NICs together to form a logical
network device called a bond. This provides for load balancing and fault tolerance"
-All-in-One Security+ SY0-601 Exam Guide Sixth Edition by Conklin & White
A load balancer acts as the “traffic cop” sitting in front of your servers and routing client requests across all servers capable of fulfilling those requests in a manner that maximizes speed and capacity utilization and ensures that no one server is overworked, which could degrade performance. If a single server goes down, the load balancer redirects traffic to the remaining online servers. When a new server is added to the server group, the load balancer automatically starts to send requests to it.
The network architect should implement NIC teaming on the server to achieve the goal of retaining network availability even if one of the network switches it is connected to goes down. NIC teaming, also known as network interface card bonding or link aggregation, is the practice of combining multiple network connections to increase bandwidth and provide redundancy. By configuring NIC teaming on the server, the architect can ensure that if one of the network switches fails, the server will still have a network connection through the other switch.
>>>>>C<<<<<<
To achieve the goal of retaining network availability even if one of the network switches it is connected to goes down, the network architect should implement "NIC teaming" on the server. NIC teaming is a technique that allows multiple network interface cards (NICs) to be combined into a single logical interface, providing redundancy and load balancing. If one of the switches goes down, the server can continue to communicate through the other NICs, ensuring network availability.
-C NIC Teaming is correct
The network architect should implement NIC teaming on the server to achieve the goal of retaining network availability even if one of the network switches it is connected to goes down. NIC teaming is a technique that involves combining two or more network interfaces into a single logical interface. This provides redundancy and fault tolerance in case one of the network interfaces or switches fails. If one switch goes down, the server can still communicate over the other network interface, ensuring network availability.
upvoted 3 times
...
This section is not available anymore. Please use the main Exam Page.SY0-601 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
ApplebeesWaiter1122
Highly Voted 2 years, 1 month agoswiggharo
Highly Voted 2 years, 1 month agoAbdullahMohammad251
Most Recent 1 year, 1 month agoMalkhofash
1 year, 6 months agocyberPunk28
1 year, 6 months agoje123
1 year, 10 months agoLeonardSnart
2 years agosyimir
2 years, 1 month agofouserd
2 years, 1 month agoif10w
2 years, 1 month agomouettespaghetti
2 years, 1 month ago