Answer-first summary for fast verification
Answer: Peer ASN: 64515 - Advertised Route Priority (MED): 100 Local BGP IP: 169.254.11.2 - Peer BGP IP: 169.254.11.1 - MD5 Authentication: Disabled
The correct configuration must align with the customer's provided BGP settings. The customer's local ASN is 64515, and their BGP IP is 169.254.11.1. The peer (Google) should use ASN 64517, but the Cloud Router's BGP session configuration requires the Peer ASN to be the customer's ASN (64515). Google's local BGP IP is 169.254.11.2, and the peer BGP IP is 169.254.11.1. MD5 is disabled. The Advertised Route Priority (MED) in Google's configuration does not need to match the customer's base MED (1000); the default/example value (100) is acceptable. Option C correctly sets all these parameters.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have set up a single IPSec Cloud VPN tunnel between your organization and a third-party customer, and the VPN tunnel is confirmed to be established. However, the BGP session status indicates that BGP is not configured. The customer has provided the following BGP settings:
169.254.11.1/3064515169.254.11.2645171000Since the Cloud Router is already associated with the Cloud VPN Tunnel, what BGP session configuration should you apply based on the customer's provided settings?
A
Peer ASN: 64517 - Advertised Route Priority (MED): 100 Local BGP IP: 169.254.11.2 - Peer BGP IP: 169.254.11.1 - MD5 Authentication: Disabled
B
Peer ASN: 64515 - Advertised Route Priority (MED): 100 Local BGP IP: 169.254.11.1 - Peer BGP IP: 169.254.11.2 - MD5 Authentication: Disabled
C
Peer ASN: 64515 - Advertised Route Priority (MED): 100 Local BGP IP: 169.254.11.2 - Peer BGP IP: 169.254.11.1 - MD5 Authentication: Disabled
D
Peer ASN: 64515 - Advertised Route Priority (MED): 1000 Local BGP IP: 169.254.11.2 - Peer BGP IP: 169.254.11.1 - MD5 Authentication: Enabled
No comments yet.