Courseiva

CCNA Bgp Questions

75 of 114 questions · Page 1/2 · Bgp topic · Answers revealed

1
Drag & Dropmedium

Drag and drop the steps of BGP graceful restart negotiation steps into the correct order, from first to last.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5

Why this order

Graceful restart begins with the restarting router sending an OPEN message with the graceful restart capability, followed by the peer acknowledging, then the restarting router marking routes as stale, and finally the peer sending End-of-RIB markers.

2
MCQhard

A network engineer is implementing Control Plane Policing (CoPP) on a Cisco IOS XE router that runs BGP, SSH, and SNMP. The engineer wants to ensure that BGP keepalives are not dropped during a control plane overload, while still rate-limiting SSH and SNMP. The engineer creates a class-map matching BGP, SSH, and SNMP traffic, then applies a policy-map with a single policer of 1000 pps to that class. After applying the service-policy to the control plane, BGP sessions flap during high CPU utilization. What is the most likely cause?

A.CoPP cannot be applied to BGP traffic; it only supports management protocols like SSH and SNMP.
B.The service-policy must be applied to the data plane instead of the control plane for BGP to be protected.
C.The policer rate is too low for BGP keepalives, and all matched traffic is treated equally.
D.The policer should be configured with 'police cir' instead of 'police pps' to properly rate-limit BGP.
AnswerC

A single policer applied to a class that matches BGP, SSH, and SNMP treats all three protocols identically. During high CPU, BGP keepalives may exceed the 1000 pps rate along with other traffic, causing drops. BGP requires a separate class with a higher rate or priority to ensure keepalives are not dropped. The design flaw is the lack of granularity.

Why this answer

CoPP requires granular classification to protect critical protocols. When BGP, SSH, and SNMP are matched in the same class and policed together, BGP keepalives compete with other traffic and may be dropped during high CPU. BGP should be placed in its own class with a higher rate or priority to prevent flapping.

The single policer approach lacks the necessary differentiation.

Exam trap

The trap here is assuming that a single policer can adequately protect all control plane protocols, when in fact BGP requires separate treatment to avoid keepalive drops during congestion.

3
MCQhard

A network engineer is troubleshooting a BGP issue where a router is not installing a specific prefix in its routing table, even though the prefix is present in the BGP table. The engineer runs 'show ip bgp 10.0.0.0/24' and sees that the route is valid but not best. The BGP table shows that the route has a higher local preference than the current best path, but the AS_PATH is longer. What is the most likely reason the route is not being selected as best?

A.The route with higher local preference has a lower weight than the current best path.
B.The route with higher local preference has a higher MED value.
C.The route with higher local preference is not synchronized with IGP.
D.The route with higher local preference was learned from an eBGP peer, while the current best path is from an iBGP peer.
AnswerA

Cisco's BGP best-path algorithm evaluates weight first; the highest weight always wins. Since the current best path has a higher weight, it remains selected regardless of local preference, because local preference is only compared after weights are found equal. Thus a higher local preference cannot make a lower-weight route the best path.

Why this answer

BGP selects the best path based on a sequence of comparison steps. Local preference is checked before AS_PATH length, so a higher local preference should normally win. However, weight is the very first criterion in the BGP best-path selection algorithm.

If the current best path has a higher weight than the route with higher local preference, weight overrides local preference, making the higher-local-preference route not best.

Exam trap

Cisco often tests the order of BGP best-path selection steps, specifically that weight is evaluated before local preference, leading candidates to incorrectly assume that a higher local preference always wins regardless of weight.

How to eliminate wrong answers

Option B is wrong because MED is compared only after the AS_PATH length and origin code, and it is not relevant when a higher local preference is present; the issue here is that weight, which is checked first, is higher on the current best path. Option C is wrong because BGP synchronization is a Cisco-specific feature that requires an IGP route for the next-hop before installing an iBGP route, but it does not affect the best-path selection process; the route is already in the BGP table as valid, and synchronization would prevent installation, not selection as best. Option D is wrong because eBGP routes are preferred over iBGP routes only if all earlier steps (weight, local preference, locally originated) are equal; here, local preference is higher on the candidate route, but weight is the first tiebreaker and is higher on the current best path, so the eBGP vs iBGP comparison never occurs.

4
Matchingmedium

Drag and drop each BGP attribute on the left to its preferred value (highest or lowest) on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Highest

Highest

Lowest

Lowest

Lowest

Why these pairings

Higher WEIGHT and LOCAL_PREF are preferred; lower MED, AS_PATH length, and IGP metric to next-hop are preferred.

5
MCQmedium

An enterprise is implementing MPLS L3VPN to connect multiple branch offices. The PE routers are using eBGP to exchange VPNv4 routes. The engineer notices that some VPN routes are not being advertised to the remote PE. The 'show bgp vpnv4 unicast all' on the local PE shows the routes as valid but not best. What is the most likely reason?

A.The route has a higher local preference than the best path.
B.The route is not valid due to a missing label.
C.The route is not in the BGP table.
D.The route has a higher MED value than the best path.
AnswerD

Multi-Exit Discriminator (MED) is an attribute carried across an AS and is compared only for routes from the same neighboring AS; the lowest MED is preferred. A higher MED value makes a route less desirable and would cause BGP to select the competing path with the lower MED as best. Therefore, this route being non-best is consistent with having a higher MED than the best path.

Why this answer

In BGP, the route with the highest local preference is preferred, so option A is incorrect. The route is valid, so options B and C are incorrect because a missing label would make it invalid, and being in the BGP table is confirmed. MED (Multi-Exit Discriminator) is used in the BGP path selection process; a higher MED value makes a route less preferred compared to a lower MED.

Therefore, if the route has a higher MED than the best path, it will not be selected as best, even though it is valid. This is the most likely reason for the route being valid but not best.

Exam trap

Candidates often assume that a valid route is always advertised, but BGP only advertises the best path. The trap here is confusing local preference and MED: high local preference increases preference, while high MED decreases preference.

How to eliminate wrong answers

Option B is wrong because if the route were missing a label, it would be marked as 'not valid' in the BGP table, not 'valid but not best'. Option C is wrong because the question explicitly states the route is shown in the 'show bgp vpnv4 unicast all' output, so it is in the BGP table. Option D is wrong because a higher MED value would make the route less preferred only if the paths are from the same neighboring AS; however, the route is already valid, and MED is compared after LP and AS-path length, so a higher MED would not cause the route to be valid but not best if LP is the deciding factor.

6
MCQmedium

Consider the following BGP configuration: router bgp 65000 bgp router-id 10.0.0.1 neighbor 10.0.0.2 remote-as 65001 neighbor 10.0.0.2 route-map SET-MED out ! route-map SET-MED permit 10 set metric 50 ! What is the effect of this route-map on outbound updates to neighbor 10.0.0.2?

A.It sets the MED to 50 for all routes advertised to 10.0.0.2, but only if they match a prefix-list.
B.It sets the MED to 50 for all routes advertised to 10.0.0.2.
C.It sets the local preference to 50 for routes received from 10.0.0.2.
D.It filters all routes to 10.0.0.2 because there is no match statement.
AnswerB

The route-map is applied in the outbound direction to neighbor 10.0.0.2. The single permit sequence without a match clause matches all routes, and the set metric 50 command sets the MED to 50. Therefore, every route advertised to that neighbor will carry the MED value of 50. No filtering occurs; the route-map simply modifies the MED attribute for all outbound updates.

Why this answer

The route-map SET-MED is applied to outbound updates to neighbor 10.0.0.2 with a permit sequence 10 and a set metric 50 command, but no match statement. In BGP, a route-map with a permit clause and no match condition matches all routes by default. Therefore, the MED (Multi-Exit Discriminator) attribute is set to 50 for every route advertised to that neighbor.

Exam trap

Cisco often tests the misconception that a route-map without a match statement will deny or filter all routes, but in reality, a permit clause with no match matches everything and applies the set actions.

How to eliminate wrong answers

Option A is wrong because the route-map does not reference any prefix-list, so it applies to all routes, not only those matching a prefix-list. Option C is wrong because the set metric command modifies the MED, not local preference; local preference is set with set local-preference and is an inbound attribute. Option D is wrong because a permit route-map without a match statement does not filter routes; it matches all routes and applies the set actions.

7
MCQmedium

Which BGP attribute is used as the first tie-breaker when multiple paths are available and the weight is equal?

A.Local preference
B.AS path length
C.Origin code
D.MED
AnswerA

Local preference is the second attribute in Cisco's BGP best-path selection process, immediately after the locally significant weight. Because it is a well-known discretionary attribute, it is advertised among iBGP peers within an AS, allowing a network operator to influence outbound traffic across all routers. A higher local preference means the path is more preferred, so it overrides even a longer AS path.

Why this answer

When multiple BGP paths are available for the same prefix, the first tie-breaker after comparing weight (where higher weight is preferred) is Local Preference (Local Pref). Since weight is a Cisco-proprietary attribute that is only locally significant, the next step in the BGP best-path selection algorithm is to compare the Local Preference value, with the highest value being preferred. This makes Local Preference the correct first tie-breaker when weight is equal.

Exam trap

Cisco often tests the order of BGP path selection steps, and the trap here is that candidates confuse the Cisco-proprietary 'weight' attribute (which is checked first) with the standard 'Local Preference' attribute (which is checked second), leading them to incorrectly select AS path length or MED as the next tie-breaker.

How to eliminate wrong answers

Option B is wrong because AS path length is the third tie-breaker in the BGP best-path selection process, used only after comparing weight and Local Preference. Option C is wrong because Origin code (IGP, EGP, incomplete) is the fourth tie-breaker, evaluated after AS path length. Option D is wrong because MED (Multi-Exit Discriminator) is the fifth tie-breaker, used only after comparing Origin code, and it is compared only when paths come from the same neighboring AS.

8
Multi-Selectmedium

Which three statements about BGP peering are true? (Choose three.)

Select 3 answers
A.eBGP peers are typically directly connected, but can be multi-hop with the ebgp-multihop command.
B.iBGP peers can be non-directly connected and often use loopback interfaces for reachability.
C.The default TTL for eBGP packets is 255.
D.In iBGP, all routers within the same AS must be fully meshed unless route reflectors or confederations are used.
E.The BGP router ID is used only for OSPF, not for BGP.
AnswersA, B, D

eBGP peers conventionally establish sessions across directly connected interfaces, since TTL defaults to one. The ebgp-multihop command raises that TTL, permitting sessions between non-adjacent routers separated by intermediate hops. This satisfies the stem's requirement that eBGP peering is typically direct but can be extended across multiple hops when needed.

Why this answer

Option A is correct because eBGP peering normally requires directly connected neighbors, but the Cisco IOS command neighbor x.x.x.x ebgp-multihop <ttl> allows an eBGP session to be established across multiple hops. Option B is correct because iBGP peers do not have to be directly connected; they commonly peer using loopback interfaces, relying on an IGP or static routes for reachability. Option D is correct because iBGP has a split-horizon-like rule preventing routes learned from one iBGP peer from being advertised to another, so full mesh peering is required unless route reflectors or confederations are used.

Option C is not correct because the default TTL for eBGP packets is 1, not 255; 255 is the maximum TTL value. Option E is not correct because the BGP router ID is a 32-bit value used by BGP to identify the router, not an OSPF-only concept.

Exam trap

The trap here is confusing the default TTL for eBGP (which is 1) with the maximum TTL (255), and mistakenly thinking the BGP router ID is used by OSPF.

9
Multi-Selecthard

Which three statements about BGP route selection are true? (Choose three.)

Select 3 answers
A.A route with a lower MED is preferred over a route with a higher MED when all other factors are equal.
B.A route with a higher LOCAL_PREF is preferred over a route with a lower LOCAL_PREF.
C.A route with a shorter AS_PATH is preferred over a route with a longer AS_PATH.
D.A route with a lower weight is preferred over a route with a higher weight.
E.A route with ORIGIN code EGP is preferred over a route with ORIGIN code IGP.
AnswersA, B, C

MED, the optional non-transitive metric, is compared between routes from the same neighbouring AS; the lower value wins when earlier attributes such as weight, LOCAL_PREF and AS_PATH length tie. This matches the stem's condition that all other factors are equal.

Why this answer

Option A is correct because in the BGP best-path algorithm, when all preceding attributes are equal, the route with the lower Multi-Exit Discriminator (MED) value is preferred over one with a higher MED. Option B is correct because a higher LOCAL_PREF (local preference) is always preferred over a lower LOCAL_PREF, and this attribute is evaluated early in the BGP decision process, before AS_PATH. Option C is correct because a shorter AS_PATH is preferred over a longer AS_PATH when comparing routes, as this attribute is checked after LOCAL_PREF and before ORIGIN.

Option D is incorrect because Cisco weight prefers a higher weight, not a lower one. Option E is incorrect because the ORIGIN code preference order is IGP (i) over EGP (e) over INCOMPLETE (?), so EGP is not preferred over IGP.

Exam trap

The trap here is that candidates often confuse weight and LOCAL_PREF preference direction, or forget that ORIGIN preference is IGP > EGP > INCOMPLETE, leading them to select D or E incorrectly.

10
MCQmedium

A network engineer applies the above CoPP policy on a router. The router has BGP peers, SSH management, and SNMP monitoring. After applying this policy, which traffic will be affected?

A.BGP sessions may flap due to dropped keepalives.
B.Data plane traffic will be dropped.
C.Only SSH sessions will be rate-limited.
D.SNMP and SSH will be unaffected because they are explicitly permitted.
AnswerA

BGP keepalives are sent periodically (typically every 60 seconds) and matched by the CoPP BGP class because they are control-plane TCP traffic to/from port 179. If the policer's committed rate is exceeded—even briefly—the excess keepalives are dropped. After a few missed keepalives, the BGP hold timer (default 180 seconds) expires, causing the peer session to flap. The same policer can also drop BGP route updates, which may cause instability beyond just keepalives.

Why this answer

The CoPP policy applies to control plane traffic, not data plane traffic. BGP keepalives are control plane packets; if the policy drops or rate-limits them, BGP sessions may time out and flap. The correct answer is A because BGP keepalives are essential for maintaining neighbor adjacency, and dropping them directly causes session instability.

Exam trap

Cisco often tests the misconception that CoPP affects data plane traffic or that only management protocols like SSH are impacted, when in fact control plane policing targets all control plane packets, including routing protocol keepalives.

How to eliminate wrong answers

Option B is wrong because CoPP operates on the control plane, not the data plane; data plane traffic is forwarded in hardware and unaffected by control plane policing. Option C is wrong because the policy affects all control plane traffic matching the class maps, not just SSH; BGP and SNMP are also subject to rate-limiting or dropping. Option D is wrong because SNMP and SSH are not 'unaffected' — they are explicitly permitted only if they match a permit ACE in the class map; if the class map drops or rate-limits them, they will be affected.

11
MCQeasy

A network engineer runs the following command on Router R4: R4# show mpls interfaces Interface IP Tunnel BGP Static Operational GigabitEthernet0/0 Yes No No No Yes GigabitEthernet0/1 Yes No No No Yes GigabitEthernet0/2 No No No No No Based on this output, what can be concluded?

