SK0-003 · Question #451
A new server must be configured to provide fault tolerant connectivity to the DMZ and the backend database. Which of the following is the MOST cost effective way to accomplish this?
The correct answer is D. A total of four NICs: two NICs for the DMZ and two NICs for the backend database.. To provide fault-tolerant connectivity to two distinct networks (DMZ and database) in a cost-effective manner, the server should have two separate network interfaces for each network, totaling four NICs.
Question
A new server must be configured to provide fault tolerant connectivity to the DMZ and the backend database. Which of the following is the MOST cost effective way to accomplish this?
Options
- AA total of six NICs: two pairs of teamed NICs for the DMZ and two NICs for the backend database.
- BOne NIC can be configured with VLANs for the DMZ and backend database.
- CA total of eight NICs to be teamed with the appropriate VLANs configured for the DMZ and backend database.
- DA total of four NICs: two NICs for the DMZ and two NICs for the backend database.
How the community answered
(36 responses)- A14% (5)
- B6% (2)
- C25% (9)
- D56% (20)
Why each option
To provide fault-tolerant connectivity to two distinct networks (DMZ and database) in a cost-effective manner, the server should have two separate network interfaces for each network, totaling four NICs.
Six NICs (two pairs of teamed NICs for DMZ, two for database) is excessive if only fault tolerance is required for two connections, increasing cost and complexity without added benefit over four NICs.
One NIC configured with VLANs is not fault tolerant, as the single NIC represents a single point of failure for all connectivity.
Eight NICs (two teamed sets of four) is overly complex and expensive for simple fault tolerance to two distinct networks, providing more redundancy than necessary.
Using two NICs for the DMZ and two NICs for the backend database provides fault tolerance for each connection via NIC teaming or bonding, ensuring connectivity even if one NIC fails for either segment. This configuration is a common and cost-effective approach that avoids unnecessary complexity or insufficient single points of failure.
Concept tested: Network fault tolerance and cost-effective NIC configuration
Source: https://learn.microsoft.com/en-us/windows-server/networking/technologies/nic-teaming/nic-teaming
Topics
Community Discussion
No community discussion yet for this question.