Answer-first summary for fast verification
Answer: The IEEE 802.1Q VLAN identifier is misconfigured on the customer Direct Connect router.
The status of a private VIF (Virtual Interface) on an AWS Direct Connect connection being DOWN, despite the physical connection being UP and RUNNING, and the ARP entry for the VLAN interface being visible on the customer Direct Connect router, suggests a configuration issue rather than a physical connectivity problem. Option A, ICMP being blocked, is unlikely to cause the VIF status to be DOWN because ICMP is not required for the VIF to establish a connection. Option B, TCP port 179 being blocked, is also unlikely because this port is used for BGP (Border Gateway Protocol) sessions, and the question does not mention any issues with BGP. Option D, configuring IEEE 802.1ad instead of 802.1Q, is incorrect because 802.1ad is for provider bridging and not relevant to this scenario. The most likely cause is Option C, the IEEE 802.1Q VLAN identifier being misconfigured on the customer Direct Connect router. This misconfiguration would prevent the VIF from correctly identifying and using the VLAN for its connection, leading to a DOWN status.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company has established a new AWS Direct Connect connection linking its on-premises data center to the AWS Cloud and configured a private VIF on this connection. Despite the physical connection status showing as UP and RUNNING in the AWS Management Console, the private VIF status remains DOWN. The network engineer confirms the ARP entry for the VLAN interface associated with the private VIF is visible on the customer's Direct Connect router. What potential issue could be causing the private VIF to remain in a DOWN state?
A
ICMP is blocked on the customer Direct Connect router.
B
TCP port 179 is blocked on the customer Direct Connect router.
C
The IEEE 802.1Q VLAN identifier is misconfigured on the customer Direct Connect router.
D
The company has configured IEEE 802.1ad instead of 802.1Q on the customer Direct Connect router.