A.MPLS is enabled and operational on GigabitEthernet0/0 and GigabitEthernet0/1.
B.MPLS is enabled on all three interfaces, but only Gi0/0 and Gi0/1 are operational.
C.BGP and Static label switching are enabled on Gi0/0 and Gi0/1.
D.Tunnel interfaces are configured on Gi0/0 and Gi0/1.
AnswerA

The correct interpretation of the `show mpls interface` output is that both GigabitEthernet0/0 and GigabitEthernet0/1 have MPLS enabled and fully operational. The presence of 'IP: Yes' for each interface indicates that IPv4 label switching is active, while 'Operational: Yes' confirms that the MPLS data plane is ready to forward labeled packets. Therefore, MPLS is not only configured but also functioning on these two interfaces.

Why this answer

The 'show mpls interfaces' command displays MPLS status per interface. The 'Operational' column indicates whether MPLS is actively forwarding labels. GigabitEthernet0/0 and GigabitEthernet0/1 both show 'Yes' in the Operational column, confirming MPLS is enabled and operational on those interfaces.

GigabitEthernet0/2 shows 'No' in both the IP and Operational columns, meaning MPLS is not enabled or operational there.

Exam trap

Cisco often tests the distinction between the 'IP' column (configuration) and the 'Operational' column (actual forwarding state), leading candidates to mistakenly assume an interface is operational just because MPLS is configured, or to misinterpret the 'No' in the IP column as meaning MPLS is disabled entirely rather than just not enabled for IP label distribution.

How to eliminate wrong answers

Option B is wrong because the output shows GigabitEthernet0/2 has 'No' in the IP column and 'No' in the Operational column, indicating MPLS is not enabled on that interface, not just non-operational. Option C is wrong because the BGP and Static columns both show 'No' for all interfaces, meaning BGP label switching and static label switching are not enabled on Gi0/0 or Gi0/1. Option D is wrong because the Tunnel column shows 'No' for all interfaces, indicating no tunnel interfaces are configured on Gi0/0 or Gi0/1.

12
MCQhard

A network engineer is troubleshooting a Cisco Nexus 9000 switch configured with VXLAN EVPN. The engineer notices that the switch is not learning remote MAC addresses from the EVPN control plane. The underlay is OSPF, and BGP EVPN peering is established with the spine switches. Which command should the engineer use to verify that the switch is receiving EVPN Type-2 routes?

A.show ip route vrf all
B.show l2route evpn mac all
C.show nve peers
D.show bgp l2vpn evpn
AnswerD

The command 'show bgp l2vpn evpn' displays the BGP EVPN table, including Type-2 routes (MAC/IP advertisement routes). If the switch is not receiving Type-2 routes, this command will show an empty table or missing entries for the expected MAC addresses. It is the primary command to verify EVPN route reception and is essential for troubleshooting control-plane learning.

Why this answer

To verify that the switch is receiving EVPN Type-2 routes, the engineer should use 'show bgp l2vpn evpn'. This command displays the BGP EVPN table, where Type-2 routes appear as '[2]:[MAC/IP]' entries. If these routes are missing, the switch will not learn remote MAC addresses via EVPN.

Checking the BGP EVPN table is the first step in troubleshooting control-plane learning issues.

Exam trap

The trap here is confusing data-plane verification commands like 'show nve peers' with control-plane verification commands like 'show bgp l2vpn evpn', or looking at the L2 route table instead of the BGP table.

13
Matchingmedium

Drag and drop each BGP message type on the left to its matching function on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Establishes BGP peering parameters

Advertises or withdraws prefixes

Reports error conditions

Maintains session liveness

Requests re-advertisement of routes

Why these pairings

OPEN establishes peering; UPDATE advertises/withdraws routes; NOTIFICATION signals errors; KEEPALIVE maintains session; ROUTE-REFRESH requests re-advertisement.

14
MCQmedium

A network engineer runs the following command on Router R3: R3# show bgp vpnv4 unicast all summary BGP router identifier 10.0.0.3, local AS number 65000 BGP table version is 10, main routing table version 10 10 network entries using 1440 bytes of memory 10 path entries using 1360 bytes of memory 6/5 BGP path/bestpath attribute entries using 840 bytes of memory 4 BGP AS-PATH entries using 112 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 0 BGP filter-list cache entries using 0 bytes of memory BGP using 3752 total bytes of memory BGP activity 20/10 prefixes, 20/10 paths, scan interval 60 secs Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 192.168.1.1 4 65000 1000 1000 10 0 0 01:23:45 5 192.168.2.2 4 65000 800 800 10 0 0 00:45:12 3 Based on this output, what can be concluded?

A.Both neighbors are eBGP peers
B.Both neighbors are iBGP peers exchanging VPNv4 prefixes
C.The neighbor 192.168.1.1 is not receiving any prefixes
D.The BGP table has 20 prefixes
AnswerB

The output is from the IPv4 VPNv4 BGP table, and both neighbors are configured with the same AS number (65000) as the local router, which classifies them as iBGP peers. The PfxRcd column shows that each neighbor has sent 5 prefixes, meaning they are actively exchanging VPNv4 prefixes with this router. This is the correct interpretation of the 'show bgp vpnv4 unicast all' output.

Why this answer

The command `show bgp vpnv4 unicast all summary` displays BGP VPNv4 unicast summary information for all VRFs. Both neighbors (192.168.1.1 and 192.168.2.2) are in the same AS 65000, and the output shows they are exchanging VPNv4 prefixes (State/PfxRcd shows 5 and 3 prefixes received). This confirms they are iBGP peers within the same AS, specifically for VPNv4 address family, which is used in MPLS Layer 3 VPN environments to carry customer VPN routes.

Exam trap

Cisco often tests the distinction between eBGP and iBGP by using the same AS number in the output, and candidates may overlook that the `vpnv4 unicast all` address family is specifically for MPLS VPN iBGP peering, not for standard IPv4 unicast.

How to eliminate wrong answers

Option A is wrong because both neighbors have the same AS number (65000) as the local router, which indicates iBGP peering, not eBGP (which requires different AS numbers). Option C is wrong because the State/PfxRcd column shows 5 prefixes received from 192.168.1.1, meaning it is actively receiving prefixes. Option D is wrong because the output clearly states '10 network entries' and '20/10 prefixes' (activity counters), not 20 prefixes in the current BGP table.

15
MCQmedium

A network engineer is deploying Control Plane Policing on a Cisco IOS XE router that runs BGP, SSH management, and SNMP monitoring. The engineer must ensure that BGP keepalives are never dropped even during a control-plane flood, while SSH and SNMP traffic should be rate-limited. Which CoPP configuration element accomplishes this requirement?

A.Create a class-map matching BGP traffic with a 'police' action and assign it to the control-plane policy-map.
B.Create a class-map matching BGP traffic and apply a 'police' action with a conform-action of 'transmit' and an exceed-action of 'transmit'.
C.Create a class-map matching BGP traffic and apply a 'police' action with a very high committed information rate (CIR).
D.Create a class-map matching BGP traffic and reference it in the control-plane policy-map without applying any police action.
AnswerD

Classes in a control-plane policy-map that have no police action applied are not rate-limited, so matching BGP traffic and simply referencing it in the policy-map exempts BGP from CoPP policing. The engineer can then apply 'police' actions to SSH and SNMP classes. This satisfies the requirement that BGP keepalives are never dropped while still rate-limiting other control-plane traffic.

Why this answer

CoPP works by classifying control-plane traffic and applying actions, most commonly 'police'. Any class that has no police action is effectively passed without rate limiting, which is exactly what is needed for BGP keepalives that must never be dropped. SSH and SNMP classes can then receive 'police' actions with appropriate conform/exceed handling.

This design isolates critical routing protocol traffic from the effects of a control-plane flood.

Exam trap

The trap here is assuming that every class in a CoPP policy-map must have a police action, when in fact a class without a police action passes traffic unconditionally.

16
MCQeasy

Which BGP attribute is preferred when it has the lowest value?

A.MED (Multi-Exit Discriminator)
B.Local Preference
C.Weight
D.AS Path
AnswerA

The MED attribute is used to indicate the preferred path into an AS; lower MED is better.

Why this answer

The Multi-Exit Discriminator (MED) is a BGP path attribute used to influence inbound traffic to an AS from multiple entry points. A lower MED value is preferred over a higher one, making it the correct answer among the options where the lowest value is preferred.

Exam trap

Cisco often tests the distinction between attributes where higher is preferred (Local Preference, Weight) versus lower is preferred (MED, AS Path length), and the trap here is that candidates might confuse MED with Local Preference or Weight, both of which use higher values as better.

How to eliminate wrong answers

Option B (Local Preference) is wrong because Local Preference is used to influence outbound traffic from an AS, and a higher value is preferred, not lower. Option C (Weight) is wrong because Weight is a Cisco-proprietary attribute that is preferred when it has a higher value, not lower. Option D (AS Path) is wrong because a shorter AS Path length is preferred, meaning a lower count is better, but the question asks for an attribute where the lowest value is preferred, and AS Path is not typically described as a 'value' in the same sense as MED; moreover, AS Path length is a count, not a metric like MED, and the question's phrasing aligns more directly with MED's explicit numeric comparison.

17
MCQhard

A network engineer runs the following command on Router R6: R6# show ip bgp vpnv4 all summary BGP router identifier 10.0.0.6, local AS number 65000 BGP table version is 10, main routing table version 10 10 network entries using 1440 bytes of memory 10 path entries using 800 bytes of memory 4/3 BGP path/bestpath attribute entries using 576 bytes of memory 2 BGP AS-PATH entries using 48 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 0 BGP filter-list cache entries using 0 bytes of memory Bitfield cache entries: current 1 (at peak 2) using 32 bytes of memory BGP using 2896 total bytes of memory BGP activity 20/10 prefixes, 20/10 paths, scan interval 60 secs Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.0.0.7 4 65001 1000 1000 10 0 0 00:20:00 5 10.0.0.8 4 65002 500 500 10 0 0 00:10:00 3 Based on this output, what can be concluded?

A.Both BGP sessions are in the Idle state.
B.The router is receiving VPNv4 prefixes from both neighbors.
C.The BGP table has no entries because the table version is 10.
D.The neighbor 10.0.0.8 is not configured for VPNv4.
AnswerB

The State/PfxRcd values of 5 and 3 for the two neighbors indicate that the local router has received a total of eight VPNv4 unicast prefixes from them. Because the command is issued under the VPNv4 address family, these prefixes are VPNv4 routes, which carry an 8-byte route distinguisher and are used in MPLS L3VPN to propagate customer prefixes across the provider backbone. The nonzero counts prove active, established sessions and successful VPNv4 route exchange with both peers, so the correct interpretation is that the router is receiving VPNv4 prefixes from both neighbors.

Why this answer

The output shows that neighbor 10.0.0.7 (AS 65001) has 5 prefixes received (State/PfxRcd = 5) and neighbor 10.0.0.8 (AS 65002) has 3 prefixes received (State/PfxRcd = 3). Since the command 'show ip bgp vpnv4 all summary' specifically displays VPNv4 address family information, these received prefixes are VPNv4 routes. Therefore, Router R6 is successfully receiving VPNv4 prefixes from both BGP neighbors.

Exam trap

Cisco often tests the misinterpretation of the 'State/PfxRcd' column, where candidates mistakenly think a numeric value indicates a state like 'Idle' or 'Active', rather than recognizing it as the count of received prefixes confirming an Established session.

How to eliminate wrong answers

Option A is wrong because both neighbors show an Up/Down time (00:20:00 and 00:10:00) and a numeric State/PfxRcd value, indicating the sessions are in the Established state, not Idle. Option C is wrong because the BGP table version being 10 indicates the table has been updated and is stable; the output explicitly shows '10 network entries' and '10 path entries', proving the BGP table has entries. Option D is wrong because neighbor 10.0.0.8 shows 3 prefixes received (State/PfxRcd = 3) under the VPNv4 summary, confirming it is configured for VPNv4 and is actively exchanging VPNv4 routes.

18
MCQhard

A network engineer runs the following command on Router R5: R5# show ip route vrf CUSTOMER-A Routing Table: CUSTOMER-A Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route Gateway of last resort is 10.1.1.1 to network 0.0.0.0 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 10.1.1.0/24 is directly connected, GigabitEthernet0/0 B 10.2.2.0/24 [20/0] via 10.1.1.1, 00:10:20 Based on this output, what can be concluded?

A.The VRF has no routes and is not functional.
B.The route 10.2.2.0/24 is learned via OSPF.
C.The VRF has a default route pointing to 10.1.1.1.
D.The BGP route is sourced from an internal BGP peer.
AnswerC

The VRF routing table shows a 'Gateway of last resort is 10.1.1.1' line, which indicates a default route of 0.0.0.0/0 is installed with next hop 10.1.1.1. This S* route means any destination not matching a more specific prefix will be sent to 10.1.1.1. Thus, the correct statement is that the VRF has a default route pointing to 10.1.1.1.

Why this answer

The output shows a VRF routing table with a gateway of last resort set to 10.1.1.1 for network 0.0.0.0, which is a default route. This indicates that the VRF has a default route pointing to 10.1.1.1, making option C correct. The presence of a connected route and a BGP-learned route further confirms the VRF is functional.

Exam trap

Cisco often tests the distinction between eBGP and iBGP by using administrative distance values; the trap here is that candidates may assume any BGP route is from an internal peer without checking the AD value, which for eBGP is 20 and for iBGP is 200.

How to eliminate wrong answers

Option A is wrong because the VRF has both a connected route (10.1.1.0/24) and a BGP-learned route (10.2.2.0/24), so it is functional. Option B is wrong because the route 10.2.2.0/24 is marked with 'B' in the routing table, which indicates it is learned via BGP, not OSPF. Option D is wrong because the BGP route shows an administrative distance of 20 and a metric of 0, which are typical for eBGP (external BGP) routes, not iBGP (internal BGP) routes; iBGP routes typically have an administrative distance of 200.

19
Matchinghard

Drag and drop each BGP path selection criterion on the left to its order of preference (1 = highest priority) on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

1

2

3

4

5

Why these pairings

Weight (highest) is checked first, then LOCAL_PREF (highest), then locally originated routes, then AS_PATH (shortest), then ORIGIN (IGP < EGP < incomplete).

20
MCQmedium

A network administrator is configuring Control Plane Policing (CoPP) on a Cisco IOS XE router that peers BGP with two ISPs and is managed over SSH. The administrator needs to protect the route processor from excessive BGP and SSH traffic without breaking the existing sessions. Which action should be taken when applying the CoPP policy?

A.Apply the policy-map to the control-plane interface using the service-policy input command.
B.Apply the policy-map to the management VRF interface using service-policy input.
C.Apply the policy-map globally with the service-policy command in global configuration mode.
D.Apply the policy-map to each ISP-facing physical interface with service-policy output.
AnswerA

CoPP policies are applied to the control plane by attaching the policy-map to the control-plane interface with service-policy input. This filters traffic destined to the route processor while allowing transit traffic to pass untouched, which preserves the BGP and SSH sessions.

Why this answer

CoPP is designed to classify and police traffic destined to the route processor. The policy-map must be attached to the control-plane interface with service-policy input so that only CPU-bound traffic is policed while transit traffic remains unaffected, preserving BGP peering and SSH management access.

