Question 280
A server operations team encounters the following situation: A server NIC is attached to the wrong tagged VLAN and can ping its local test equipment but not its production peers. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Port or virtual NIC VLAN placement differs from the production network design. It builds validation into the affected workflow and supports the expected recovery result: The host reaches authorized same-VLAN peers while isolated networks stay separate.
Incorrect Answers
This control addresses a different scenario: A server has a valid IPv4 address and local subnet access but all remote-site connections fail because the default gateway points to a retired router. That event's root mechanism was incorrect gateway settings prevent off-subnet packet forwarding. The described incident instead arises from: Port or virtual NIC VLAN placement differs from the production network design.
This control addresses a different scenario: Two statically configured cluster nodes share the same IP address and each intermittently drops remote sessions when the other boots. That event's root mechanism was duplicate physical-interface addresses create ARP conflicts and instability. The described incident instead arises from: Port or virtual NIC VLAN placement differs from the production network design.
This control addresses a different scenario: A Windows server obtains a 169.254.x.x address after a switch replacement and cannot reach the production gateway. That event's root mechanism was automatic private IP addressing indicates the expected DHCP configuration was not obtained. The described incident instead arises from: Port or virtual NIC VLAN placement differs from the production network design.