Topic 1 Question 165
A company has a new AWS Direct Connect connection between its on-premises data center and the AWS Cloud. The company has created a new private VIF on this connection. However, the VIF status is DOWN.
A network engineer verifies that the physical connection status is UP and RUNNING based on information from the AWS Management Console. The network engineer checks the customer Direct Connect router and can see the ARP entry for the VLAN interface created for the private VIF at AWS.
What could be causing the private VIF to have a DOWN status?
ICMP is blocked on the customer Direct Connect router.
TCP port 179 is blocked on the customer Direct Connect router.
The IEEE 802.1Q VLAN identifier is misconfigured on the customer Direct Connect router.
The company has configured IEEE 802.1ad instead of 802.1Q on the customer Direct Connect router.
ユーザの投票
コメント(6)
- 👍 7ISSDoksim2023/07/27
- 正解だと思う選択肢: B
Changed to B as the entry is visible for the VLAN interface created for the private VIF at AWS, which means that the Layer 2 connectivity appears to be functioning correctly.
BGP is the issue
👍 6Certified1012023/08/03 - 正解だと思う選択肢: C
If it was B it would show BGP as DOWN not VIF - this is a layer 2 issue
Given the ARP entry visibility and physical connection's UP state, it indicates that the Layer 2 configuration (VLAN) might be correct on the Direct Connect router. However, if the VIF status is still showing as DOWN, it can be related to incorrect 802.1Q VLAN configuration, which might have been performed correctly on the customer end, but misconfigured on the AWS side or vice versa.
So, the correct answer would be:
C. The IEEE 802.1Q VLAN identifier is misconfigured on the customer Direct Connect router.
👍 4Certified1012023/08/03
シャッフルモード