Exam trap

The trap here is assuming CoPP is applied to physical interfaces like a normal QoS policy, when it must be attached to the control-plane interface.

21
MCQmedium

A network administrator is configuring Control Plane Policing (CoPP) on a Cisco IOS XE router that runs BGP, SSH, and SNMP. The administrator needs to verify which traffic classes are being matched and how many packets are being dropped by the policy. Which command should be used to display the CoPP policy statistics and class-map information?

A.show policy-map interface
B.show class-map
C.show policy-map control-plane
D.show control-plane host open-ports
AnswerC

This command displays the Control Plane policy-map configuration and the per-class packet statistics, including matched and dropped packets. It directly shows which traffic classes are being matched and how many packets are being dropped, which is exactly what the administrator needs to verify CoPP operation.

Why this answer

The show policy-map control-plane command is specifically designed to display the CoPP policy configuration and per-class statistics, including matched and dropped packets. It allows the administrator to verify which traffic classes are being matched and how many packets are being dropped by the policy. The other commands either show only class-map definitions or interface-level policy statistics, which are not relevant to the control plane.

Exam trap

The trap here is confusing interface-level policy statistics with control plane policy statistics, or assuming that show class-map displays counters when it only shows match criteria.

22
MCQmedium

A network administrator is troubleshooting a BGP routing issue where routes from an eBGP neighbor are not being installed in the routing table. The 'show ip bgp' output shows the routes are received but not valid. What is the most likely cause?

A.The AS-path contains the local AS number.
B.The next-hop IP address is not reachable.
C.BGP synchronization is enabled.
D.The maximum-prefix limit has been exceeded.
AnswerB

Correct. For a BGP route to be considered valid and installed in the routing table, the next-hop IP address must be reachable via an IGP or static route. If the next hop is not reachable, the route will appear in the 'show ip bgp' output but be marked as not valid.

Why this answer

For a BGP route to be considered valid and installed in the routing table, the next-hop IP address must be reachable via an IGP or a static route. If the next hop is not reachable, the route will appear in the 'show ip bgp' output but will be marked as not valid (often with a 'r' for received but not valid). This is the most common cause when routes are received from an eBGP neighbor but not installed.

Exam trap

Cisco often tests the distinction between routes being received in the BGP table versus being installed in the routing table, and the trap here is that candidates confuse synchronization (a deprecated feature) with the next-hop reachability requirement, which is the immediate cause of the 'not valid' status.

How to eliminate wrong answers

Option A is wrong because if the AS-path contains the local AS number, BGP would reject the route due to loop prevention (the route would be marked as invalid or not received at all), but the question states routes are received. Option C is wrong because BGP synchronization is disabled by default in modern IOS versions and, even if enabled, it would affect the route's validity only if the prefix is not present in the IGP, but the next-hop reachability check is more fundamental. Option D is wrong because exceeding the maximum-prefix limit would cause the BGP session to be torn down or the neighbor to be shut down, not simply mark routes as not valid while keeping them in the BGP table.

23
MCQhard

A network engineer is troubleshooting a Cisco Nexus 9000 switch configured for VXLAN EVPN. The engineer notices that the switch is not learning remote MAC addresses from other VTEPs. The underlay routing is working, and MP-BGP EVPN peering is established. Which configuration issue could prevent the switch from learning remote MAC addresses?

A.The BGP router ID is not unique.
B.The VNI is not mapped to the correct VLAN in the EVPN configuration.
C.The underlay OSPF cost is too high.
D.The switch is configured with a static VXLAN tunnel instead of a dynamic one.
AnswerB

For VXLAN EVPN to learn remote MAC addresses, the VNI must be mapped to the correct VLAN. If the mapping is missing or incorrect, the switch cannot associate incoming EVPN routes with the local VLAN, preventing MAC learning. This is a common misconfiguration that breaks overlay connectivity.

Why this answer

In VXLAN EVPN, the VNI must be mapped to the correct VLAN for the switch to associate EVPN routes with local VLANs and learn remote MAC addresses. If the mapping is missing or incorrect, the switch cannot install remote MACs into the MAC address table, even if EVPN peering is up and the underlay is functional.

Exam trap

The trap here is focusing on underlay or BGP peering issues when the problem is actually a local mapping mismatch between the VNI and VLAN, which is a common EVPN configuration oversight.

24
MCQeasy

Which BGP attribute is preferred with the lowest value?

A.MED
B.Local Preference
C.Weight
D.Origin
AnswerA

MED (Multi-Exit Discriminator) is an optional, non-transitive BGP attribute used to influence inbound traffic from a neighboring autonomous system. When comparing multiple paths that share the same neighboring AS, Cisco IOS prefers the path with the lowest MED value, making lower better. MED is the correct answer because it is the only attribute among the listed options where a numerically lower value is explicitly preferred in BGP path selection, and it is typically set to reflect internal IGP metrics or link costs.

Why this answer

MED (Multi-Exit Discriminator) is a BGP attribute that is preferred with the lowest value. It is used to influence inbound traffic to an AS when multiple entry points exist, and a lower MED value is more preferred over a higher one.

Exam trap

Cisco often tests the confusion between attributes that use 'lowest is best' (like MED and IGP metric) versus 'highest is best' (like Local Preference and Weight), so candidates mistakenly apply the 'highest is best' rule to MED.

How to eliminate wrong answers

Option B (Local Preference) is wrong because Local Preference is preferred with the highest value, not the lowest, and is used to influence outbound traffic from an AS. Option C (Weight) is wrong because Weight is a Cisco-proprietary attribute that is preferred with the highest value, and it is local to the router. Option D (Origin) is wrong because Origin is preferred in the order IGP < EGP < incomplete, not based on a numeric value.

25
Matchingmedium

Drag and drop each BGP attribute on the left to its matching attribute type on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Well-known mandatory

Well-known discretionary

Optional transitive

Optional non-transitive

Well-known mandatory

Why these pairings

AS_PATH is well-known mandatory; LOCAL_PREF is well-known discretionary; COMMUNITY is optional transitive; MULTI_EXIT_DISC is optional non-transitive; ORIGIN is well-known mandatory.

26
MCQmedium

A company is using a dual-homed MPLS L3VPN connection with two different ISPs. The CE router is running eBGP with both PE routers. The engineer wants to ensure that inbound traffic from the Internet to the company's web servers uses both links, but outbound traffic from the company should prefer ISP A. The company advertises the same /24 prefix to both ISPs. What BGP configuration should the engineer apply on the CE router?

A.Set a lower MED for routes advertised to ISP A and a higher MED for routes advertised to ISP B.
B.Use AS path prepending on routes advertised to ISP B and set a higher local preference for routes learned from ISP A.
C.Advertise a more specific prefix (e.g., /25) to ISP A and a less specific prefix (/24) to ISP B.
D.Configure the CE router to use BGP multipath with both ISPs.
AnswerB

AS path prepending artificially extends the AS_PATH attribute, so ISP B sees a longer AS path and deprioritizes that route for inbound traffic, while the /24 remains advertised normally. Setting a higher local preference for routes learned from ISP A only influences routers inside your autonomous system, causing outbound traffic to prefer ISP A regardless of other attributes. This separation of inbound and outbound control is exactly the standard BGP traffic engineering approach.

Why this answer

AS path prepending makes the route to ISP B appear less attractive for inbound traffic, while setting a higher local preference on routes learned from ISP A makes ISP A the preferred path for outbound traffic. This combination achieves the asymmetric routing goal: inbound traffic uses both links (since prepending only influences ISP B's decision, not ISP A's), and outbound traffic prefers ISP A due to the higher local preference.

Exam trap

Cisco often tests the distinction between inbound and outbound traffic engineering: candidates confuse attributes that influence inbound traffic (like MED and AS path prepending) with those that influence outbound traffic (like local preference and weight), leading them to pick Option A or C incorrectly.

How to eliminate wrong answers

Option A is wrong because MED is a metric sent to a specific neighbor and is only compared when paths come from the same AS; since the two ISPs are different ASes, MED would not be compared, and even if it were, lower MED makes a route more preferred, which would attract more inbound traffic to ISP A, not balance it. Option C is wrong because advertising a more specific prefix (/25) to ISP A would cause ISP A to prefer that route over the /24, attracting all inbound traffic to ISP A, not balancing it; also, this violates the requirement to advertise the same /24 prefix to both ISPs. Option D is wrong because BGP multipath allows the CE router to load-balance outbound traffic across both ISPs, but the requirement is to prefer ISP A for outbound traffic, not to load-balance equally.

27
Multi-Selectmedium

A network engineer is hardening a Cisco IOS XE router against control plane attacks. The router runs OSPF, BGP, and SSH management. The engineer wants to apply Control Plane Policing (CoPP) to rate-limit nonessential traffic while ensuring routing protocols are not disrupted. Which two actions should the engineer take? (Choose two.)

Select 2 answers
A.Configure a single class map that matches all IP traffic and police it to a low rate to simplify the policy.
B.Use a route map to classify traffic and attach it to the control plane with the service-policy command.
C.Create class maps that match routing protocol traffic, such as OSPF and BGP, and assign them a higher policing rate than nonessential traffic.
D.Apply the CoPP policy map under control-plane configuration mode using the service-policy command.
E.Apply the CoPP policy map inbound on all WAN interfaces to filter traffic before it reaches the route processor.
AnswersC, D

Routing protocols are essential for network stability, so they should be matched in dedicated class maps and given sufficient policing rates to avoid dropping legitimate updates. This allows CoPP to protect the CPU while preventing disruption to OSPF and BGP adjacencies, which is a key requirement in the scenario.

Why this answer

Effective CoPP requires class maps that separate essential traffic, such as OSPF and BGP, from nonessential traffic, with appropriate policing rates for each. The policy map is then applied under control-plane configuration mode. This structure protects the route processor without disrupting routing protocols or management access.

Exam trap

The trap here is applying CoPP to data interfaces or using a single blanket policer, which would either miss CPU-bound traffic or throttle essential routing and management protocols.

28
MCQmedium

A network engineer is deploying Control Plane Policing on a Cisco IOS XE router that carries eBGP, OSPF, SSH management, and SNMP traffic. The engineer wants to ensure that BGP and OSPF routing updates are never dropped while still rate-limiting SSH and SNMP. Which CoPP configuration approach best meets this requirement?

A.Apply a single class-map matching all control-plane traffic and set a single police rate that is high enough for routing protocols.
B.Create separate class-maps for BGP, OSPF, SSH, and SNMP, then apply a policy-map where routing classes use police with a high conform rate and management classes use a lower police rate.
C.Use MQC with a single class-default and configure a priority queue for BGP and OSPF packets.
D.Configure an ACL that denies SSH and SNMP to the control plane and apply it inbound on all interfaces.
AnswerB

Separate class-maps allow granular classification, and the policy-map can apply different police actions per class. Routing classes can be policed generously (or with conform-action transmit and exceed-action transmit for critical control traffic), while SSH and SNMP are rate-limited. This is the standard CoPP design pattern for differentiated control-plane protection.

Why this answer

CoPP is designed to classify control-plane traffic into distinct classes and apply independent policers. Separating routing protocols from management protocols allows the engineer to protect BGP and OSPF adjacencies while still enforcing limits on SSH and SNMP. A single class-map or class-default cannot provide this granularity, and an ACL would block rather than rate-limit management traffic.

Exam trap

The trap here is assuming that a single high-rate policer can protect all control-plane traffic without distinguishing routing protocols from management protocols.

29
MCQeasy

A network engineer runs the following command on Router R1: R1# show bgp ipv4 unicast summary | include 10.0.1.5 10.0.1.5 4 65005 3456 3457 15 0 0 00:15:22 5 Based on this output, what can be concluded?

A.The BGP session with 10.0.1.5 has been down for 15 minutes and 22 seconds.
B.The BGP session with 10.0.1.5 is up and has received 5 prefixes.
C.The BGP session with 10.0.1.5 is in the 'Active' state.
D.The BGP session with 10.0.1.5 has sent 5 prefixes.
AnswerB

The '5' in the State/PfxRcd column is the number of Network Layer Reachability Information (NLRI) prefixes that this router received from 10.0.1.5 over the established BGP session. Crucially, when the session is in the Established state, the column shows a numeric prefix count rather than a state keyword such as Active, Idle, or Connect. Thus, the neighbor is up and has successfully exchanged routes.

Why this answer

The 'show bgp ipv4 unicast summary' output displays BGP neighbor status. The column 'Up/Down' shows '00:15:22', indicating the session has been established for 15 minutes and 22 seconds, not down. The last column shows '5', which under the 'PfxRcd' (Prefixes Received) column indicates the number of prefixes received from the neighbor.

Therefore, the session is up and has received 5 prefixes.

Exam trap

Cisco often tests the misinterpretation of the 'Up/Down' column, where candidates mistakenly read it as downtime instead of uptime, and the confusion between prefixes received (PfxRcd) and prefixes sent (PfxSent), which is not shown in this output.

How to eliminate wrong answers

Option A is wrong because the 'Up/Down' column value '00:15:22' represents the duration the session has been up, not down; a down session would show a different state or 'never'. Option C is wrong because the output shows a valid neighbor IP, AS number, and uptime, indicating the session is in the Established state, not Active; the Active state would not show prefixes received. Option D is wrong because the '5' in the output corresponds to prefixes received (PfxRcd), not sent; sent prefixes are not displayed in this summary output.

30
MCQhard

A network engineer is configuring CoPP on a Cisco ASR 1000 router to protect the control plane from excessive traffic. The engineer wants to allow BGP traffic from a specific peer (10.0.0.1) while rate-limiting all other BGP traffic. The engineer creates an ACL that permits TCP port 179 from host 10.0.0.1 and denies all other BGP traffic. The CoPP class-map matches this ACL. However, after applying the policy, BGP sessions from other peers are still being established. What is the most likely reason?

A.The ACL denies all other BGP traffic, so CoPP does not match it, and it falls through to the default class, which permits it.
B.The ACL is applied in the wrong order; the deny statement should be before the permit statement.
C.BGP uses UDP port 179, not TCP, so the ACL does not match BGP traffic.
D.CoPP does not affect BGP sessions because they are established before the policy is applied.
AnswerA

CoPP class-maps only act on traffic the ACL permits; denied traffic matches no class and falls to the default class, which typically permits it. So other BGP peers are not rate-limited, explaining why their sessions still establish.

Why this answer

The ACL is designed to match BGP traffic from host 10.0.0.1 (permit) and deny all other BGP traffic. However, CoPP class-maps match traffic based on permit statements in the ACL; a deny statement in the ACL causes the traffic to not be matched by that class. As a result, BGP traffic from other peers is not classified into the rate-limiting class and falls through to the default class, which typically permits all traffic.

This explains why BGP sessions from other peers are still being established.

Exam trap

Cisco often tests the misconception that a deny statement in an ACL used with CoPP will drop traffic, when in reality it only prevents the traffic from being matched by that class, allowing it to fall through to the default class which typically permits everything.

How to eliminate wrong answers

