CV0-003 · Question #816
An organization has decided to implement the following network segregation: Below is a configuration of an application server: The application team is unable to establish connectivity to another serve
The correct answer is A. Incorrect routing configuration. When a server has multiple NICs on different network segments and cannot reach a host on a separate subnet, the routing table is the most likely misconfiguration because it governs which interface handles traffic to each destination.
Question
An organization has decided to implement the following network segregation:
Below is a configuration of an application server:
The application team is unable to establish connectivity to another server, which has the IP address 10.10.10.180. Which of the following is the MOST likely reason for the issue?
Exhibit
Options
- AIncorrect routing configuration
- BIncorrect NIC1 configuration
- CIncorrect gateway in NIC 1
- DIncorrect subnet mask in NIC2
How the community answered
(58 responses)- A81% (47)
- B5% (3)
- C2% (1)
- D12% (7)
Why each option
When a server has multiple NICs on different network segments and cannot reach a host on a separate subnet, the routing table is the most likely misconfiguration because it governs which interface handles traffic to each destination.
A server with multiple NICs attached to different network segments requires correct routing table entries to determine which interface and gateway should be used for each destination subnet. If the route to the 10.10.10.0 network is missing, points to the wrong interface, or uses an incorrect next-hop, traffic destined for 10.10.10.180 will be misrouted or dropped regardless of correct NIC-level configuration.
An incorrect NIC1 configuration would disrupt connectivity on NIC1's assigned network segment, not necessarily prevent reaching a host on the subnet served by a different interface.
An incorrect default gateway on NIC1 would affect traffic leaving via NIC1 toward external or different networks but would not explain inability to reach a specific host if the static route for that subnet is the actual missing or wrong entry.
An incorrect subnet mask on NIC2 would cause NIC2 to misidentify which addresses are local versus remote on its segment, but the described symptom of being unable to reach a specific host is more precisely explained by a missing or incorrect route rather than a subnet mask error alone.
Concept tested: Multi-NIC routing table configuration for network segregation
Source: https://learn.microsoft.com/en-us/windows-server/networking/technologies/network-subsystem/net-sub-choose-nic
Topics
Community Discussion
No community discussion yet for this question.
