300-440 · Question #23
Refer to the exhibit. Which Cisco lKEv2 configuration brings up the IPsec tunnel between the remote office router and the AWS virtual private gateway? A. B. C. D.
The correct answer is B. crypto ikev2 proposal Prop-DEMO encryption aes-cbc-128 integrity sha1 group 2 ! crypto ikev2 policy POL-DEMO match address local 209.165.202.105 proposal Prop-POC ! crypto ikev2 keyring DEMO-Keyring peer Cisco-AWS address 209.165.201.1 pre-shared-key DEMOlabCisco12345 ! crypto ikev2 profile PROFILE-PoC match address local 209.165.202.105 match identity remote address 209.165.201.1 255.255.255.255 authentication remote pre-share authentication local pre-share keyring local DEMO-Keyring ! For AWS VPN, the local router's public IP is 209.165.202.105 and the AWS Virtual Private Gateway peer IP is 209.165.201.1. - The IKEv2 policy must reference the correct proposal (Prop-POC) bound to the local IP 209.165.202.105. - The keyring correctly specifies the AWS peer IP…
Question
Exhibits
Options
- Acrypto ikev2 proposal Prop-DEMO encryption aes-cbc-128 integrity sha1 group 2 ! crypto ikev2 policy POL-DEMO match address local 209.165.202.105 proposal Prop-DEMO ! crypto ikev2 keyring DEMO-Keyring peer Cisco-AWS address 209.165.201.1 pre-shared-key DEMOlabCisco12345 ! crypto ikev2 profile PROFILE-PoC match address local 209.165.202.105 match identity remote address 209.165.201.1 255.255.255.255 authentication remote pre-share authentication local pre-share keyring local DEMO-Keyring !
- Bcrypto ikev2 proposal Prop-DEMO encryption aes-cbc-128 integrity sha1 group 2 ! crypto ikev2 policy POL-DEMO match address local 209.165.202.105 proposal Prop-POC ! crypto ikev2 keyring DEMO-Keyring peer Cisco-AWS address 209.165.201.1 pre-shared-key DEMOlabCisco12345 ! crypto ikev2 profile PROFILE-PoC match address local 209.165.202.105 match identity remote address 209.165.201.1 255.255.255.255 authentication remote pre-share authentication local pre-share keyring local DEMO-Keyring !
- Ccrypto ikev2 proposal Prop-DEMO encryption aes-cbc-128 integrity sha1 group 2 ! crypto ikev2 policy POL-DEMO match address local 209.165.202.105 proposal Prop-DEMO ! crypto ikev2 keyring DEMO-Keyring peer Cisco-AWS address 209.165.202.105 pre-shared-key DEMOlabCisco12345 ! crypto ikev2 profile PROFILE-PoC match address local 209.165.202.105 match identity remote address 209.165.201.1 255.255.255.255 authentication remote pre-share authentication local pre-share keyring local DEMO-Keyring !
- Dcrypto ikev2 proposal Prop-DEMO encryption aes-cbc-128 integrity sha1 group 2 ! crypto ikev2 policy POL-DEMO match address local 209.165.202.105 proposal Prop-DEMO ! crypto ikev2 keyring DEMO-Keyring peer Cisco-AWS address 209.165.201.1 pre-shared-key DEMOlabCisco12345 ! crypto ikev2 profile PROFILE-PoC match address local 209.165.202.105 match identity remote address 209.165.202.105 255.255.255.255 authentication remote pre-share authentication local pre-share keyring local DEMO-Keyring !
How the community answered
(42 responses)- A12% (5)
- B81% (34)
- C5% (2)
- D2% (1)
Explanation
For AWS VPN, the local router's public IP is 209.165.202.105 and the AWS Virtual Private Gateway peer IP is 209.165.201.1. - The IKEv2 policy must reference the correct proposal (Prop-POC) bound to the local IP 209.165.202.105. - The keyring correctly specifies the AWS peer IP 209.165.201.1 with the pre-shared key. - The IKEv2 profile matches the local IP 209.165.202.105 and sets the remote identity as
Topics
Community Discussion
No community discussion yet for this question.