Option B is wrong because the order of permit and deny statements in an ACL is critical, but here the permit for host 10.0.0.1 is correctly placed before the deny all; the issue is not about order but about how CoPP treats deny entries. Option C is wrong because BGP uses TCP port 179, not UDP; this is a fundamental protocol fact. Option D is wrong because CoPP affects all traffic arriving at the control plane after the policy is applied, regardless of when sessions were established; existing sessions are still subject to rate-limiting.

31
MCQmedium

A network engineer runs the following command on Router R3: R3# show ip route ospf Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP a - application route + - replicated route, % - next hop override Gateway of last resort is not set 10.0.0.0/8 is variably subnetted, 5 subnets, 3 masks O IA 10.1.1.0/24 [110/20] via 192.168.1.1, 00:12:34, GigabitEthernet0/0 O 10.2.2.0/24 [110/10] via 192.168.1.2, 00:15:22, GigabitEthernet0/0 O E2 10.3.3.0/24 [110/20] via 192.168.1.3, 00:08:11, GigabitEthernet0/0 Based on this output, what can be concluded?

A.The route to 10.3.3.0/24 is an external route redistributed into OSPF.
B.The route to 10.1.1.0/24 is in the same OSPF area as R3.
C.The metric for 10.3.3.0/24 includes the internal cost to the ASBR.
D.R3 is an ASBR.
AnswerA

The route to 10.3.3.0/24 is an external route redistributed into OSPF. In the routing table, the code 'O E2' explicitly marks this as an OSPF external route of type 2. Type 2 (E2) routes are routes that originated outside the OSPF domain and were redistributed into OSPF, typically from another routing protocol such as EIGRP or BGP. The external cost is carried as configured on the ASBR, and in this case the metric of 20 is the default external cost for redistributed routes, confirming the redistributed origin.

Why this answer

The route to 10.3.3.0/24 is marked as 'O E2' in the output, which stands for OSPF external type 2. This indicates that the route was redistributed into OSPF from another routing protocol or a different OSPF process, making it an external route. The 'E2' designation confirms it is an external route with a fixed metric that does not include the internal cost to the ASBR.

Exam trap

Cisco often tests the difference between OSPF external type 1 (E1) and type 2 (E2) routes, specifically that E2 routes do not include the internal cost to the ASBR, which is a common misconception that leads candidates to incorrectly select option C.

How to eliminate wrong answers

Option B is wrong because the route to 10.1.1.0/24 is marked as 'O IA' (OSPF inter-area), which means it originates from a different OSPF area than R3, not the same area. Option C is wrong because for an OSPF external type 2 (E2) route, the metric shown (20) is the external metric only and does not include the internal cost to the ASBR; that behavior is specific to external type 1 (E1) routes. Option D is wrong because R3 is simply receiving these OSPF routes; there is no indication in the output that R3 is redistributing routes into OSPF, which would be required for it to be an ASBR.

32
MCQmedium

A network engineer is configuring MPLS L3VPN on a Cisco IOS-XE PE router. The engineer creates a VRF named CUSTOMER_A with route-target import and export 100:1. After configuring the VRF on the interface connected to the CE router, the CE router can ping the PE's VRF interface IP, but cannot reach any remote VPNv4 routes. The BGP session between PE and route reflector is up. What is the most likely cause?

A.The route-target import/export values are mismatched with the route reflector's configuration.
B.The VRF is not activated under BGP using the address-family ipv4 vrf CUSTOMER_A command.
C.The CE router is not configured with a default route pointing to the PE.
D.The PE router needs the mpls ip command on the interface facing the CE router.
AnswerB

Without the address-family ipv4 vrf CUSTOMER_A command under BGP, the PE does not establish an internal BGP session for that VRF nor inject connected/static routes into VPNv4. This means no VPNv4 routes are generated for CUSTOMER_A, and no remote VPNv4 routes are imported into the VRF, so only the directly connected CE subnet is reachable. Activating the VRF in BGP is the mandatory prerequisite for inter-site route exchange in MPLS Layer 3 VPN.

Why this answer

The CE router can ping the PE's VRF interface IP, confirming Layer 2 and VRF interface configuration are correct. However, the CE cannot reach remote VPNv4 routes, which indicates that the PE is not advertising or installing those routes into the VRF. The most likely cause is that the VRF CUSTOMER_A has not been activated under BGP using the 'address-family ipv4 vrf CUSTOMER_A' command, which is required to exchange IPv4 routes between the PE and CE within the VRF context and to redistribute them into MP-BGP for VPNv4 propagation.

Exam trap

Cisco often tests the misconception that a working BGP session to the route reflector and correct route-target values alone are sufficient for VPNv4 route exchange, when in fact the VRF must be explicitly activated under BGP to enable route advertisement and import.

How to eliminate wrong answers

Option A is wrong because the route-target import/export values (100:1) are configured on the PE, and the route reflector does not need matching route-targets; it only reflects VPNv4 routes based on the RTs attached to the routes, and the PE's import RT must match the export RT of the remote PE, not the route reflector. Option C is wrong because the CE router not having a default route pointing to the PE would affect reachability to remote networks from the CE, but the symptom is that the CE cannot reach remote VPNv4 routes at all, which is a routing advertisement issue on the PE, not a missing default route on the CE. Option D is wrong because the 'mpls ip' command is required on the PE's core-facing interfaces to enable MPLS forwarding, not on the interface facing the CE, which is a Layer 3 VRF interface that does not require MPLS encapsulation.

33
Drag & Dropmedium

Drag and drop the steps of BGP policy application (route-map, prefix-list, AS-path ACL) into the correct order, from first to last.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5

Why this order

First, you create the prefix-list or AS-path ACL to match routes. Then you define the route-map with match and set clauses. Next, you apply the route-map to a neighbor under the BGP address-family.

After that, you clear the BGP session to apply the policy. Finally, you verify the policy effect with show ip bgp.

34
Matchinghard

Drag and drop each BGP path selection criterion on the left to its correct order of preference (1 = highest priority) on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

1

2

3

4

5

Why these pairings

Weight (highest) is checked first, then LOCAL_PREF (highest), then locally originated routes, then AS_PATH length (shortest), then ORIGIN (IGP > EGP > incomplete).

35
Multi-Selecthard

A network engineer is implementing Control Plane Policing (CoPP) on a Cisco ASR 1000 router to protect the route processor from excessive traffic. The router runs OSPF, BGP, SSH management, and NTP. The engineer wants to ensure that OSPF hello packets are always prioritized and that SSH traffic from the management subnet is rate-limited. Which two statements about the CoPP configuration are true? (Choose two.)

Select 2 answers
A.CoPP is applied to individual data plane interfaces using the 'service-policy input' command on each physical interface.
B.CoPP uses a modular QoS CLI policy map applied globally with the 'service-policy' command under control-plane configuration mode.
C.The default CoPP policy that ships with Cisco IOS XE already rate-limits SSH and OSPF traffic without any custom configuration.
D.CoPP policies can differentiate OSPF and SSH traffic by using ACLs referenced in class maps to match specific protocols and source addresses.
E.CoPP can only police traffic; it cannot mark or prioritize specific control plane protocols such as OSPF.
AnswersB, D

CoPP is implemented using MQC constructs where a class map matches control plane traffic and a policy map defines policing actions. The policy map is then applied under the control-plane configuration mode using the service-policy command, which directs the policy to the route processor's traffic rather than to data plane interfaces.

Why this answer

CoPP uses MQC class maps and policy maps applied under control-plane configuration mode. Class maps reference ACLs to distinguish protocols like OSPF and SSH, allowing differentiated policing and prioritization actions. Applying the policy to physical interfaces or assuming default policies meet custom requirements are common misconceptions.

Exam trap

The trap here is confusing CoPP with interface-level QoS by assuming the service-policy is applied to data plane interfaces rather than the control plane.

36
MCQmedium

A network engineer is configuring Control Plane Policing (CoPP) on a Cisco IOS XE router. The router has management SSH access, SNMP monitoring, and BGP peering. After applying the CoPP policy shown in the exhibit, the engineer notices that SNMP polling from the management station fails, while SSH and BGP remain operational. Which action should be taken to restore SNMP polling while maintaining control plane protection?

A.Increase the policer rate for the default class to allow all unmatched traffic, including SNMP.
B.Remove the CoPP policy from the control plane and reapply it after verifying SNMP connectivity.
C.Configure an ACL to permit SNMP traffic and apply it to the management interface instead of the control plane.
D.Add a class-map that matches SNMP traffic (UDP port 161) and include it in the CoPP policy with an appropriate policer rate.
AnswerD

The CoPP policy likely does not have a class-map for SNMP, so SNMP packets fall into the default class and may be dropped by the default policer. Adding a specific class-map for SNMP (UDP 161) with a suitable policer ensures SNMP traffic is permitted at the required rate while still protecting the control plane from excessive SNMP traffic.

Why this answer

CoPP policies must explicitly classify and police all desired control plane traffic. If SNMP is not classified, it falls into the default class, which typically has a low rate and may drop legitimate SNMP. Adding a dedicated class-map for SNMP with an appropriate policer restores connectivity while preserving protection.

Exam trap

The trap here is assuming that increasing the default policer rate or removing CoPP is acceptable, rather than adding the missing classification for SNMP.

37
Multi-Selecthard

Which two statements about BGP route selection are true? (Choose two.)

Select 2 answers
A.A route with a higher LOCAL_PREF is preferred over a route with a lower LOCAL_PREF.
B.A route learned via eBGP is preferred over a route learned via iBGP, all else being equal.
C.A route with a longer AS_PATH is preferred over a route with a shorter AS_PATH.
D.The MED attribute is always compared regardless of the AS of the neighbor.
E.The IGP metric to the next hop is the first criterion in BGP path selection.
AnswersA, B

LOCAL_PREF is evaluated early in the BGP best-path algorithm, before AS_PATH and origin. A higher value signals local preference, so the route with the greater LOCAL_PREF wins, directly satisfying the statement about preference ordering between competing paths.

Why this answer

Option A is correct because LOCAL_PREF is evaluated early in the BGP best-path algorithm (after weight and before AS_PATH), and a higher LOCAL_PREF value is always preferred over a lower one. Option B is correct because, all other attributes being equal, eBGP-learned routes are preferred over iBGP-learned routes, since eBGP routes are considered more trustworthy and are evaluated before the IGP metric tiebreaker. Option C is incorrect because BGP prefers the shorter AS_PATH, not the longer one, to minimize the number of autonomous systems traversed.

Option D is incorrect because MED is only compared between routes from the same neighboring AS by default (unless bgp always-compare-med is configured). Option E is incorrect because the IGP metric to the next hop is one of the last tiebreakers in the BGP path selection process, not the first criterion.

38
MCQhard

A network engineer is deploying Control Plane Policing (CoPP) on a Cisco IOS XE router. The router runs BGP, OSPF, SSH management, and SNMP. After applying a CoPP policy that rate-limits all control-plane traffic to 1000 pps, BGP sessions flap and OSPF adjacencies reset during peak traffic. Which action should the engineer take to resolve the problem while maintaining control-plane protection?

A.Create separate class-maps for BGP, OSPF, SSH, and SNMP, and apply protocol-specific rate limits within the policy-map.
B.Enable Control Plane Protection (CPPr) with the aggregate option to automatically prioritize routing protocols.
C.Increase the global CoPP rate limit to 5000 pps to accommodate all control-plane protocols.
D.Remove the CoPP policy from the control plane and rely on QoS policies on data interfaces instead.
AnswerA

CoPP works by classifying traffic into distinct classes and applying individual policers. Creating separate class-maps for each protocol allows the engineer to set appropriate rates for BGP and OSPF while still policing SSH and SNMP. This targeted approach protects the control plane without starving routing protocols, resolving the flapping while maintaining security.

Why this answer

CoPP uses a modular QoS CLI (MQC) structure with class-maps to identify traffic types and a policy-map to apply policers per class. A single policer for all control-plane traffic causes legitimate routing protocol updates to compete with management and monitoring traffic, leading to drops and session resets. The correct solution is to define separate class-maps for BGP, OSPF, SSH, and SNMP, then assign differentiated rate limits in the policy-map.

This preserves control-plane protection while ensuring routing protocols receive adequate bandwidth.

Exam trap

The trap here is treating CoPP as a single-rate mechanism and either removing it or inflating the global limit instead of using granular per-protocol classification, which is the intended design.

39
Drag & Dropmedium

Drag and drop the steps of MP-BGP VPNv4 route advertisement between PE routers into the correct order, from first to last.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5

Why this order

The correct order starts with the PE learning the customer route via IGP or static, then redistributing it into MP-BGP as a VPNv4 route with a route distinguisher, advertising it to the other PE via MP-BGP update, the receiving PE importing the route based on matching route targets, and finally installing the route into the appropriate VRF.

40
MCQmedium

Consider the following configuration: router bgp 65000 bgp router-id 192.168.0.1 neighbor 10.0.0.2 remote-as 65001 neighbor 10.0.0.2 ebgp-multihop 2 neighbor 10.0.0.2 update-source Loopback0 ! interface Loopback0 ip address 192.168.0.1 255.255.255.255 What is missing for this BGP session to establish?

A.A route to reach 10.0.0.2 is missing; the neighbor must be reachable via the routing table.
B.The ebgp-multihop value should be 1 for a directly connected neighbor.
C.The remote-as must be the same as the local AS for EBGP.
D.The router-id must be the same as the update-source interface IP.
AnswerA

BGP establishes sessions over TCP port 179, so the router must have a valid route to 10.0.0.2 in its IPv4 unicast routing table before attempting the connection. Without that route, packets destined for the neighbor are dropped, the TCP three-way handshake never completes, and the BGP session remains Idle. This would happen even if the neighbor has reachability to this router, because BGP requires bidirectional IP reachability.

Why this answer

For an eBGP session to establish, the neighbor IP address (10.0.0.2) must be reachable via the routing table. The configuration uses `ebgp-multihop 2` and an update-source of Loopback0, but there is no route (static or dynamic) to reach 10.0.0.2, so the TCP connection cannot be initiated. Without reachability, BGP will remain in the Idle state.

Exam trap

Cisco often tests the misconception that ebgp-multihop alone ensures connectivity, but the trap here is that candidates forget BGP requires IP reachability in the routing table for the neighbor address, not just a configured multihop value.

How to eliminate wrong answers

Option B is wrong because ebgp-multihop 2 is correctly used when the neighbor is not directly connected (e.g., using loopback interfaces); setting it to 1 would assume a directly connected interface, which is not the case here. Option C is wrong because for eBGP, the remote-as must be different from the local AS (65000 vs 65001), so stating it must be the same is incorrect. Option D is wrong because the router-id does not need to match the update-source interface IP; the router-id is used for BGP identifier purposes and can be any unique IP, while the update-source specifies which interface's IP to use for the TCP connection.

41
MCQhard

A network engineer is implementing VXLAN with BGP EVPN on Cisco Nexus switches. The underlay network is OSPF, and the overlay uses MP-BGP EVPN. The engineer wants to ensure that the VXLAN tunnel endpoints (VTEPs) can discover each other and exchange MAC and IP address information. Which statement correctly describes the role of the BGP EVPN address family in this scenario?

