Refer to the exhibit.

The neighbor relationship is not coming up Which two configurations bring the adjacency up? (Choose two)

• A.NY
  router ospf 1
  area 0 authentication message-digest
• B.LA
  interface E 0/0
  ip ospf message-digest-key 1 md5 Cisco123
• C.NY
  interface E 0/0
  no ip ospf message-digest-key 1 md5 Cisco123
  ip ospf authentication-key Cisco123
• D.LA
  interface E 0/0
  ip ospf authentication-key Cisco123
• E.LA
  router ospf 1
  area 0 authentication message-digest

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

An engineer has configured DMVPN on a spoke router. What is the WAN IP address of another spoke router within the DMVPN network?

• A.172.18.46.2
• B.192.168.1.4
• C.172.18.16.2
• D.192.168.1.1

Correct Answer: A

From the output we can see there are 2 NHRP Peers. The first one with the NBMA Address of
172.18.16.2 and the "Attribute" (Attrb) of Static (S) so we can deduce it is the Hub device.
Therefore the second one must be the remaining Spoke device with the attribute of Dynamic (D).

--> S - Static, D - Dynamic, I - Incomplete
N - NATed, L - Local, X - No Socket
# Ent --> Number of NHRP entries with same NBMA peer
NHS Status: E --> Expecting Replies, R --> Responding, W --> Waiting
UpDn Time --> Up or Down Time for a Tunnel
==
Interface: Tunnel1, IPv4 NHRP Details
Type:Spoke, NHRP Peers:2,
# Ent Peer NBMA Addr Peer Tunnel Add State UpDn Tm Attrb
----- --------------- --------------- ----- -------- -----
1 44.44.44.4 192.168.100.254 UP 00:03:40 S
1 12.12.12.2 192.168.100.2 UP 00:03:20 D

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.


The administrator can see the traps for the failed login attempts, but cannot see the traps of successful login attempts. What command is needed to resolve the issue?

• A.Configure logging history 2
• B.Configure logging history 3
• C.Configure logging history 4
• D.Configure logging history 5

Correct Answer: D

By default, the maximum severity sent as a syslog trap is warning. That is why you see syslog traps for login failures. Since a login success is severity 5 (notifications), those syslog messages will not be converted to traps. To fix this, configure:

Note:
The syntax of login block is:
login block-for seconds attempts tries within seconds

Comment: *

Name: *

Email: *

Verification: *

Drag and drop the MPLS VPN device types from me left onto the definitions on the right.

Correct Answer:

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

Troubleshoot and ensure that branch B only ever uses the MPLS B network to reach HQ. Which action achieves this requirement?

• A.Introduce an AS path filter on branch A routers so that only local prefixes are advertised into BGP
• B.increase the local preference for all HQ prefixes received at branch B from the MPLS B network to be higher than the local preferences used on the MPLS A network
• C.Introduce AS path prepending on the branch A MPLS B network connection so that any HQ advertisements from branch A toward the MPLS B network are prepended three times
• D.Modify the weight of all HQ prefixes received at branch B from the MPLS B network to be higher than the weights used on the MPLS A network

Comment: *

Name: *

Email: *

Verification: *