A.It provides a routing underlay for the VXLAN tunnels by advertising VTEP loopback addresses.
B.It synchronizes the MAC address tables of all VTEPs by flooding unknown unicast traffic.
C.It encapsulates the original Ethernet frames into VXLAN packets and forwards them across the underlay.
D.It distributes MAC and IP address reachability information for hosts and enables VTEP peer discovery.
AnswerD

The BGP EVPN address family carries MAC and IP address reachability information in the form of EVPN routes, such as Type 2 and Type 5 routes. This allows VTEPs to learn about remote hosts and VTEPs, facilitating the creation of VXLAN tunnels and enabling efficient forwarding without flooding.

Why this answer

The BGP EVPN address family is used to distribute MAC and IP address reachability information across VTEPs. This enables control plane learning, reducing flooding and allowing VTEPs to discover remote hosts and VTEPs. The other options incorrectly attribute underlay routing, data plane encapsulation, or flooding-based learning to BGP EVPN.

Exam trap

The trap here is assuming that BGP EVPN handles encapsulation or underlay routing, when it is actually an overlay control plane protocol for distributing host reachability.

42
MCQmedium

A network engineer is deploying Control Plane Policing on a Cisco IOS-XE router that runs OSPF, BGP, and SSH management. The engineer wants to rate-limit routing protocol traffic while ensuring that SSH management traffic is never dropped, even during a routing protocol flood. The router uses a single physical interface for all control plane traffic. Which CoPP design approach best meets these requirements?

A.Create separate class-maps for OSPF, BGP, and SSH, then apply individual policers to each class in the policy-map, with SSH assigned a higher rate or set to conform-action transmit.
B.Use a single class-map for OSPF and BGP, and rely on SSH being exempt because it is TCP-based and not subject to CoPP.
C.Configure CoPP only on the management interface and leave the data interfaces unprotected.
D.Apply a single class-map matching all control plane traffic and set a single policer with a high rate limit.
AnswerA

Creating separate class-maps allows the engineer to apply distinct policers to each traffic type. By giving SSH a higher rate limit or configuring it to always transmit, management access is protected. OSPF and BGP can be rate-limited independently to prevent control plane overload. This granular approach is the recommended CoPP design for protecting critical management traffic.

Why this answer

Separate class-maps for OSPF, BGP, and SSH allow individual policing actions. Assigning SSH a higher rate or conform-action transmit ensures management access is preserved during routing protocol floods. This granular CoPP design protects both routing stability and administrative access, which is the core goal of control plane policing.

Exam trap

The trap here is assuming that SSH management traffic is automatically exempt from CoPP because it is TCP-based, when in fact all control plane traffic is subject to the policy-map.

43
Multi-Selecthard

Which three statements about BGP route reflectors are true? (Choose three.)

Select 3 answers
A.Route reflectors allow iBGP speakers to advertise routes learned from other iBGP speakers without requiring a full mesh.
B.A route reflector client must be fully meshed with all other clients in the same cluster.
C.The route reflector can be a client of another route reflector.
D.The cluster ID is used to prevent routing loops in a route reflector environment.
E.The route reflector modifies the AS_PATH attribute to prevent loops.
AnswersA, C, D

Route reflection removes the iBGP full-mesh requirement: the reflector re-advertises routes learned from one client to other clients and non-clients. This directly satisfies the scalability constraint of avoiding a full mesh between all iBGP speakers.

Why this answer

Option A is correct because a route reflector relaxes the iBGP full-mesh requirement by reflecting routes learned from one iBGP peer to other iBGP peers (its clients and non-clients), so speakers no longer need direct sessions with every other iBGP speaker. Option C is correct because route reflectors can be arranged in a hierarchy: a route reflector can itself be a client of a higher-level route reflector, allowing large ASes to scale beyond a single cluster. Option D is correct because the CLUSTER_ID attribute (a 4-byte value, often derived from the router ID) identifies the cluster and lets a route reflector detect and drop routes that have already been reflected, preventing loops within the cluster.

Option B is not correct because route reflector clients do not need to be fully meshed with each other; they only peer with the route reflector, which is the whole point of the design. Option E is not correct because loop prevention in route reflection is handled by ORIGINATOR_ID and CLUSTER_ID (and CLUSTER_LIST), not by modifying AS_PATH, which is used for inter-AS loop prevention in eBGP.

Exam trap

350-401 often tests the misconception that route reflectors modify AS_PATH for loop prevention; the correct mechanisms are ORIGINATOR_ID and CLUSTER_LIST.

44
MCQmedium

A network engineer is configuring a Cisco Nexus 9000 switch as a VTEP in a VXLAN EVPN fabric. The engineer wants to ensure that the switch uses the loopback0 interface as the source for VXLAN tunnels and that it can dynamically learn remote VTEPs via BGP EVPN. Which command set is required under the NVE interface?

A.interface nve1; source-interface loopback0; vni 10000; ip address 10.0.0.1/32
B.interface nve1; source-interface loopback0; no shutdown
C.interface nve1; source-interface loopback0; peer-ip 10.0.0.2
D.interface nve1; source-interface loopback0; host-reachability protocol bgp
AnswerD

Under the NVE interface, source-interface loopback0 sets the VTEP IP address, and host-reachability protocol bgp enables BGP EVPN for remote VTEP and MAC learning. This combination is essential for a functioning VTEP in an EVPN fabric. Without the source-interface, the NVE would not know which IP to use for tunnels, and without host-reachability, it would rely on data-plane learning.

Why this answer

For a Cisco Nexus 9000 VTEP in an EVPN fabric, the NVE interface must be configured with source-interface loopback0 to set the tunnel source IP and host-reachability protocol bgp to enable dynamic learning of remote VTEPs and MAC addresses via BGP EVPN. Other commands like no shutdown are necessary but insufficient, and static peer-ip or IP address under NVE is incorrect.

Exam trap

The trap here is forgetting the host-reachability protocol bgp command, which is often overlooked when focusing only on the source-interface configuration.

45
MCQhard

A network engineer is configuring Control Plane Policing (CoPP) on a Cisco IOS XE router to protect against DoS attacks. The router has a management plane that includes SSH and SNMP, and a control plane that includes routing protocols like OSPF and BGP. The engineer wants to rate-limit traffic destined to the route processor while ensuring that management traffic is not dropped during high CPU load. Which CoPP configuration approach is most appropriate?

A.Configure separate classes for management traffic (SSH, SNMP) and control plane traffic (OSPF, BGP), and assign higher rate limits to management traffic.
B.Use a single class that matches all IP traffic and set a high rate limit to avoid dropping any packets.
C.Apply a single CoPP policy that classifies all traffic to the route processor and sets a low rate limit for all classes.
D.Configure CoPP only for routing protocols and rely on QoS for management traffic.
AnswerA

This is the best practice. By creating separate classes, the engineer can apply different rate limits. Management traffic should have a higher rate limit to ensure administrators can always access the device, while control plane protocols can have lower limits to protect the route processor. This granularity ensures that critical management access is not starved during an attack, and routing protocols are still protected but not at the expense of management access.

Why this answer

CoPP allows granular control over traffic destined to the route processor. By separating management and control plane traffic into different classes, the engineer can assign higher rate limits to management traffic to ensure administrative access is maintained, while still protecting the route processor from excessive control plane traffic. This approach balances security and availability, preventing both DoS attacks and administrator lockout.

Exam trap

The trap here is assuming that a single CoPP policy with a uniform rate limit is sufficient, overlooking the need to prioritize management traffic to prevent lockout during an attack.

46
MCQmedium

Given the following SD-WAN configuration on a Cisco IOS-XE router: router ospf 1 redistribute bgp 65000 subnets network 192.168.1.0 0.0.0.255 area 0 ! interface GigabitEthernet0/0/0 ip address 192.168.1.1 255.255.255.0 ip ospf network point-to-point ! Which statement is true?

A.The OSPF network type is point-to-point, so the hello interval defaults to 10 seconds on this interface.
B.The OSPF network type is point-to-point, so the dead interval defaults to 120 seconds.
C.The redistribution of BGP into OSPF will cause OSPF to advertise all BGP routes, including those learned via SD-WAN overlay.
D.The configuration is incomplete because OSPF requires a router-id to be manually configured.
AnswerA

On a point-to-point OSPF network type, Cisco's default hello interval is 10 seconds, identical to the default on broadcast networks. This is because both network types use the same timer defaults on Cisco IOS, and the dead interval is then calculated as 4 × 10 = 40 seconds. Since the option specifically addresses the hello interval, it is correct.

Why this answer

On a Cisco IOS-XE router, when the OSPF network type is set to point-to-point, the default hello interval is 10 seconds (not 30 seconds as on broadcast networks). The dead interval defaults to 40 seconds (four times the hello interval), not 120 seconds. This configuration is valid and does not require a manually configured router-id, as OSPF can dynamically select one.

The redistribution of BGP into OSPF only injects routes that are in the BGP table; it does not automatically include all SD-WAN overlay routes unless they are present in BGP.

Exam trap

Cisco often tests the default OSPF timer values for different network types, specifically tricking candidates into thinking point-to-point uses 30-second hello or 120-second dead intervals, which are actually defaults for NBMA networks.

How to eliminate wrong answers

Option B is wrong because the OSPF dead interval for a point-to-point network defaults to 40 seconds (4 × hello interval of 10 seconds), not 120 seconds. Option C is wrong because the 'redistribute bgp 65000 subnets' command only redistributes BGP routes that are in the BGP routing table; it does not automatically advertise all SD-WAN overlay routes unless they are learned via BGP and meet redistribution criteria (e.g., subnets keyword includes classless prefixes). Option D is wrong because OSPF does not require a manually configured router-id; if none is configured, OSPF automatically selects the highest IP address on a loopback interface or the highest IP address on any active physical interface.

47
MCQmedium

router bgp 65000 bgp router-id 10.0.0.1 neighbor 10.0.0.2 remote-as 65001 neighbor 10.0.0.2 route-map SET_COMMUNITY in ! route-map SET_COMMUNITY permit 10 set community 100:200 ! What is the effect of this configuration?

A.Routes received from 10.0.0.2 are tagged with community 100:200, but the community is not sent to other BGP peers unless send-community is configured.
B.Routes received from 10.0.0.2 are tagged with community 100:200 and automatically sent to all neighbors.
C.The route-map is applied to outbound updates to 10.0.0.2, setting community on routes sent to that neighbor.
D.The configuration is invalid because the community must be a string, not a numeric value.
AnswerA

This is correct because the route-map 'bgp' is applied inbound from neighbor 10.0.0.2, and it sets the community 100:200 on all received routes. However, BGP does not include community attributes in updates to other peers unless the neighbor is explicitly configured with the send-community parameter. Without send-community, the routes are advertised but the community attribute is stripped, so it never propagates beyond the local router.

Why this answer

The route-map SET_COMMUNITY is applied to inbound updates from neighbor 10.0.0.2, so routes received from that neighbor are tagged with community 100:200. However, BGP does not propagate communities to other peers unless the neighbor is explicitly configured with the send-community command. Without send-community, the community attribute is stripped from outbound updates, so the community is not sent to other BGP peers.

Exam trap

Cisco often tests the distinction between inbound and outbound route-map application, and the fact that communities are not automatically sent to peers without explicit send-community configuration, leading candidates to assume the community is propagated by default.

How to eliminate wrong answers

Option B is wrong because BGP does not automatically send communities to all neighbors; the send-community command is required under the neighbor configuration for the community attribute to be included in outbound updates. Option C is wrong because the route-map is applied with the 'in' keyword, meaning it affects inbound routes from 10.0.0.2, not outbound updates to that neighbor. Option D is wrong because the community value 100:200 is a valid numeric format (AS:value) and is perfectly acceptable in BGP configuration.

48
MCQmedium

Examine the following BGP configuration on a Cisco IOS-XE router: ``` router bgp 65000 bgp default local-preference 150 neighbor 10.1.1.1 remote-as 65001 neighbor 10.1.1.1 password cisco123 neighbor 10.1.1.1 route-map SET-MED out ! route-map SET-MED permit 10 set metric 50 ``` What is the effect of the route-map on outbound updates to 10.1.1.1?

A.The MED value of routes advertised to 10.1.1.1 is set to 50.
B.The local preference of routes received from 10.1.1.1 is set to 150.
C.The route-map filters routes; only those with metric 50 are advertised.
D.The password is applied to the BGP session, but the route-map is ignored due to the password.
AnswerA

This route-map is applied to BGP routes before they are sent to the peer, and it explicitly uses a set command that assigns the Multi-Exit Discriminator (MED) value of 50 to all advertised routes. MED is a non-transitive BGP attribute that influences the peer's inbound path selection, with a lower value preferred over a higher one. Therefore, the statement is correct: the MED of routes advertised to 10.1.1.1 is set to 50.

Why this answer

The route-map SET-MED is applied to outbound updates to neighbor 10.1.1.1 using the 'route-map SET-MED out' command. The route-map permits all routes (no match statement) and sets the MED (Multi-Exit Discriminator) attribute to 50. This means that when the local router advertises routes to this eBGP neighbor, the MED value in those updates will be 50, influencing the neighbor's inbound path selection.

Exam trap

Cisco often tests the distinction between 'route-map out' (affects outbound updates) and 'route-map in' (affects inbound updates), and the trap here is assuming the route-map filters routes when it actually sets an attribute without any match conditions.

How to eliminate wrong answers

Option B is wrong because the 'bgp default local-preference 150' command sets the default local preference for routes received from all eBGP peers, not just 10.1.1.1, and the route-map does not affect local preference. Option C is wrong because the route-map has no match clause, so it permits all routes; it does not filter based on metric 50—it sets the metric to 50 on all advertised routes. Option D is wrong because the password and route-map are independent configurations; the route-map is not ignored due to the password—both are applied correctly.

49
MCQhard

An enterprise has two BGP routers, R1 and R2, both in AS 65000. R1 peers with ISP1 (AS 100) and R2 peers with ISP2 (AS 200). The enterprise advertises a prefix 192.168.0.0/24 to both ISPs. The engineer wants to ensure that traffic from the Internet to this prefix enters the network primarily via R1, and only uses R2 if the link to ISP1 fails. Which BGP attribute should be manipulated on the updates sent to the ISPs?

A.Prepend AS 65000 multiple times on R2's updates to ISP2.
B.Set a higher MED on R1's updates to ISP1.
C.Set a higher local preference on R1 for routes learned from ISP1.
D.Use the no-export community on R1's updates to ISP1.
AnswerA

AS_PATH prepending artificially lengthens the AS path by adding multiple copies of the enterprise's ASN (65000) to the prefix advertised to ISP2. Because ISP2's BGP best-path algorithm compares AS_PATH length among equal-preference routes, the path through R2 appears longer than the same prefix advertised via ISP1's shorter AS path. This induces ISP2 to select the ISP1 route for inbound traffic, thereby directing traffic to R1 as intended. It is a standard, lightweight technique that only changes how ISPs view the return path, without affecting outbound routing.

Why this answer

To influence inbound traffic from the Internet, you must manipulate attributes sent to the ISPs. AS path prepending makes a route appear less preferred by artificially lengthening the AS path. By prepending AS 65000 multiple times on R2's updates to ISP2, ISP2 will see a longer AS path for the prefix and prefer the shorter path via ISP1, causing traffic to enter primarily via R1 unless the ISP1 link fails.

Exam trap

Cisco often tests the distinction between attributes that influence inbound vs. outbound traffic; the trap here is confusing local preference (outbound) with AS path prepending (inbound), leading candidates to incorrectly choose local preference manipulation.

How to eliminate wrong answers

Option B is wrong because MED is a metric exchanged between ASes to influence inbound traffic from a neighboring AS, but it is only compared when paths come from the same neighboring AS; here ISP1 and ISP2 are different ASes, so MED would not be compared. Option C is wrong because local preference is an attribute used within an AS to influence outbound traffic, not sent to external peers; setting it on R1 for routes learned from ISP1 affects R1's choice of exit path, not how ISPs send traffic inbound. Option D is wrong because the no-export community prevents a route from being advertised to any eBGP peers beyond the immediate neighbor; using it on R1's updates to ISP1 would block the prefix from being propagated further, which is unrelated to influencing inbound path preference.

50
MCQhard

A network administrator is implementing Control Plane Policing (CoPP) on a Cisco ASR 1000 router to protect against DoS attacks. The router has a management plane that must remain accessible via SSH and SNMP, and a control plane that must process BGP and OSPF routing updates. The administrator applies a CoPP policy that rate-limits all traffic destined to the control plane to 1000 pps, except for traffic from trusted management subnets. After applying the policy, BGP sessions flap intermittently. What is the most likely cause?

A.The CoPP policy is rate-limiting BGP keepalives and updates, causing session timeouts.
B.The CoPP policy is applied to the data plane instead of the control plane, causing routing updates to be dropped.
C.The CoPP policy is incorrectly classifying SSH traffic as BGP, leading to rate limiting of SSH.
D.The CoPP policy is dropping SNMP traps, causing BGP to lose its peer state.
AnswerA

CoPP policies that apply a blanket rate limit to all control plane traffic can inadvertently throttle essential routing protocol messages like BGP keepalives and updates. If the rate limit is too low or not exempting BGP, sessions may flap due to missed keepalives or delayed updates. The policy must be fine-tuned to allow sufficient bandwidth for routing protocols.

Why this answer

CoPP policies must be carefully designed to avoid throttling critical control plane protocols. A blanket rate limit of 1000 pps may be insufficient for BGP, especially if there are many peers or frequent updates. BGP keepalives are sent every 60 seconds by default, but updates and other messages can burst.

If the policer drops these, sessions can flap. The correct approach is to create granular class-maps that match BGP and other routing protocols, and assign appropriate rates or exempt them from policing.

Exam trap

The trap here is assuming that a single rate limit for all control plane traffic is safe, without considering the specific needs of routing protocols like BGP.

51
MCQhard

A network engineer runs the following command on Router R1: R1# show policy-map control-plane Control Plane Service-policy input: CoPP-POLICY Class-map: BGP-CLASS (match-all) 50 packets, 2500 bytes 5 minute offered rate 500 bps Match: access-group name BGP-ACL police: cir 64000 bps, bc 8000 bytes, be 8000 bytes conformed 50 packets, 2500 bytes; actions: transmit exceeded 0 packets, 0 bytes; actions: drop violated 0 packets, 0 bytes; actions: drop Class-map: SNMP-CLASS (match-all) 200 packets, 10000 bytes 5 minute offered rate 2000 bps Match: access-group name SNMP-ACL police: cir 16000 bps, bc 2000 bytes, be 2000 bytes conformed 150 packets, 7500 bytes; actions: transmit exceeded 40 packets, 2000 bytes; actions: drop violated 10 packets, 500 bytes; actions: drop Class-map: class-default (match-any) 100 packets, 5000 bytes 5 minute offered rate 1000 bps Match: any police: cir 32000 bps, bc 4000 bytes, be 4000 bytes conformed 100 packets, 5000 bytes; actions: transmit exceeded 0 packets, 0 bytes; actions: drop violated 0 packets, 0 bytes; actions: drop Based on this output, what can be concluded?

A.SNMP traffic to the control plane is experiencing drops due to exceeding its policer rate, while BGP traffic is within its rate.
B.BGP traffic is being dropped because it exceeds the CIR.
C.All traffic to the control plane is being dropped.
D.The control-plane policy is applied in the output direction.
AnswerA

The SNMP-CLASS policer shows 40 exceeded and 10 violated packets dropped against its 16000 bps CIR, while BGP-CLASS reports zero exceeded and zero violated with all 50 packets conformed and transmitted, confirming BGP stayed within its 64000 bps rate.

Why this answer

The output shows that for the SNMP-CLASS, 40 packets exceeded and 10 packets violated the policer, resulting in drops, while the BGP-CLASS had 0 exceeded and 0 violated packets, meaning all BGP traffic conformed to its CIR of 64000 bps. This confirms that SNMP traffic is being dropped due to exceeding its policer rate, while BGP traffic is within its rate.

Exam trap

The trap here is that candidates may misinterpret the 'exceeded' and 'violated' counters as indicating that all traffic in a class is being dropped, when in fact only packets that exceed the policer thresholds are dropped, while conforming traffic is still transmitted.

How to eliminate wrong answers

Option B is wrong because the BGP-CLASS shows 0 exceeded and 0 violated packets, indicating no drops; it is not exceeding its CIR. Option C is wrong because the output shows that conformed packets for all classes are being transmitted, so not all traffic is dropped. Option D is wrong because the command 'show policy-map control-plane' and the output explicitly state 'Service-policy input: CoPP-POLICY', meaning the policy is applied in the input direction, not output.

52
MCQhard

A network engineer runs the following command on Router R1: R1# show ip bgp summary BGP router identifier 10.0.0.1, local AS number 65001 BGP table version is 10, main routing table version 10 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 192.168.1.2 4 65002 1024 1020 10 0 0 02:30:15 5 192.168.1.3 4 65003 500 498 10 0 0 00:15:20 3 10.0.0.2 4 65004 0 0 0 0 0 never Active Based on this output, what can be concluded?

A.All BGP neighbors are fully established.
B.The BGP session to 10.0.0.2 is down due to a TCP connection issue.
C.The BGP session to 192.168.1.3 has been up for 2 hours 30 minutes.
D.The router is receiving prefixes from all neighbors.
AnswerB

The BGP session to 10.0.0.2 is down due to a TCP connection issue. The Active state indicates that the local router is attempting to initiate a TCP connection to 10.0.0.2 but has not received a successful three-way handshake—either the remote peer is unreachable, a firewall is blocking TCP port 179, or the remote BGP process is not responding. Until the TCP session is established, BGP cannot exchange routes, which is why 0 prefixes are received and the session remains down.

Why this answer

The BGP session to neighbor 10.0.0.2 is in the 'Active' state with 'never' uptime and zero messages sent/received. This indicates that the router is actively trying to establish a TCP connection (port 179) but has not yet succeeded, typically due to a connectivity issue such as an unreachable IP, ACL blocking, or incorrect neighbor configuration. The 'Active' state specifically means the BGP process is waiting for the TCP connection to complete, confirming a TCP-level problem.

Exam trap

Cisco often tests the distinction between 'Active' and 'Idle' states—candidates may confuse 'Active' as meaning the session is up or partially up, but 'Active' specifically indicates a TCP connection failure, not a BGP configuration error like wrong AS number (which would cause 'Idle').

How to eliminate wrong answers

Option A is wrong because the neighbor 10.0.0.2 is in 'Active' state, not 'Established', so not all BGP neighbors are fully established. Option C is wrong because the 'Up/Down' column shows 02:30:15 for neighbor 192.168.1.2, not 192.168.1.3, which has an uptime of 00:15:20. Option D is wrong because the router is receiving prefixes only from the two established neighbors (5 and 3 prefixes), but the neighbor 10.0.0.2 has zero prefixes received (State/PfxRcd is blank), so it is not receiving prefixes from all neighbors.

53
MCQmedium

Examine the following BGP configuration: router bgp 65001 bgp log-neighbor-changes neighbor 10.1.1.1 remote-as 65002 neighbor 10.1.1.1 route-map SET_MED out ! route-map SET_MED permit 10 set metric 50 What is the purpose of this configuration?

A.It sets the MED value to 50 for all routes sent to the neighbor 10.1.1.1.
B.It sets the local preference to 50 for routes received from the neighbor.
C.It filters routes with a metric of 50 from being advertised to the neighbor.
D.It sets the weight to 50 for routes learned from the neighbor.
AnswerA

The route-map is applied in the outbound direction for neighbor 10.1.1.1, and the set metric command sets the BGP MED (Multi-Exit Discriminator) value to 50 for every permitted route. Because the route-map contains a permit statement without a restrictive match clause, all routes advertised to this neighbor carry MED 50. This influences the neighbor's inbound path selection, preferring lower MED values, so routes with MED 50 may be less preferred than routes with lower MED from other peers.

Why this answer

The configuration applies a route-map named SET_MED to outbound updates toward neighbor 10.1.1.1. The route-map permits all routes (no match statement) and sets the Multi-Exit Discriminator (MED) to 50. MED is a BGP path attribute that influences inbound traffic from the neighbor AS, making this path less preferred if the neighbor has a lower MED from another entry point.

Thus, all routes sent to 10.1.1.1 will carry a MED of 50.

Exam trap

Cisco often tests the distinction between BGP path attributes (MED vs. local preference vs. weight) and the direction in which they are applied (inbound vs. outbound), causing candidates to confuse 'set metric' with 'set local-preference' or 'set weight'.

How to eliminate wrong answers

Option B is wrong because local preference is set using the 'set local-preference' command in a route-map, and it applies to inbound updates, not outbound; the configuration here uses 'set metric' (MED) on outbound updates. Option C is wrong because the route-map is configured with 'permit' and no match condition, so it does not filter routes; it modifies the MED attribute of all advertised routes, not filtering based on metric. Option D is wrong because weight is a Cisco-proprietary attribute set with 'set weight' in a route-map, and it applies to inbound updates; this configuration sets MED on outbound updates, not weight.

54
MCQmedium

A network administrator is deploying Control Plane Policing (CoPP) on a Cisco IOS XE router that runs BGP, SSH, and NTP. The requirement is to protect the route processor from excessive BGP keepalive traffic while still allowing all legitimate BGP peering. Which CoPP module should the administrator use to classify and police this traffic before the policy is applied to the control plane?

A.A class map that matches BGP traffic using an ACL or NBAR, referenced by a policy map, which is then applied with the service-policy command under control-plane configuration mode.
B.A route map applied inbound on the BGP neighbor session that sets a lower precedence for keepalive packets.
C.A class map referenced by a policy map that is applied outbound on the WAN interface toward the BGP peer.
D.An access list applied directly to the physical interface facing the BGP peer using the ip access-group command.
AnswerA

CoPP on IOS XE uses a modular QoS CLI structure: class maps identify control-plane traffic, a policy map defines policing actions, and the policy is attached to the control plane with service-policy under control-plane mode. Matching BGP via ACL or NBAR lets the administrator police keepalives while permitting other BGP flows, which satisfies the stated requirement.

Why this answer

Control Plane Policing requires a modular QoS configuration: class maps to identify traffic, a policy map to define policer actions, and the service-policy command applied under control-plane configuration mode. This structure allows BGP keepalives to be matched and policed while other traffic is handled separately, directly protecting the route processor as the scenario requires.

Exam trap

The trap here is assuming a route map or interface ACL can police traffic destined to the route processor, when CoPP specifically requires a policy map attached to the control plane.

55
MCQmedium

router bgp 65000 bgp router-id 10.0.0.1 neighbor 10.0.0.2 remote-as 65001 neighbor 10.0.0.2 route-map SET_MED out ! route-map SET_MED permit 10 set metric 50 ! What is the effect of this configuration on routes advertised to 10.0.0.2?

A.All routes sent to 10.0.0.2 will have the MED value set to 50.
B.Routes received from 10.0.0.2 will have their MED set to 50.
C.The local preference of routes sent to 10.0.0.2 is set to 50.
D.The configuration is invalid because MED cannot be set on outbound updates.
AnswerA

With the route-map applied to the neighbor in the outbound direction, every BGP route that is being advertised toward 10.0.0.2 is processed through the 'set metric 50' command. This sets the MULTI_EXIT_DISC (MED) attribute to 50 on those advertised routes, thereby signaling the external peer that this path is more preferred for incoming traffic. Since the direction is explicitly 'out', the policy applies only to updates leaving the router toward 10.0.0.2.

Why this answer

The route-map SET_MED is applied to outbound updates to neighbor 10.0.0.2, and the 'set metric 50' command sets the Multi-Exit Discriminator (MED) attribute to 50 for all routes advertised to that neighbor. The MED is a metric used to influence inbound traffic from the AS of the neighbor, and it is propagated to the neighbor's BGP table.

Exam trap

Cisco often tests the distinction between outbound and inbound route-map application, and the trap here is confusing the 'set metric' command (which sets MED) with 'set local-preference' or assuming that MED cannot be set on outbound updates.

How to eliminate wrong answers

Option B is wrong because the route-map is applied to outbound updates ('out'), not inbound updates, so it does not affect routes received from 10.0.0.2. Option C is wrong because the 'set metric' command sets the MED, not the local preference; local preference is set using 'set local-preference' and is used for outbound traffic within the local AS. Option D is wrong because the configuration is valid; MED can be set on outbound updates using a route-map with the 'set metric' command, and this is a common practice for influencing path selection in neighboring ASes.

56
MCQmedium

router bgp 65000 bgp router-id 10.0.0.1 neighbor 10.0.0.2 remote-as 65001 neighbor 10.0.0.2 route-map SET_ORIGIN in ! route-map SET_ORIGIN permit 10 set origin incomplete ! What is the effect of this configuration?

A.Routes received from 10.0.0.2 will have their origin set to incomplete, making them less preferred compared to IGP origin.
B.Routes sent to 10.0.0.2 will have their origin set to incomplete.
C.The router will not advertise any routes with origin incomplete to other peers.
D.The configuration is invalid because origin cannot be changed with a route-map.
AnswerA

A route-map applied in the inbound direction to neighbor 10.0.0.2 will process received BGP updates and modify their origin attribute to incomplete (value 2). Since origin is a well-known mandatory attribute considered during best-path selection, incomplete is less preferred than IGP (0) or EGP (1). This makes the route less attractive within BGP path selection.

Why this answer

The route-map SET_ORIGIN is applied as an inbound filter to neighbor 10.0.0.2. When a route is received, the 'set origin incomplete' command changes the origin attribute to incomplete (value 2). In BGP path selection, origin incomplete is the least preferred origin type, making these routes less preferred than routes with IGP (value 0) or EGP (value 1) origin.

Exam trap

Cisco often tests the directionality of route-maps (in vs out) and the fact that origin can be modified with a route-map, leading candidates to mistakenly think the route-map applies to outbound updates or that origin is immutable.

How to eliminate wrong answers

Option B is wrong because the route-map is applied 'in' (inbound), not 'out' (outbound), so it affects received routes, not sent routes. Option C is wrong because the configuration does not filter or suppress routes; it only modifies the origin attribute of received routes, and routes with origin incomplete can still be advertised to other peers. Option D is wrong because the origin attribute can be changed using a route-map with the 'set origin' command; this is a valid BGP configuration.

57
Drag & Dropmedium

Drag and drop the steps of BGP route aggregation and suppress-map process into the correct order, from first to last.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5

Why this order

The correct order for BGP route aggregation with suppress-map is: first, define a prefix-list to match the more-specific routes you want to suppress. Second, create a route-map with a suppress clause that references the prefix-list. Third, configure the aggregate-address in BGP under the address-family.

Fourth, apply the suppress-map to the aggregate-address command (typically as part of the aggregate-address command itself). Finally, verify the summary route and the suppressed routes.

58
MCQmedium

router bgp 65000 bgp router-id 10.0.0.1 neighbor 10.0.0.2 remote-as 65001 neighbor 10.0.0.2 route-map FILTER in ! route-map FILTER deny 10 match ip address prefix-list BLOCKED route-map FILTER permit 20 ! ip prefix-list BLOCKED seq 5 permit 10.0.0.0/8 ! What is the effect of this configuration?

A.All routes from neighbor 10.0.0.2 are accepted except those matching 10.0.0.0/8.
B.Only routes matching 10.0.0.0/8 are accepted from the neighbor.
C.The configuration is invalid because route-map must have a permit statement first.
D.The prefix-list is misconfigured because it should use 'deny' instead of 'permit'.
AnswerA

The route-map is evaluated in ascending sequence order, and each BGP route is checked against the clauses. The first clause is a deny statement that matches the prefix-list for 10.0.0.0/8, so any route within that aggregate is rejected. The subsequent permit clause with no match conditions acts as a catch-all, allowing every other route. Thus, only routes that fall under 10.0.0.0/8 are filtered, while all other prefixes from the neighbor are accepted.

Why this answer

The route-map FILTER is applied inbound from neighbor 10.0.0.2. Sequence 10 denies routes that match the prefix-list BLOCKED, which permits 10.0.0.0/8. Sequence 20 is a permit statement with no match, which implicitly permits all other routes.

Therefore, only routes matching 10.0.0.0/8 are denied, and all other routes are accepted.

Exam trap

Cisco often tests the interaction between route-map sequence numbers and the implicit deny at the end of a route-map, leading candidates to forget that a permit statement with no match (like sequence 20) is needed to allow all other routes through.

How to eliminate wrong answers

Option B is wrong because the configuration denies routes matching 10.0.0.0/8, not accepts them. Option C is wrong because route-maps can start with a deny statement; there is no requirement for the first statement to be permit. Option D is wrong because the prefix-list uses 'permit' to define which prefixes are matched by the route-map's deny clause; using 'deny' in the prefix-list would not match the intended prefixes.

59
Matchingmedium

Drag and drop each BGP attribute on the left to the value that is preferred (highest or lowest) during path selection on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Highest

Highest

Lowest

Lowest

Lowest

Why these pairings

Higher weight is preferred; higher LOCAL_PREF is preferred; shorter AS_PATH length is preferred; lower MULTI_EXIT_DISC is preferred; lower IGP metric to next-hop is preferred.

60
MCQmedium

A network engineer is configuring a Cisco Nexus 9000 switch as a VXLAN Tunnel Endpoint (VTEP). The switch has two loopback interfaces: Loopback0 (10.0.0.1/32) and Loopback1 (10.0.0.2/32). The engineer wants VXLAN traffic to use the loopback interface that is also used for BGP EVPN peering. Which command should be used to specify the source interface for the VXLAN tunnels?

A.interface nve1 source-interface loopback1
B.interface loopback1 vxlan source-interface
C.interface nve1 source-interface loopback0
D.feature nv overlay source-interface loopback1
AnswerA

The 'source-interface loopback1' command under the NVE interface configuration sets Loopback1 as the source for all VXLAN encapsulated traffic. Since Loopback1 is also used for BGP EVPN peering, this ensures consistent reachability and avoids asymmetric routing. This is the correct way to bind the VTEP source to a specific loopback, which is a common best practice in VXLAN EVPN deployments.

Why this answer

The correct configuration is to specify the source interface under the NVE interface using 'source-interface loopback1'. This binds the VTEP to the same loopback used for BGP EVPN peering, ensuring that the tunnel source address is reachable and consistent with the control plane. Using a different loopback could cause routing inconsistencies and is not recommended when the same loopback is already used for EVPN peering.

Exam trap

The trap here is confusing the global 'feature nv overlay' command with the interface-level source-interface configuration, or assuming the source interface should be configured on the loopback rather than under the NVE interface.

61
MCQhard

A network engineer is implementing Control Plane Policing (CoPP) on a Cisco IOS router to protect the route processor from excessive CPU utilization due to malicious traffic. The engineer wants to ensure that BGP, SSH, and SNMP traffic are rate-limited appropriately. After applying the CoPP policy, the engineer notices that BGP sessions are flapping. Which action should the engineer take to resolve the issue while maintaining protection?

A.Remove the CoPP policy from the control plane and apply it only to the data plane.
B.Configure a separate class-map for BGP and assign it to a higher priority queue in the policy-map.
C.Enable BGP graceful restart to prevent session flapping during CoPP drops.
D.Increase the rate limit for the class-map that matches BGP traffic.
AnswerD

BGP sessions flapping indicate that the CoPP policy is dropping legitimate BGP keepalives or updates due to an overly restrictive rate limit. Increasing the rate limit for the BGP class-map allows sufficient BGP control traffic to reach the route processor while still protecting against excessive traffic. This balances protection with operational stability.

Why this answer

BGP session flapping after applying CoPP typically occurs because the policer is dropping legitimate BGP control packets. The correct fix is to increase the rate limit for the BGP traffic class so that keepalives and updates are not dropped, while still protecting the control plane from excessive traffic. Other options either do not address the rate limit or suggest inappropriate mechanisms.

Exam trap

The trap here is thinking that CoPP uses queuing or that BGP graceful restart can prevent flapping caused by policer drops, when the real issue is an insufficient rate limit.

62
Matchingmedium

Drag and drop each MP-BGP address family on the left to its matching use case on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Carries MPLS Layer 3 VPN routes with route distinguisher and route target

Carries standard IPv4 unicast routes (non-VPN)

Carries standard IPv6 unicast routes

Carries MPLS Layer 3 VPN routes for IPv6 customer prefixes

Carries Layer 2 VPN information such as VPLS or EVPN

Why these pairings

The VPNv4 unicast address family carries MPLS VPN routes with RD and RT; IPv4 unicast carries standard IPv4 routes; IPv6 unicast carries IPv6 routes; VPNv6 unicast carries IPv6 MPLS VPN routes; L2VPN address family carries Layer 2 VPN information like VPLS.

63
MCQhard

A network administrator is configuring Control Plane Policing (CoPP) on a Cisco IOS XE router. The router runs OSPF, BGP, SSH management, and SNMP polling. After applying a CoPP policy, the administrator notices that OSPF adjacencies flap intermittently while BGP and SSH remain stable. Which action should the administrator take to resolve the flapping while maintaining control plane protection?

A.Remove the CoPP policy entirely and rely on interface ACLs for control plane protection.
B.Increase the committed information rate (CIR) for the OSPF class in the CoPP policy.
C.Apply the CoPP policy only to the BGP and SSH classes, leaving OSPF unpoliced.
D.Configure OSPF authentication to reduce the number of OSPF packets processed by the route processor.
AnswerB

OSPF hellos and LSAs are being dropped because the policer for the OSPF class is too restrictive. Increasing the CIR for that class allows more OSPF control traffic to reach the route processor, stabilizing adjacencies. This maintains protection for other protocols while addressing the specific queue that is over-policing legitimate OSPF packets during normal adjacency formation and maintenance.

Why this answer

OSPF adjacency flapping after applying CoPP indicates that the policer for the OSPF control plane class is dropping legitimate hello or LSA packets. Increasing the CIR for that class allows the required OSPF traffic to be punted to the route processor. This preserves control plane protection for other protocols while resolving the flapping, which is a common tuning step in CoPP deployments.

Exam trap

The trap here is thinking that CoPP either works or does not, when in reality each class needs to be tuned to match the protocol's legitimate traffic profile.

64
MCQmedium

A large enterprise is migrating from traditional SNMP-based monitoring to streaming telemetry for better scalability and real-time visibility. The network team has Cisco Nexus 9000 switches running NX-OS. They want to stream interface counters and BGP neighbor state changes to a collector. Which telemetry technology should they implement?

A.Configure model-driven telemetry (MDT) using gRPC or gNMI to subscribe to the desired YANG data models for interface counters and BGP state.
B.Enable NetFlow v9 on the switches and configure the collector to receive flow records that include interface statistics.
C.Use SNMP traps to send interface and BGP state changes to the collector.
D.Deploy IP SLA responders on the switches to measure performance and send results via syslog.
AnswerA

Model-driven telemetry (MDT) with gRPC or gNMI creates a persistent subscription to YANG-defined data models, allowing the NX-OS device to push interface counters and BGP state at a configured cadence or immediately on change. This push model scales to thousands of counters without collector polling overhead and supports structured encoding (protobuf/JSON), making it ideal for real-time visibility. Unlike flow or event mechanisms, MDT is purpose-built for streaming operational state from network devices.

Why this answer

Model-driven telemetry (MDT) using gRPC or gNMI is the correct choice because it provides a push-based, scalable, and real-time streaming mechanism for subscribing to specific YANG data paths, such as interface counters and BGP neighbor state, directly from Cisco Nexus 9000 switches running NX-OS. This approach eliminates the polling overhead of SNMP and supports high-frequency data collection, making it ideal for large-scale enterprise monitoring.

Exam trap

Cisco often tests the distinction between streaming telemetry (push-based, model-driven) and legacy monitoring methods like SNMP or NetFlow, where candidates mistakenly choose NetFlow because it sounds similar to 'streaming' or SNMP traps because they think 'state changes' imply event-driven traps, but the key is that MDT provides structured, scalable, and real-time data for operational state, not just flow records or performance metrics.

How to eliminate wrong answers

Option B is wrong because NetFlow v9 is designed for traffic flow analysis (e.g., IP flows, protocols, ports) and does not natively stream interface counters or BGP neighbor state changes; it focuses on network traffic metadata, not device operational state. Option C is wrong because SNMP traps are event-driven but lack the scalability and granularity of streaming telemetry; they are pull-based for counters and can miss state changes due to unreliable UDP transport, and they do not support the high-frequency, model-driven subscriptions required for real-time visibility. Option D is wrong because IP SLA responders measure network performance metrics like latency and jitter, not interface counters or BGP neighbor state; they send results via syslog, which is a log-based, non-structured method unsuitable for streaming telemetry.

65
MCQhard

A network administrator must protect the control plane of a Cisco IOS XE router that peers BGP with an ISP. The requirement is to rate-limit specifically ARP and IPv4 TTL-expired packets destined to the route processor while allowing all other transit traffic to be forwarded normally. Which CoPP implementation step is required to achieve this?

A.Enable Control Plane Protection with a port-filter policy that drops ARP and TTL-expired packets before they reach the route processor.
B.Apply an ACL directly to the BGP peer interface inbound to deny ARP and TTL-expired packets, then rely on uRPF to drop remaining control-plane traffic.
C.Configure an MQC service policy with service-policy type control-plane on the BGP-facing interface to rate-limit ARP and TTL-expired packets.
D.Create an ACL matching ARP and TTL-expired traffic, reference it in a class-map of type control-plane, define a policy-map with police actions, and attach it with service-policy type control-plane in global configuration.
AnswerD

CoPP on IOS XE requires classifying control-plane-bound traffic with a class-map of type control-plane, then applying policing in a policy-map that is attached globally with service-policy type control-plane. An ACL matching ARP and TTL-expired packets provides the specific match, and transit traffic is unaffected because CoPP only inspects packets punted to the route processor.

Why this answer

CoPP uses MQC with a class-map of type control-plane to identify traffic punted to the route processor, a policy-map to police that class, and a global service-policy type control-plane attachment. Matching ARP and TTL-expired packets with an ACL inside the class-map isolates exactly the traffic to be rate-limited, while transit traffic continues to be forwarded in hardware and is never inspected by CoPP.

Exam trap

The trap here is attaching the control-plane service policy to an interface instead of globally, which would police forwarded traffic rather than packets punted to the route processor.

66
MCQmedium

An engineer is troubleshooting an MPLS VPN where CE1 (10.1.1.0/24) cannot reach CE2 (10.2.2.0/24). The PE routers are running OSPF with the CE routers. On PE1, the 'show ip route vrf CUSTOMER' output shows 10.2.2.0/24 as an OSPF route, but the prefix is not present in the global BGP table. What is the most likely cause?

A.Redistribution from OSPF into BGP under the VRF is not configured on PE1.
B.The OSPF adjacency between PE1 and CE1 is down.
C.The VRF forwarding table on PE1 is full.
D.MPLS LDP is not enabled on the PE1-CE1 link.
AnswerA

Within an MPLS L3VPN, simply running OSPF in the VRF does not make a CE route available to the MP-BGP VPNv4 control plane. The PE must explicitly execute a redistribution command, such as 'redistribute ospf 1 vrf CUSTOMER' under 'router bgp AS ... address-family ipv4 vrf CUSTOMER'. Missing this command means the OSPF-installed route stays confined to the VRF RIB; it is never given a route distinguisher, tagged with an export route target, or sent to remote PEs. Consequently, even a healthy OSPF adjacency and populated VRF still result in no VPNv4 prefix.

Why this answer

In an MPLS VPN, the PE router must redistribute OSPF routes learned from the CE into MP-BGP under the VRF to propagate them across the MPLS backbone. Without this redistribution, the prefix 10.2.2.0/24 appears in the VRF routing table as an OSPF route but is never injected into the BGP table, so it cannot be advertised to the remote PE. This explains why CE1 cannot reach CE2 despite the route being present locally on PE1.

Exam trap

Cisco often tests the distinction between a route being present in the VRF routing table versus being present in the BGP table, trapping candidates who assume that OSPF-learned routes are automatically propagated across the MPLS VPN backbone without explicit redistribution into MP-BGP.

How to eliminate wrong answers

Option B is wrong because if the OSPF adjacency between PE1 and CE1 were down, the 10.2.2.0/24 route would not appear in the VRF routing table at all, but the question states it is present. Option C is wrong because a full VRF forwarding table would cause route installation failures or drops, not the specific symptom of a route missing from the global BGP table while present in the VRF. Option D is wrong because MPLS LDP on the PE1-CE1 link is irrelevant for MPLS VPN; LDP is used for label distribution in the core, not on the CE-facing link, and the issue is about BGP route propagation, not label switching.

67
MCQhard

A large enterprise uses a centralized automation platform based on Ansible Tower to manage its network infrastructure. The network consists of 500 Cisco IOS XE routers and switches distributed across multiple sites. The automation team has created a playbook that configures BGP peerings on all devices. The playbook uses the ios_bgp module. Recently, during a maintenance window, the playbook was run against a subset of devices that were supposed to be upgraded to a new IOS XE version. However, after the run, several devices lost their BGP configurations entirely. The team discovers that the new IOS XE version introduced a new BGP configuration model that is not fully compatible with the ios_bgp module's expected CLI commands. The playbook failed silently on those devices, and the existing BGP configuration was removed. The team needs to prevent this from happening in future maintenance windows. Which action should be taken?

A.Add a pre-task that validates the device's OS version and conditionally applies the appropriate module or command set
B.Implement idempotency checks in the playbook using the 'check_mode' option
C.Set 'gather_facts: no' in the playbook to speed up execution and avoid version detection issues
D.Replace the ios_bgp module with the ios_config module and use raw CLI commands for BGP configuration
AnswerA

Running a pre-task that inspects ansible_net_version and then uses conditional logic to select either the native ios_bgp module or an alternative module (e.g., ios_config) ensures that the playbook aligns with the device's supported API and syntax. This avoids silent failures caused by module versions that do not recognize the running IOS release, and it is the recommended pattern for maintaining idempotent, OS-aware automation across a heterogeneous fleet.

Why this answer

It directly addresses the root cause: the new IOS XE version uses an incompatible BGP configuration model. By adding a pre-task that validates the OS version, the playbook can conditionally apply the correct module (e.g., ios_bgp for older versions or a different module/CLI for the new model), preventing silent failures and configuration loss. This ensures the automation adapts to version-specific changes, maintaining idempotency and safety.

Exam trap

Cisco often tests the misconception that idempotency (check_mode) or simply using raw CLI commands (ios_config) solves version incompatibility, when the real solution is version-aware conditional logic to handle model changes.

How to eliminate wrong answers

Option B is wrong because 'check_mode' only simulates changes without applying them; it does not prevent the ios_bgp module from removing existing BGP configs due to incompatibility, nor does it handle version-specific behavior. Option C is wrong because setting 'gather_facts: no' would skip version detection entirely, making the playbook blind to the OS version and increasing the risk of applying incompatible commands. Option D is wrong because replacing ios_bgp with ios_config and raw CLI commands bypasses Ansible's structured module logic, losing idempotency and validation, and still requires version-aware logic to avoid the same incompatibility issue.

68
MCQhard

A network engineer is configuring control plane policing (CoPP) on a Cisco IOS XE router that peers BGP with two service providers and is managed over SSH from a jump host. After applying a new policy-map, the engineer notices that BGP sessions remain up but SSH logins intermittently time out during traffic spikes. Which action should the engineer take to resolve the SSH timeouts while preserving the CoPP protection model?

A.Add a class-map matching TCP port 22 traffic and attach it to the policy-map with an appropriate rate and conform/exceed actions.
B.Remove the service-policy from the control plane and rely on QoS on the data plane instead.
C.Increase the BGP class rate and move the SSH class into the BGP class-map.
D.Configure an ACL that permits only the jump host's IP and apply it as the match for the class-default class.
AnswerA

SSH traffic must be explicitly classified so CoPP can rate-limit it separately instead of letting it fall into a default or catch-all class that may be policed aggressively. Adding a TCP port 22 class with a suitable rate and transmit action preserves protection while guaranteeing management access. This is the standard CoPP design practice for management protocols.

Why this answer

CoPP works by classifying punted control-plane traffic into classes and applying per-class policers. If SSH is not explicitly matched, it is handled by class-default, which is often policed conservatively. Creating a dedicated class matching TCP port 22 with an adequate rate and a conform action of transmit ensures interactive management traffic survives bursts while BGP and other protocols stay protected.

Exam trap

The trap here is treating CoPP as an all-or-nothing filter and removing it, rather than recognizing that unclassified management traffic is the real cause of the timeouts.

69
MCQmedium

A network administrator is deploying Control Plane Policing (CoPP) on a Cisco IOS XE router that runs BGP, OSPF, and SSH management. The administrator wants to protect the route processor from excessive control-plane traffic while still allowing legitimate routing protocol and management traffic. The administrator creates a class map that matches BGP, OSPF, and SSH traffic and applies a police action with a committed information rate. Which additional configuration element is required to complete the CoPP implementation?

A.Configure a route map that matches the control-plane protocols and reference it in the policy map.
B.Apply the policy map to all physical interfaces using the service-policy input command under interface configuration mode.
C.Apply the policy map to the control plane using the service-policy input command under control-plane configuration mode.
D.Enable NetFlow on the router to export control-plane traffic statistics to a collector.
AnswerC

CoPP requires a policy map to be attached to the control plane with service-policy input under control-plane configuration mode. Without this attachment, the class maps and policy map exist but are not enforced on control-plane traffic, leaving the route processor unprotected.

Why this answer

CoPP is implemented by defining class maps to identify control-plane traffic, a policy map to apply actions such as police, and then attaching the policy map to the control plane with service-policy input under control-plane configuration mode. Without that attachment, the policy is never applied to control-plane traffic, so the route processor remains vulnerable to excessive protocol or management packets.

Exam trap

The trap here is assuming that applying a policy map to physical interfaces protects the control plane, when CoPP specifically requires attachment under control-plane configuration mode.

70
MCQmedium

ip vrf RED rd 200:1 route-target export 200:1 route-target import 200:1 ! interface GigabitEthernet0/1 ip vrf forwarding RED ip address 10.1.1.1 255.255.255.0 ! router bgp 65000 neighbor 192.168.1.1 remote-as 65000 neighbor 192.168.1.1 update-source Loopback0 address-family vpnv4 neighbor 192.168.1.1 activate neighbor 192.168.1.1 send-community extended ! Which statement about this configuration is true?

A.The configuration is correct for MPLS L3VPN, but the VRF RED must also be configured under BGP with 'address-family ipv4 vrf RED'.
B.The 'send-community extended' command is unnecessary because it is enabled by default.
C.The interface GigabitEthernet0/1 requires 'mpls ip' to forward MPLS packets.
D.The VRF RED will automatically import routes from the VPNv4 address-family without additional configuration.
AnswerA

The statement is correct: for an MPLS L3VPN, the VRF RED configuration itself is valid, but the VRF must also be activated in BGP under the 'address-family ipv4 vrf RED' stanza. This enables BGP to import and export routes between the VRF and the VPNv4 address family, converting IPv4 VRF routes into VPNv4 routes with the appropriate route target extended communities. Without this BGP address-family configuration, the VRF will have no BGP peering for VPN routes, so even if other pieces are in place, end-to-end L3VPN connectivity will not work.

Why this answer

In an MPLS L3VPN configuration, after creating the VRF and applying it to an interface, you must also configure the VRF under BGP using the 'address-family ipv4 vrf RED' command to exchange IPv4 routes within that VRF. Without this, the VRF will not participate in BGP route exchange, and the VPNv4 address-family alone cannot import or export VRF routes. The given configuration is incomplete, as it lacks the VRF-specific address-family under BGP.

Exam trap

Cisco often tests the misconception that applying a VRF to an interface and configuring route-target import/export is sufficient for BGP route exchange, but the missing 'address-family ipv4 vrf' under BGP is the critical step that candidates overlook.

How to eliminate wrong answers

Option B is wrong because the 'send-community extended' command is not enabled by default for VPNv4 neighbors; it must be explicitly configured to allow the exchange of extended communities, which are essential for MPLS L3VPN route target filtering. Option C is wrong because the 'mpls ip' command is required on interfaces that participate in MPLS forwarding (e.g., core-facing interfaces), but not on the customer-facing interface GigabitEthernet0/1, which only needs VRF forwarding and an IP address. Option D is wrong because VRF RED will not automatically import routes from the VPNv4 address-family; you must explicitly configure the VRF under BGP with 'address-family ipv4 vrf RED' and then use the 'import' and 'export' route-target commands (already done in VRF definition) to control route exchange.

71
MCQmedium

A network engineer runs the following command on Router R1: R1# show bgp summary BGP router identifier 192.168.1.1, local AS number 65001 BGP table version is 10, main routing table version 10 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 192.168.1.2 4 65002 1024 1020 10 0 0 00:12:34 15 192.168.1.3 4 65003 2048 2040 10 0 0 00:24:56 20 Based on this output, what can be concluded?

A.Both BGP sessions are in the established state
B.The BGP session with 192.168.1.2 is idle
C.Router R1 is using iBGP with both neighbors
D.The BGP table version is 10, meaning 10 prefixes are in the table
AnswerA

The output shows State/PfxRcd counts of 15 and 20 for the two neighbors. In BGP's state machine, only the established state populates the PfxRcd column with a numeric prefix count; any other state (Idle, Connect, Active, OpenSent, OpenConfirm) would display the state name or a placeholder. Consequently, both neighbors are fully peering and exchanging reachability information.

Why this answer

The 'State/PfxRcd' column shows the number of prefixes received from each neighbor, and the 'Up/Down' column shows the session uptime, both of which indicate that the BGP sessions are fully established. An idle session would show 'Idle' in the State/PfxRcd column, not a prefix count. Therefore, both sessions are in the established state.

Exam trap

Cisco often tests the distinction between the BGP table version (a change counter) and the prefix count in the State/PfxRcd column, leading candidates to mistakenly interpret the version number as the number of prefixes.

How to eliminate wrong answers

Option B is wrong because the output shows '15' and '20' in the State/PfxRcd column, indicating the sessions are established and exchanging prefixes; an idle session would display 'Idle' or 'Active' in that column. Option C is wrong because the neighbor AS numbers (65002 and 65003) differ from the local AS 65001, which means these are eBGP sessions, not iBGP (iBGP requires the same AS number). Option D is wrong because the BGP table version (10) is a version counter that increments with each change to the BGP table, not a count of prefixes; the actual number of prefixes is shown in the State/PfxRcd column (15 and 20).

72
MCQmedium

A network engineer runs the following command on Router R1: R1# show ip route 10.1.1.0 Routing entry for 10.1.1.0/24 Known via "bgp 65001", distance 200, metric 0 Tag 65002, type external Last update from 192.168.1.2 00:00:15 ago Routing Descriptor Blocks: * 192.168.1.2, from 192.168.1.2, 00:00:15 ago Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 65002 MPLS label: 18 Based on this output, what can be concluded?

A.The route is learned via OSPF and tagged with an MPLS label.
B.The route is learned via BGP and has an MPLS label assigned, indicating MPLS forwarding.
C.The route is a directly connected interface with an MPLS label.
D.The route is a static route with an MPLS label.
AnswerB

The command output shows 'Known via bgp 65001' and 'MPLS label: 18', which together confirm that the route was received from a BGP peer in AS 65001 and that an MPLS label has been assigned to the prefix. In BGP labeled unicast or MPLS VPN operation, the label is propagated with the route so that ingress PEs can impose the correct label and forward traffic along the LSP. This is the only option that correctly correlates both the routing protocol source and the MPLS forwarding indicator.

Why this answer

The output shows the route is known via BGP (AS 65001) with a distance of 200, which is the administrative distance for external BGP routes. The presence of an MPLS label (18) in the routing table indicates that MPLS forwarding is enabled for this prefix, typically via Label Distribution Protocol (LDP) or BGP label distribution. This confirms that the route is learned via BGP and has an MPLS label assigned, making option B correct.

Exam trap

Cisco often tests the misconception that MPLS labels only appear in the CEF table or MPLS forwarding table, but they can also be displayed in the routing table when MPLS forwarding is active, leading candidates to incorrectly dismiss option B.

How to eliminate wrong answers

Option A is wrong because the route is explicitly identified as 'Known via bgp 65001', not OSPF, and OSPF does not use MPLS labels in the routing table. Option C is wrong because the route is not directly connected; it is learned from a neighbor (192.168.1.2) and has an AS hop count of 1, indicating it is a BGP external route. Option D is wrong because the route is not static; it is dynamically learned via BGP, as shown by the BGP AS number and the 'type external' field.

73
MCQmedium

Consider the following BGP configuration on a Cisco IOS-XE router: router bgp 65001 neighbor 10.0.0.2 remote-as 65002 neighbor 10.0.0.2 route-map SET_COMMUNITY out ! route-map SET_COMMUNITY permit 10 set community 65001:100 What is the effect of this configuration?

A.The router will set the community to 65001:100 on all routes received from neighbor 10.0.0.2.
B.The router will set the community to 65001:100 on all routes advertised to neighbor 10.0.0.2.
C.The router will filter routes with community 65001:100 from being advertised.
D.The router will remove the community from routes advertised to the neighbor.
AnswerB

The outbound route-map applies the set community action to every prefix advertised to 10.0.0.2, so the neighbour receives routes tagged 65001:100. Because no send-community keyword is shown, the attribute is set locally but only transmitted if community propagation is enabled.

Why this answer

The route-map SET_COMMUNITY is applied with the 'out' keyword on the neighbor statement, meaning it is evaluated on routes being advertised to neighbor 10.0.0.2. The 'set community 65001:100' action therefore stamps the community value 65001:100 on all outbound routes sent to that neighbor.

Exam trap

350-401 often tests the direction of route-map application — candidates confuse 'in' (affects received routes) with 'out' (affects advertised routes) and pick the wrong effect.

How to eliminate wrong answers

Option A is wrong because an 'out' route-map affects outbound advertisements, not inbound received routes — to modify received routes you would use 'in'. Option C is wrong because the route-map uses 'set community', not a 'match community' with a deny action; nothing filters routes based on community. Option D is wrong because 'set community 65001:100' adds/sets the community value; it does not remove communities (that would require 'set community none' or 'set comm-list delete').

74
Matchingmedium

Drag and drop each BGP attribute on the left to its matching type on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Well-known mandatory

Well-known mandatory

Well-known discretionary

Optional non-transitive

Optional transitive

Why these pairings

AS_PATH and NEXT_HOP are well-known mandatory; LOCAL_PREF is well-known discretionary; MED is optional non-transitive; COMMUNITY is optional transitive.

75
MCQmedium

A network administrator is deploying Control Plane Policing (CoPP) on a Cisco IOS XE router that peers BGP with two ISPs. After applying a policer to the control plane, the BGP sessions tear down repeatedly while OSPF adjacencies stay stable. The administrator confirms CPU utilization is low. Which action should be taken to resolve the issue?

A.Apply the CoPP policy to the data plane interfaces using the service-policy input command.
B.Increase the CIR of the policer class matching BGP traffic and permit the BGP class in the control-plane service policy.
C.Disable CEF switching on the router so BGP packets are process-switched and bypass the policer.
D.Enable NetFlow on the WAN interfaces and export records to a collector for BGP traffic analysis.
AnswerB

BGP session teardown with low CPU indicates the policer is dropping BGP keepalives before they reach the control plane. Raising the committed information rate for the BGP class and explicitly permitting that class in the control-plane policy allows the protocol traffic to pass at the required rate, restoring adjacency stability without disabling CoPP for other traffic.

Why this answer

CoPP policies inspect and police traffic punted to the route processor. When a policer for a critical routing protocol is too restrictive, protocol hellos and keepalives are dropped, causing peering failures even though CPU load is low. Adjusting the policer rate and ensuring the protocol class is permitted restores the required control-plane traffic while retaining protection against abuse.

Exam trap

The trap here is assuming that low CPU utilization proves CoPP is working correctly, when in fact a too-strict policer silently discards essential routing protocol keepalives.

Page 1 of 2 · 114 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Bgp questions.