Buckets:
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have a main office and many branch sites"}, {"role": "assistant", "content": "DMVPN uses mGRE, NHRP, and IPsec to let many branch spokes register dynamically with a hub, so adding branches requires far less hub-side configuration than building a separate static IPsec tunnel for each site. This makes DMVPN more scalable than traditional point-to-point IPsec tunnels. DMVPN also lets spokes resolve each other through NHRP and build dynamic spoke-to-spoke tunnels on demand, which avoids permanent full-mesh IPsec tunnel designs. AES-256 is available in both IPsec and DMVPN, anycast gateway is not a DMVPN feature, and DMVPN generally adds GRE/NHRP overhead rather than lowering it."}], "meta": {"exam": "A", "qnum": 2, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In NETCONF, how can I subscribe to notifications for my session and apply an event filter so I only receive the notifications I care about?"}, {"role": "assistant", "content": "Use the `<create-subscription>` operation with the optional `<filter>` parameter. It creates the notification subscription and scopes the filter to that session, so only matching notifications are sent to the requesting client; this is why it is the correct operation for session-specific notification filtering."}], "meta": {"exam": "A", "qnum": 3, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In NETCONF, how can I subscribe to notifications for my session and apply an event filter so I only receive the notifications I care about?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - `<commit>` commits a candidate configuration to the running"}], "meta": {"exam": "A", "qnum": 3, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "A customer requires QoS that can verify the complete end-to-end path and reserve resources for individual traffic flows before they are admitted. Which QoS model should we recommend?"}, {"role": "assistant", "content": "Use the IntServ model with RSVP. IntServ uses RSVP to request and maintain per-flow reservations along every hop, so each router can verify whether the requested resources are available before accepting the flow. This gives the required end-to-end path verification; DiffServ and marking-only approaches provide classification or per-hop treatment but do not verify end-to-end resource availability."}], "meta": {"exam": "A", "qnum": 6, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: A customer requires QoS that can verify the complete end-to-end path and reserve resources for individual traffic flows before they are admitted. Which QoS model should we recommend?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - DiffServ with PHB provides scalable class-based forwarding treatment but does not signal or verify resources along the end-to-end path.\nC - Marking traffic at the access layer with DSCP only classifies packets for per-hop treatment and does not verify end-to-end path availability.\nD - Marking traffic at the access layer with CoS only sets Layer 2 priority and does not provide end-to-end path verification."}], "meta": {"exam": "A", "qnum": 6, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a WAN edge design, we need a QoS mechanism that starts dropping lower-priority packets as a"}, {"role": "assistant", "content": "WRED (Weighted Random Early Detection) is a congestion-avoidance mechanism that drops packets before a queue is completely full. It uses minimum/maximum thresholds and mark-probability settings, and can weight drops by IP precedence or DSCP so lower-priority packets are discarded more aggressively. This protects higher-priority traffic and helps TCP flows reduce their send rate before global synchronization occurs. CBWFQ and strict priority are primarily scheduling/queueing features, and tail drop is an indiscriminate full-queue drop behavior. Therefore, WRED is the correct answer."}], "meta": {"exam": "A", "qnum": 8, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are designing management access for our campus and WAN routers. Should we use in-band management over the production links or build a separate out-of-band management network, and what is the main operational benefit?"}, {"role": "assistant", "content": "Go with out-of-band management because it preserves administrative access during a production network outage. Recommend a dedicated management path (console/terminal server or separate management network) so that if production routing, switching, or links fail, you can still reach devices to troubleshoot and recover them. That management survivability under failure is the key advantage, and it also isolates management traffic from user traffic for better security."}], "meta": {"exam": "A", "qnum": 14, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass_regenerated"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I need a QoS design for an interface where short bursts above the contracted rate should be held and sent later instead of being dropped immediately. Which mechanism should I include?"}, {"role": "assistant", "content": "Use traffic shaping. It queues excess packets and releases them later according to the configured rate, so bursts are smoothed rather than dropped; policing would drop or remark excess traffic, while RED/WRED are congestion-avoidance drop mechanisms, not deferred-transmission queues."}], "meta": {"exam": "A", "qnum": 18, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I need a QoS design for an interface where short bursts above the contracted rate should be held and sent later instead of being dropped immediately. Which mechanism should I include?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - WRED is a congestion-avoidance queue-management mechanism that probabilistically drops packets before tail drop, not one that queues excess traffic for later transmission.\nC - Policing enforces a rate by dropping or remarking excess packets, so it does not queue them for later transmission.\nD - RED is an early-drop congestion-avoidance algorithm that discards packets probabilistically, rather than buffering excess packets for later sending."}], "meta": {"exam": "A", "qnum": 18, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are designing an SD-WAN fabric and considering direct Internet access at every branch instead of backhauling Internet-bound traffic to a data center. What are the main design benefits of doing that?"}, {"role": "assistant", "content": "Use local DIA at each site for Internet, SaaS, and public-cloud traffic, while steering private traffic over the SD-WAN overlay or MPLS. This improves latency to public cloud applications because traffic takes a local Internet path rather than being backhauled, and it offloads MPLS circuits so they are less congested. DIA does not change the inherent latency of the Internet circuit, does not add total Internet bandwidth, and is not what makes zero-touch provisioning faster."}], "meta": {"exam": "A", "qnum": 21, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are designing an SD-WAN fabric and considering direct Internet access at every branch instead of backhauling Internet-bound traffic to a data center. What are the main design benefits of doing that?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - DIA changes the traffic path and breakout location, but it does not decrease the underlying latency of Internet circuits.\nC - Zero-touch provisioning is an automation capability of the SD-WAN controller, not a benefit created by placing DIA at every site.\nD - DIA uses the existing Internet circuit capacity; it can improve"}], "meta": {"exam": "A", "qnum": 21, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m designing multicast for a financial application where most multicast sources also receive multicast traffic, so it’s a many-to-many deployment. To scale routing tables, the design must not use source trees. Which multicast protocol should I choose?"}, {"role": "assistant", "content": "Use BIDIR-PIM. It builds a bidirectional shared tree per group rooted at the RP and keeps only (*,G) routing state, avoiding per-source (S,G) source trees. That matches the many-to-many model and scales routing tables better than protocols that rely on source-specific trees or SPT switchover."}], "meta": {"exam": "A", "qnum": 26, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I’m designing multicast for a financial application where most multicast sources also receive multicast traffic, so it’s a many-to-many deployment. To scale routing tables, the design must not use source trees. Which multicast protocol should I choose?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A – PIM-SSM uses source-specific (S,G) trees and is intended for one-to-many source-specific multicast, so it violates the no"}], "meta": {"exam": "A", "qnum": 26, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are a cable TV provider multicasting many video channels from multiple known sources. The design must"}, {"role": "assistant", "content": "PIM-SSM builds source-specific shortest-path trees and does not use a rendezvous point or shared tree, directly meeting the no-RP requirement. Receivers join individual (S,G) channels using IGMPv3/MLDv2, which fits known broadcast/video sources. PIM-SM and BIDIR-PIM both depend on an RP, while ASM is the shared-tree/RP model. Therefore, B is correct."}], "meta": {"exam": "A", "qnum": 27, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-WAN architecture, which component is responsible for the centralized control plane and distributing overlay routing and policy information to the branch devices?"}, {"role": "assistant", "content": "The vSmart controller is the component that provides the centralized control plane. It peers with WAN edge devices using OMP, distributes overlay reachability and TLOC information, and applies centralized control policies such as topology and route policy. It does not perform device orchestration, GUI-based management, or data-plane forwarding."}], "meta": {"exam": "A", "qnum": 28, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco SD-WAN architecture, which component is responsible for the centralized control plane and distributing overlay routing and policy information to the branch devices?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Orchestrating initial vEdge and cEdge connectivity is primarily the role of the vBond orchestrator, not vSmart.\nC - Providing centralized network management and a GUI to monitor and operate the SD-WAN overlay is the role of vManage.\nD - Providing a data-plane at branch offices to forward traffic through the SD-WAN overlay is the role of vEdge/cEdge WAN edge devices."}], "meta": {"exam": "A", "qnum": 28, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We’re designing branch redundancy with vEdge routers and need first-hop gateway redundancy for LAN hosts. Which FHRP can we run on the vEdge routers?"}, {"role": "assistant", "content": "Use VRRP. vEdge routers support VRRP for first-hop redundancy, allowing redundant vEdge devices to present a virtual gateway IP to the LAN. HSRP and GLBP are not supported on vEdge, and OMP is an SD-WAN overlay protocol rather than an FHRP."}], "meta": {"exam": "A", "qnum": 32, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We’re designing branch redundancy with vEdge routers and need first-hop gateway redundancy for LAN hosts. Which FHRP can we run on the vEdge routers?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - HSRP is a Cisco-proprietary FHRP, but it is not supported on vEdge routers for this redundancy design.\nB - OMP is Cisco SD-WAN’s overlay management protocol and does not provide first-hop gateway redundancy.\nC - GLBP is a Cisco-proprietary"}], "meta": {"exam": "A", "qnum": 32, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We run OSPF and BGP with graceful restart on a chassis that has dual supervisors. What redundancy feature must be in place so the router can survive an active route-processor crash without dropping traffic?"}, {"role": "assistant", "content": "You need Stateful Switchover (SSO) along with NSF/graceful restart. SSO keeps the standby supervisor synchronized with the active one, so when the active processor fails, the standby can take over and preserve forwarding state while routing protocols restart gracefully."}], "meta": {"exam": "A", "qnum": 33, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We run OSPF and BGP with graceful restart on a chassis that has dual supervisors. What redundancy feature must be in place so the router can survive an active route-processor crash without dropping traffic?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Cisco Express Forwarding is a forwarding-plane/FIB mechanism and does not synchronize supervisor state for processor failover.\nB - Virtual Switch System is a multichassis virtualization technology and is not the required feature for single-chassis processor failure recovery.\nD - Bidirectional Forwarding Detection detects forwarding-path failures but does not preserve control-plane state or enable graceful restart recovery."}], "meta": {"exam": "A", "qnum": 33, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I have two EIGRP routers in the same AS, and I need to stop one router from learning or advertising a specific subnet to its EIGRP neighbor without changing the autonomous system. What is the standard way to filter those EIGRP routes?"}, {"role": "assistant", "content": "Use an EIGRP distribute-list with an ACL or prefix-list, applied inbound or outbound under the EIGRP process or on the relevant interface. It directly filters"}], "meta": {"exam": "A", "qnum": 34, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need first-hop redundancy where hosts use one default gateway IP, but traffic should be shared across several routers without configuring multiple VIPs or changing host settings. Which FHRP should we use?"}, {"role": "assistant", "content": "Use GLBP. GLBP provides a single virtual IP and multiple virtual MAC addresses; the AVG assigns AVFs, and hosts resolve the same VIP to different MACs for round-robin, weighted, or host-dependent load balancing. HSRP and VRRP with one virtual IP elect one active forwarding router/MAC, so they do not natively load"}], "meta": {"exam": "A", "qnum": 42, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m using NETCONF against Cisco NX-OS devices and need to configure a feature that is specific to NX-OS and not standardized. Which YANG model family should I use?"}, {"role": "assistant", "content": "Use the Cisco NX-OS native YANG model. Native models are vendor-specific and expose NX-OS-only features, while IETF, IEEE, and OpenConfig models are standards-based"}], "meta": {"exam": "A", "qnum": 50, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have an application that needs to signal the network with its traffic profile and ask for strict bandwidth and delay guarantees from end to end. Which QoS architecture model should I propose?"}, {"role": "assistant", "content": "Use IntServ with RSVP. IntServ lets the application signal its traffic profile and request per-flow service, and RSVP reserves resources along the path with admission control, which can provide consistent dedicated bandwidth and bounded delay end to end."}], "meta": {"exam": "A", "qnum": 58, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We have an application that needs to signal the network with its traffic profile and ask for strict bandwidth and delay guarantees from end to end. Which QoS architecture model should I propose?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - DiffServ is a scalable class-based model, but it does not let applications signal per-flow requirements or guarantee dedicated bandwidth end to end.\nB - LLQ is a queuing and scheduling mechanism inside a QoS deployment, not an end-to-end QoS architecture.\nC - WRED is a congestion-avoidance drop mechanism, not an admission-controlled service model."}], "meta": {"exam": "A", "qnum": 58, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "When Cisco Express Forwarding forwards traffic to a next hop, which OSI layer’s addressing information does the adjacency table populate for the rewrite?"}, {"role": "assistant", "content": "The adjacency table populates Layer 2 addressing information. CEF separates control-plane and data-plane functions: the FIB contains Layer 3 prefix reachability, while the adjacency table holds the Layer 2 next-hop rewrite details, such as the destination MAC address. ARP or IPv6 neighbor discovery populates those adjacencies, allowing CEF to encapsulate frames without per-packet recursive lookups."}], "meta": {"exam": "A", "qnum": 75, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: When Cisco Express Forwarding forwards traffic to a next hop, which OSI layer’s addressing information does the adjacency table populate for the rewrite?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Layer 4 is above the forwarding rewrite path and deals with transport-layer identifiers, not CEF adjacency addressing.\nC - Layer 1 covers physical signaling and media characteristics, not the addressing information stored in CEF adjacencies.\nD - Layer 3 is represented primarily by the CEF FIB for prefix reachability, while the adjacency table supplies the Layer 2 rewrite."}], "meta": {"exam": "A", "qnum": 75, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-WAN design, what techniques should I use in the overlay to make business-critical voice and video applications perform better when WAN links experience packet loss and congestion?\n\nASSISTANT_QU"}, {"role": "assistant", "content": "FEC improves application experience by adding redundant/parity packets so that packet loss on a WAN link can be reconstructed without retransmission, which helps real-time and interactive applications. QoS improves application experience by classifying, marking, queuing, scheduling, and shaping traffic so business-critical applications receive the latency, jitter, and loss treatment they require across the SD-WAN overlay. In Cisco SD-WAN design, FEC and QoS are directly part of the application-experience/performance toolset alongside application-aware routing, packet duplication, and TCP optimization. B, C, and E are security-related controls, not direct application-performance techniques."}], "meta": {"exam": "A", "qnum": 88, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How should I design QoS on the customer router for a 50-Mbps Layer 3 service that is handed off at 1 Gbps to keep voice traffic from becoming choppy?"}, {"role": "assistant", "content": "Use hierarchical QoS with a parent shaping policy set to the 50-Mbps CIR, and place voice in a child priority/LLQ class. The provider is likely policing at 50 Mbps, so sending at 1 Gbps can cause drops; a parent shaper smooths outbound traffic and buffers excess bursts, preventing policer drops that would otherwise damage voice quality."}], "meta": {"exam": "A", "qnum": 102, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How should I design QoS on the customer router for a 50-Mbps Layer 3 service that is handed off at 1 Gbps to keep voice traffic from becoming choppy?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Reducing the connection bandwidth to the router is not a valid rate-limiting design technique and does not enforce the 50-Mbps CIR. \nB - A parent policing policy drops excess traffic rather than smoothing it, which can still cause voice packet loss and choppy audio. \nD - The bandwidth statement is informational and affects routing metrics only; it does not shape or police traffic to the CIR."}], "meta": {"exam": "A", "qnum": 102, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I need to design a scalable QoS architecture that separates traffic into classes based on predefined business requirements, uses DSCP as the priority descriptor, and supports at least 10 levels of classification. Which QoS technology should I use?"}, {"role": "assistant", "content": "Use DiffServ. DiffServ is designed for scalable, class-based QoS and uses the DSCP field in the IP header as the priority descriptor. Since DSCP provides up to 64 code points, it easily meets the requirement for at least 10 classification levels, while per-hop behaviors enforce treatment without per-flow state."}], "meta": {"exam": "A", "qnum": 104, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I need to design a scalable QoS architecture that separates traffic into classes based on predefined business requirements, uses DSCP as the priority descriptor, and supports at least 10 levels of classification. Which QoS technology should I use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - RSVP is a signaling protocol often used with IntServ and is not the scalable DSCP-based classification architecture required here.\nC - Best effort provides no traffic classification, priority marking, or QoS guarantees.\nD - Interserv, or IntServ, uses per-flow reservations and does not scale as a DSCP-based class model for large networks."}], "meta": {"exam": "A", "qnum": 104, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What is the SD-Access underlay actually responsible for, and does it handle the VXLAN encapsulation or just provide connectivity between the fabric devices?"}, {"role": "assistant", "content": "The underlay just provides physical and IP-routed connectivity between fabric switches and routers; VXLAN encapsulation and virtualization happen in the overlay. It gives the fabric nodes a stable transport path, usually with an IGP, so the control plane and overlay tunnels can be built on top of it. It"}], "meta": {"exam": "A", "qnum": 122, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access fabric, what is the role of the control plane node compared with the fabric edge and border nodes?"}, {"role": "assistant", "content": "Use the control plane node as the LISP map server/map resolver and host-tracking database for the fabric. It maintains EID-to-RLOC mappings between endpoints and their serving fabric edge nodes, while edge nodes detect and register endpoints and border nodes handle external connectivity."}], "meta": {"exam": "A", "qnum": 127, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco SD-Access fabric, what is the role of the control plane node compared with the fabric edge and border nodes?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Endpoint detection and registration of EID-to-fabric-edge bindings is performed by fabric edge nodes, not control plane nodes."}], "meta": {"exam": "A", "qnum": 127, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have several remote sites connected to headquarters through microwave links, and we need a resilient backup WAN option for when the microwave path fails. What backup WAN link type should we recommend?"}, {"role": "assistant", "content": "Recommend LTE as the backup WAN link. It gives the remote sites an independent cellular path that is not affected by microwave line-of-sight or weather issues, and it can be used with IPsec VPN or SD-WAN for automatic failover. LTE is also widely available from carriers and practical to deploy at branch sites."}], "meta": {"exam": "A", "qnum": 130, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We have several remote sites connected to headquarters through microwave links, and we need a resilient backup WAN option for when the microwave path fails. What backup WAN link type should we recommend?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - WiMAX is a legacy metropolitan wireless technology with limited carrier support and is not a practical modern backup WAN.\nC - Laser links require clear line-of-sight and are vulnerable to fog, rain, and physical obstructions, so they do not provide independent resilience.\nD - Bluetooth is a short-range personal-area technology and cannot function as a WAN backup link."}], "meta": {"exam": "A", "qnum": 130, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need a campus design that gives us isolated network segments, but we also need to allow communication between those segments when necessary. Some departments use overlapping IP address ranges, and we want to avoid buying specialized equipment. What should we use?"}, {"role": "assistant", "content": "Use VRF-Lite with OSPF. VRF-Lite provides separate routing tables for logical segmentation and isolation, supports overlapping IP addresses"}], "meta": {"exam": "B", "qnum": 20, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "A global company has many branches that communicate frequently and will keep adding more branches. Security requires dynamic IPsec tunnels between branch sites, and the overlay design should scale easily as new sites are added. Which overlay VPN solution should the network architect choose?"}, {"role": "assistant", "content": "Choose DMVPN. DMVPN uses mGRE, NHRP, and dynamic IPsec to create a scalable overlay where spokes can register with the hub and build direct spoke-to-spoke IPsec tunnels on demand. It supports frequent branch-to-branch traffic efficiently and allows new branches to be added without redesigning the IPsec topology."}], "meta": {"exam": "B", "qnum": 25, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: A global company has many branches that communicate frequently and will keep adding more branches. Security requires dynamic IPsec tunnels between branch sites, and the overlay design should scale easily as new sites are added. Which overlay VPN solution should the network architect choose?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - EasyVPN is primarily a remote-access client VPN solution and is not designed as a scalable dynamic site-to-site overlay for many branches.\nC - L2TP does not natively provide IPsec encryption and does not offer a dynamic multipoint overlay architecture like DMVPN.\nD - GETVPN provides group-based IPsec encryption but relies on a routed underlay rather than dynamic point-to-point overlay tunnels for scalable spoke-to-spoke connectivity."}], "meta": {"exam": "B", "qnum": 25, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "An ISP is providing an MPLS Layer 3 VPN to a customer with four branches, and each branch has multiple CE routers. On the PE-to-PE iBGP sessions inside the ISP core, which BGP address family should be enabled so the PEs can exchange the customer routes learned from the CE routers?"}, {"role": "assistant", "content": "Enable the VPNv4 unicast address family on the PE-to-PE MP-BGP sessions. That address family carries customer IPv4 prefixes with the RD, route targets, and VPN label needed for MPLS L3VPN, so each PE can import the routes into the correct VRF and forward traffic across the core."}], "meta": {"exam": "B", "qnum": 26, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: An ISP is providing an MPLS Layer 3 VPN to a customer with four branches, and each branch has multiple CE routers. On the PE-to-PE iBGP sessions inside the ISP core, which BGP address family should be enabled so the PEs can exchange the customer routes learned from the CE routers?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Multicast address family is for multicast routing information, not for carrying unicast customer VPN routes between PEs.\nB - L2VPN EVPN is used for Ethernet VPN services, not as the traditional MPLS L3VPN PE-to-PE address family for IPv4 customer routes.\nD - IPv4 unicast lacks the RD, route-target, and VPN label context required to separate and transport customer VRF routes across the MPLS core."}], "meta": {"exam": "B", "qnum": 26, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need to deploy multicast between two autonomous systems. The RPs in each domain must learn about active multicast sources in the other domain, exchange source information with each other over the existing routed infrastructure, and announce active sources to RPs in other domains. Which multicast solution should we use?"}, {"role": "assistant", "content": "Use MSDP between the RPs, together with PIM-SM inside each domain. MSDP lets RPs peer across domains and exchange Source-Active messages, so RPs discover active sources outside their own domain. PIM-SM handles the intra-domain tree building, while MSDP provides the interdomain source announcement and uses the underlying unicast routing for RP-to-R"}], "meta": {"exam": "B", "qnum": 32, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access fabric, which control-plane protocol lets the fabric track where an endpoint is located so traffic can be sent to the correct edge node?"}, {"role": "assistant", "content": "Use LISP. Cisco SD-Access relies on LISP for the fabric control plane: endpoints are EIDs, their edge-node locations are RLOCs, and the control-plane node resolves EID-to-RLOC mappings so fabric devices can forward traffic to the correct edge. This makes LISP the endpoint-to-location mapping protocol, while other protocols serve different roles in the fabric."}], "meta": {"exam": "B", "qnum": 40, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco SD-Access fabric, which control-plane protocol lets the fabric track where an endpoint is located so traffic can be sent to the correct edge node?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - FabricPath is a"}], "meta": {"exam": "B", "qnum": 40, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In our Cisco SD-Access fabric, which device role should I deploy to provide the LISP Map-Server and Map-Resolver functions so edge nodes can register and resolve endpoint EID-to-RLOC mappings?"}, {"role": "assistant", "content": "Use the control plane node. It is the SD-Access role that runs the LISP Map-Server and Map-Resolver, allowing fabric edge nodes to register local endpoints and resolve remote EID-to-RLOC mappings. This keeps LISP control-plane functions centralized while edge, border, and intermediate nodes handle forwarding, external connectivity, and underlay transport respectively."}], "meta": {"exam": "B", "qnum": 45, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In our Cisco SD-Access fabric, which device role should I deploy to provide the LISP Map-Server and Map-Resolver functions so edge nodes can register and resolve endpoint EID-to-RLOC mappings?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Fabric edge nodes register EIDs and encapsulate traffic, but they do not provide the LISP Map-Server or Map-Resolver service.\nC - Border nodes connect the fabric to external networks and handle VXLAN/LISP handoffs, not the central LISP MS/MR role.\nD - Intermediate nodes provide underlay transit routing and do not participate in"}], "meta": {"exam": "B", "qnum": 45, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m designing a Layer 2 campus with VSS at the distribution layer. I need fast convergence and want to use as much bandwidth as possible between the access and distribution layers, but routing protocol licensing is restricted. What should I use?"}, {"role": "assistant", "content": "Use Multichassis EtherChannel (MEC) between the access switches and the VSS distribution pair. MEC lets the access switch form one logical EtherChannel across both distribution chassis, so all links can forward traffic active-active. It gives fast convergence through EtherChannel/LACP and avoids STP blocking a redundant link, while not depending on L3 routing protocols or ECMP."}], "meta": {"exam": "B", "qnum": 48, "topic": "", "has_exhibit": true, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I’m designing a Layer 2 campus with VSS at the distribution layer. I need fast convergence and want to use as much bandwidth as possible between the access and distribution layers, but routing protocol licensing is restricted. What should I use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Standard EtherChannel is limited to a single physical switch and cannot span the two VSS chassis. \nC - RSTP provides loop prevention and convergence, but it blocks redundant links and does not aggregate their bandwidth. \nD - ECMP is an L3 routing technique and depends on routing protocols that may be unavailable due to licensing limits."}], "meta": {"exam": "B", "qnum": 48, "topic": "", "has_exhibit": true, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our cloud-based voice, video, file-sharing, content-sharing, and messaging applications intermittently become slow during business hours, but other applications work fine with our current QoS policies. How should we design QoS to fix this?"}, {"role": "assistant", "content": "Use NBAR2 to identify the cloud applications and then update the QoS policy to allocate the required bandwidth to those application classes. NBAR2 gives accurate application classification even when cloud apps use dynamic ports or HTTPS, which allows the QoS design to treat the actual business-critical traffic instead of relying on static ports that may be wrong or incomplete."}], "meta": {"exam": "B", "qnum": 57, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Our cloud-based voice, video, file-sharing, content-sharing, and messaging applications intermittently become slow during business hours, but other applications work fine with our current QoS policies. How should we design QoS to fix this?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Static port-based classification is unreliable for cloud applications that use dynamic ports, HTTPS, or encrypted flows.\nC - Reserving bandwidth only on perimeter routers does not guarantee proper classification and queuing along the full path or at the actual congestion point.\nD - Rate-limiting caps bandwidth but does not provide a minimum guarantee, so it can make the slow application experience worse."}], "meta": {"exam": "B", "qnum": 57, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have a 100-Mbps Internet link using CBWFQ. Since adding Cisco TelePresence, other applications perform poorly when video is active. What strict-priority bandwidth limit should I configure for real-time traffic to prevent starvation?\n\nASSIST"}, {"role": "assistant", "content": "Strict-priority queuing gives real-time traffic immediate service, but it must be bounded so it cannot starve other CBWFQ classes. Cisco QoS design guidance limits the priority/LLQ class to about 33 percent of the link capacity for voice and video real-time traffic. On a 100-Mbps link, 33 percent is 33 Mbps. This cap preserves TelePresence quality while leaving sufficient bandwidth for other applications, resolving their response issues."}], "meta": {"exam": "B", "qnum": 68, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need distributed QoS across our enterprise WAN, with packets marked for the treatment they require and each router forwarding them according to locally defined per-hop behavior. Which QoS technology should we choose?"}, {"role": "assistant", "content": "Choose Differentiated Services (DiffServ). DiffServ marks packets at the edge with DSCP and defines per-hop behaviors that each device enforces independently, matching your requirement for packet marking plus hop-by-hop treatment without per-flow state in"}], "meta": {"exam": "B", "qnum": 73, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need to design a management network that lets us grant and revoke admin access, permits only SSH, NTP, FTP, and SNMP, and keeps management interfaces isolated from production traffic. Which management design should we use?"}, {"role": "assistant", "content": "Use an out-of-band management network. It provides dedicated management access separate from production, supports AAA for granting/revoking privileges, and lets you enforce strict protocol and interface access controls. In-band or overlay options do not isolate management interfaces as cleanly."}], "meta": {"exam": "B", "qnum": 75, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We need to design a management network that lets us grant and revoke admin access, permits only SSH, NTP, FTP, and SNMP, and keeps management interfaces isolated from production traffic. Which management design should we use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - In-band management rides the production network, so it is harder to isolate and restrict management interfaces if production is compromised.\nB - Enterprise internal private is not a defined management-network design and does not inherently provide dedicated management-plane isolation.\nD - mGRE is a dynamic multipoint VPN overlay for tunneled traffic, not a management-network design for access control and interface isolation."}], "meta": {"exam": "B", "qnum": 75, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access fabric, what function does an intermediate node perform compared with edge, border, and control-plane nodes?"}, {"role": "assistant", "content": "Treat the intermediate node as a plain Layer 3 underlay router or switch that forwards IP traffic between fabric devices. It should not run LISP xTR, VXLAN tunnel termination, or anycast gateway functions; those belong to edge, border, and control-plane nodes. Its job is to provide routed transport so the fabric overlay nodes can reach each other."}], "meta": {"exam": "B", "qnum": 85, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco SD-Access fabric, what function does an intermediate node perform compared with edge, border, and control-plane nodes?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Acting as a LISP proxy tunnel router is the"}], "meta": {"exam": "B", "qnum": 85, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In our Cisco SD-Access fabric, endpoints in the same virtual network need to communicate, but we also need identity-based microsegmentation and filtering between them. What feature should we use to enforce that intra-VN traffic control?"}, {"role": "assistant", "content": "Use Scalable Groups (SGTs) with SGACLs as part of Cisco SD-Access group-based policy. SGTs classify endpoints by identity/role, and the fabric enforces SGACLs for traffic within the same VN, so filtering is not dependent on traditional IP prefix or interface ACL logic."}], "meta": {"exam": "B", "qnum": 95, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In our Cisco SD-Access fabric, endpoints in the same virtual network need to communicate, but we also need identity-based microsegmentation and filtering between them. What feature should we use to enforce that intra-VN traffic control?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Correct.\nB - MAC ACLs filter only with Layer 2 MAC address criteria and do not provide scalable identity-based intra-VN policy across the SD-Access fabric.\nC - Prefix lists match IP prefixes for routing protocol route filtering, not endpoint-to-endpoint traffic filtering inside a VN.\nD - Service policies typically apply QoS or interface-level service treatment and do not provide identity-based intra-VN segmentation."}], "meta": {"exam": "B", "qnum": 95, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In our campus OSPF design, every intra-area topology change from a Type 1 or Type 2 LSA triggers a full SPF run and high CPU. What OSPF feature should we enable to reduce that recomputation impact?"}, {"role": "assistant", "content": "Enable OSPF incremental SPF, also called iSPF. It limits SPT recomputation to the affected parts of the topology instead of running a full SPF for every intra-area Type 1 or Type 2 LSA change, improving convergence efficiency and reducing CPU load."}], "meta": {"exam": "B", "qnum": 101, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In our campus OSPF design, every intra-area topology change from a Type 1 or Type 2 LSA triggers a full SPF run and high CPU. What OSPF feature should we enable to reduce that recomputation impact?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - BFD is a fast failure-detection protocol and does not optimize OSPF SPT recomputation.\nC - SPF is the normal full shortest-path-first calculation; it is the process being optimized, not the optimization feature.\nD - PRC recalculates only affected routes after SPF but does not reduce the SPT recomputation caused by Type 1 or Type 2 LSA changes."}], "meta": {"exam": "B", "qnum": 101, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "When does a PIM router validate the RP address in its RPF check instead of the multicast source address?"}, {"role": "assistant", "content": "It does so when the router has shared-tree state, specifically a (*, G) entry using the RP as the upstream root. In PIM-SM, shared-tree traffic is RPF-checked toward the RP; source-tree traffic is RPF-checked toward the source. PIM-DM has no RP, so there is no RP-address RPF check in that mode."}], "meta": {"exam": "B", "qnum": 103, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: When does a PIM router validate the RP address in its RPF check instead of the multicast source address?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - A PIM-DM device receiving a packet with no directly connected members does not create an RP-based RPF check because PIM-DM"}], "meta": {"exam": "B", "qnum": 103, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "For a company comparing SaaS subscription software with an on-premises deployment, what cost and access characteristic should we highlight as the main feature of the SaaS model?"}, {"role": "assistant", "content": "Recommend highlighting lower initial costs: SaaS avoids large upfront hardware, software, and deployment purchases by using a recurring subscription. The provider manages the infrastructure and application delivery, so the customer’s upfront investment is much smaller than with on-premises software. The tradeoff is ongoing subscription fees and dependence on network/web access."}], "meta": {"exam": "B", "qnum": 108, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: For a company comparing SaaS subscription software with an on-premises deployment, what cost and access characteristic should we highlight as the main feature of the SaaS model?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - SaaS is normally delivered over the web or internet, so a web connection is generally required.\nC - SaaS reduces customer autonomy and control over hardware because the provider manages the infrastructure.\nD - Access to industrial-strength storage and computing power is more directly associated with IaaS/PaaS, and SaaS abstracts that infrastructure away"}], "meta": {"exam": "B", "qnum": 108, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What security does gRPC actually provide when we use it for model-driven telemetry between Cisco network devices and a controller?"}, {"role": "assistant", "content": "Use gRPC over TLS/HTTPS for that telemetry path. gRPC itself does not add a proprietary cipher or mandate storage encryption; its security comes from running over HTTP/2 with TLS, which encrypts the session and can authenticate the server or mutual peers. That makes TLS/HTTPS the correct security functionality for gRPC-based device-to-controller communication."}], "meta": {"exam": "B", "qnum": 109, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What security does gRPC actually provide when we use it for model-driven telemetry between Cisco network devices and a controller?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - gRPC does not use RC6 or CRC checks as its security mechanism.\nB - gRPC does not mandate AES/RSA encryption of data at rest.\nC - gRPC does not implement RSA 2048 cipher tunnels itself; it relies on TLS/HTTPS for transport security."}], "meta": {"exam": "B", "qnum": 109, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I'm designing a new SD-WAN architecture and want to align with Cisco's \"reinventing the WAN\" framework. What are the"}, {"role": "assistant", "content": "Cisco's \"reinventing the WAN\" framework for the CCNP ENSLD exam centers on three design pillars: Secure Elastic Connectivity, Application Quality of Experience, and Cloud First. Secure Elastic Connectivity uses an encrypted overlay (e.g., IPsec, DTLS) over any transport (MPLS, broadband, LTE/5G) to provide transport independence, dynamic path selection, and zero-trust segmentation. Application Quality of Experience applies application-aware routing, SLA-based policies, and per-application QoS to meet business intent across the SD-WAN fabric. Cloud First design optimizes direct access to SaaS/IaaS (e.g., Office 365, AWS) using local internet breakout and cloud on-ramps, avoiding backhaul through a centralized data center."}], "meta": {"exam": "B", "qnum": 117, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are trying to justify a Cisco ISE deployment to a customer who already has AAA and a firewall. What actual design benefits does ISE bring to their campus and WAN edge, beyond just authenticating users?"}, {"role": "assistant", "content": "Position ISE as the identity-based policy and containment layer, not just a RADIUS server. It delivers network access control — 802.1X/MAB enforcement, guest/BYOD onboarding, device profiling, and TrustSec segmentation — so the customer gets consistent zero-trust access decisions across wired, wireless, and VPN. It also provides real-time threat containment through pxGrid and ANC: when Stealthwatch or AMP detects malicious behavior, ISE can dynamically quarantine or disable that endpoint's port or session. That combination of enforced access and automated response is the measurable customer benefit."}], "meta": {"exam": "B", "qnum": 125, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are trying to justify a Cisco ISE deployment to a customer who already has AAA and a firewall. What actual design benefits does ISE bring to their campus and WAN edge, beyond just authenticating users?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A — ISE does not set traffic encryption across the network; MACsec, IPsec, and DMVPN provide that function.\nB — Accelerating application deployment and delivery is a DNA Center, SD-Access, or ACI capability, not an ISE feature."}], "meta": {"exam": "B", "qnum": 125, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "On the Cisco DNA Center Assurance Overall Health page, which two high-level health categories summarize the status of the deployment?"}, {"role": "assistant", "content": "Use Client and Network as the two primary categories. The Overall Health page rolls assurance telemetry into Network health for infrastructure and Client health for endpoints, giving the broadest summary before you drill into wired, wireless, access, distribution, core, or individual client details."}], "meta": {"exam": "B", "qnum": 130, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: On the Cisco DNA Center Assurance Overall Health page, which two high-level health categories summarize the status of the deployment?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Client is correct, not a distractor.\nB - Wired is a network subcategory or filter, not one of the two primary overall health categories.\nC - Access-Distribution is a topology layer, not a top-level Overall Health category.\nD - Core is a topology layer, not a top-level Overall Health category.\nE - Network is correct, not a distractor.\nF - Server is not one of the two primary health categories displayed on the Overall Health page."}], "meta": {"exam": "B", "qnum": 130, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access fabric, which component maintains the endpoint-to-RLOC mappings so that fabric edge nodes can forward traffic to the correct destination?"}, {"role": "assistant", "content": "Use the fabric control plane nodes running LISP map-server/map-resolver functions. They are responsible for registering EID-to-RLOC mappings from fabric edge nodes and resolving those mappings for destination lookups. The underlay provides IP reachability, the data plane encapsulates traffic in VXLAN, and the policy plane enforces group-based access control, but the control plane specifically creates and resolves endpoint-to-location mappings."}], "meta": {"exam": "C", "qnum": 4, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco SD-Access fabric, which component maintains the endpoint-to-RLOC mappings so that fabric edge nodes can forward traffic to the correct destination?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - This describes an underlay routing or BGP route-reflector/transit role, not the LISP-based endpoint mapping function of the fabric control plane.\nC - This describes a data-plane or overlay subnet-extension behavior, not the control plane’s purpose of endpoint-to-RLOC resolution.\nD - This describes the policy plane/GBAC function, typically handled through Cisco ISE and SGTs, not the fabric control plane."}], "meta": {"exam": "C", "qnum": 4, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access fabric, which role should I map to the traditional campus access layer switch that connects endpoint devices?"}, {"role": "assistant", "content": "Use the edge node role. It is the fabric node that attaches endpoints, handles their registration and authentication, encapsulates their traffic into VXLAN, and often provides the anycast gateway, so it corresponds most closely to a traditional access layer switch."}], "meta": {"exam": "C", "qnum": 5, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco SD-Access fabric, which role should I map to the traditional campus access layer switch that connects endpoint devices?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - The border node connects the SD-Access fabric to external networks and outside domains, so it is more analogous to a distribution/core boundary than an access switch.\nC - The intermediate node provides underlay transport and transit forwarding within the fabric, making it more like a core device than an endpoint-facing access switch.\nD - The control plane node provides"}], "meta": {"exam": "C", "qnum": 5, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-WAN design, which component maintains the centralized routing table that distributes overlay reachability and policy across the fabric?"}, {"role": "assistant", "content": "Use the vSmart"}], "meta": {"exam": "C", "qnum": 9, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "A company wants a simple IPv4 and IPv6 deployment strategy that avoids tunnels, translation, encapsulation overhead, and any mapping or information-hiding mechanisms. What should the architect propose?"}, {"role": "assistant", "content": "Recommend dual-stack: run IPv4 and IPv6 natively on hosts and network devices. This avoids GRE/LISP encapsulation and NAT64 translation,"}], "meta": {"exam": "C", "qnum": 19, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In Cisco SD-WAN, when I see service routes in OMP updates from edge devices, what are they actually used for in the fabric design?"}, {"role": "assistant", "content": "They are used for service insertion: OMP service routes advertise service-side reachability so vSmart can tell edges where to redirect traffic for services such as firewall, IPS, or application optimization. Rationale: service routes carry service VPN, label, TLOC, and service-type information, enabling policy-based service chaining rather than carrying management, orchestration, or underlay transport details."}], "meta": {"exam": "C", "qnum": 26, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In Cisco SD-WAN, when I see service routes in OMP updates from edge devices, what are they actually used for in the fabric design?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Remote management information is not advertised by OMP service routes; management access is handled through separate management-plane mechanisms.\nB - Routes toward a centralized orchestration plane are not the purpose of service routes; controller/orchestrator reachability is separate from service-chaining advertisements.\nC - Underlay transport information is described by TL"}], "meta": {"exam": "C", "qnum": 26, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In Cisco SD-Access, we use virtual networks to separate user groups and resources. What is that VN-level separation called, and how does it differ from SGT-based policy?"}, {"role": "assistant", "content": "It is called **macro-segmentation**. Use VNs/VRFs to provide coarse separation of routing and forwarding domains, then use SGTs and group-based policies for micro-segmentation inside a VN. The VN itself is the macro boundary; SGT enforcement provides the granular, intra-VN policy control."}], "meta": {"exam": "C", "qnum": 27, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In Cisco SD-Access, we use virtual networks to separate user groups and resources. What is that VN-level separation called, and how does it differ from SGT-based policy?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - “Stretched” generally refers to extending a Layer 2 domain or subnet across locations, not the SD-Access VN segmentation type.\nB - “Micro” describes SGT/group-based segmentation within a virtual network, not the VN-level separation.\nD - “Inter-VN” describes traffic between virtual networks, often involving a fusion router or route leaking, not the name of the segmentation type."}], "meta": {"exam": "C", "qnum": 27, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are designing service-to-service integration for a distributed network management platform and want a high-performance RPC framework with compact binary payloads and generated client/server stubs. What gRPC capability should we highlight when comparing it with REST/JSON or other integration approaches?"}, {"role": "assistant", "content": "Use gRPC for its Protocol Buffers-based serialization and deserialization of structured data, not for XMPP, GraphQL-style APIs, or LDAP integration. Protocol Buffers define services and messages in a language-neutral schema, then encode them efficiently on the wire, which reduces bandwidth and CPU overhead and enables generated stubs for clients and servers."}], "meta": {"exam": "C", "qnum": 29, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are designing service-to-service integration for a distributed network management platform and want a high-performance RPC framework with compact binary payloads and generated client/server stubs. What gRPC capability should we highlight when comparing it with REST/JSON or other integration approaches?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - XMPP is a real-time messaging and presence protocol, not the RPC serialization or integration mechanism used by g"}], "meta": {"exam": "C", "qnum": 29, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "On a PIM-SM router, when a multicast packet passes the RPF check, how does the router determine which interfaces should receive a copy?"}, {"role": "assistant", "content": "Forward the packet only on the interfaces in the multicast route’s OIL. In PIM"}], "meta": {"exam": "C", "qnum": 31, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our branches currently have only one MPLS provider, and a recent provider outage took down the WAN. We need a fast-to-deploy, cost-effective, and reliable backup to the MPLS primary. What design should we use?"}, {"role": "assistant", "content": "Deploy a business internet circuit at each site and build a DMVPN overlay over it, keeping MPLS as the preferred primary path and using routing preference or a floating static route for failover. DMVPN gives you a secure IPsec overlay over the internet with mGRE and NHRP, so it is quick to deploy, affordable compared with a second MPLS provider, and reliable as a backup. It also supports dynamic routing, which lets the network reconverge to the internet path when the MPLS provider fails."}], "meta": {"exam": "C", "qnum": 35, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Our branches currently have only one MPLS provider, and a recent provider outage took down the WAN. We need a fast-to-deploy, cost-effective, and reliable backup to the MPLS primary. What design should we use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Adding another WAN router and a floating static route does not"}], "meta": {"exam": "C", "qnum": 35, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need to connect two hosts—one in Company A and one in Company B—over the internet with encryption. There will never be any additional sites, and we want the simplest possible configuration. What should we use?"}, {"role": "assistant", "content": "Use a policy-based IPsec tunnel with static routing. For only two fixed endpoints, a crypto ACL can match the required traffic and IPsec can encrypt it directly between peers, while static routes keep forwarding simple. There is no need for dynamic routing, GRE/VTI interfaces, DMVPN, or an MPLS VPN service."}], "meta": {"exam": "C", "qnum": 52, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We need to connect two hosts—one in Company A and one in Company B—over the internet with encryption. There will never be any additional sites, and we want the simplest possible configuration. What should we use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B -"}], "meta": {"exam": "C", "qnum": 52, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "When migrating from a carrier-managed IP-VPN to Cisco SD-WAN, which architecture benefits should I expect to gain?"}, {"role": "assistant", "content": "Expect better scalability and centralized application policy control as the key design gains. Cisco SD-WAN centralizes control via vSmart, uses OMP and templates for scalable site/transport onboarding, and lets vManage/vSmart apply application-aware routing, QoS, and segmentation policies consistently across the overlay. These are the core improvements over"}], "meta": {"exam": "C", "qnum": 56, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access fabric, which fabric role should I deploy to route traffic between fabric endpoints and an external data center or legacy WAN?"}, {"role": "assistant", "content": "Use border nodes. They are the fabric boundary devices that connect SD-Access to external Layer 3 networks, perform VXLAN-to-VLAN/VRF handoff, and exchange routes with external routers via protocols such as BGP or OSPF. Control plane nodes provide LISP mapping services, edge nodes connect endpoints, and intermediate nodes carry underlay traffic, but external communication is a border-node function."}], "meta": {"exam": "C", "qnum": 89, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco SD-Access fabric, which fabric role should I deploy to route traffic between fabric endpoints and an external data center or legacy WAN?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Control plane nodes provide LISP map-server/map-resolver functions and do not peer with external networks for fabric external connectivity.\nC - Intermediate nodes are under"}], "meta": {"exam": "C", "qnum": 89, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have a printer connected to a switch port that does not run an 802.1X supplicant. How should Cisco ISE authenticate and authorize it while still keeping port-based access control?"}, {"role": "assistant", "content": "Use MAB on the switch port and configure Cisco ISE to authorize the printer based on its MAC address, ideally with profiling to confirm it is a printer.\nThe printer cannot do 802.1X because it lacks a supp"}], "meta": {"exam": "C", "qnum": 91, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco ISE deployment, what are the main functions it provides for endpoint visibility and enforcing security policy?"}, {"role": "assistant", "content": "The two primary functions are enforcing endpoint compliance and providing information about every device that touches the network. ISE identifies and profiles endpoints using RADIUS, 802.1X, MAB, and posture, then applies authorization policies to enforce compliance and network access rules."}], "meta": {"exam": "C", "qnum": 98, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco ISE deployment, what are the main functions it provides for endpoint visibility and enforcing security policy?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Enabling WAN deployment over any type of connection is a function of Cisco SD-WAN, not Cisco ISE.\nC - Automatically enabling, disabling, or reducing power to devices is Power over Ethernet negotiation, not a primary ISE function.\nE - Providing encryption for mobile devices is typically handled by VPN, IPsec, or SSL, not Cisco ISE.\nF - Allocating cloud resources is a cloud orchestration/management function, not Cisco ISE."}], "meta": {"exam": "C", "qnum": 98, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need a WAN service that gives us end-to-end QoS for VoIP and business applications using CoS markings, lets us run IPv6 and multicast ourselves without depending on the carrier, and provides any-to-any Layer 2 connectivity between all sites. Which WAN connectivity option should we choose?"}, {"role": "assistant", "content": "Choose VPLS. VPLS provides a multipoint Layer 2 Ethernet service with full-mesh site connectivity, preserves CoS/802.1p marking for QoS, and lets the enterprise handle its own IPv6 and multicast routing at Layer 3 without relying on the service provider."}], "meta": {"exam": "A", "qnum": 4, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We need a WAN service that gives us end-to-end QoS for VoIP and business applications using CoS markings, lets us run IPv6 and multicast ourselves without depending on the carrier, and provides any-to-any Layer 2 connectivity between all sites. Which WAN connectivity option should we choose?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - VPWS is a point-to-point Layer 2 service, so it cannot provide full-mesh Layer 2 connectivity across multiple sites.\nB - MPLS VPN is a Layer 3 VPN where the provider typically participates in routing, and IPv6 or multicast support may depend on provider offerings.\nC - DMVPN is a Layer 3 overlay over an IP underlay, not a Layer 2 full-mesh service, so it does not transparently carry CoS-marked Layer 2 traffic end to end."}], "meta": {"exam": "A", "qnum": 4, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are redesigning first-hop redundancy and considering VRRPv3 instead of VRRPv2. What real protocol benefit should drive that choice?"}, {"role": "assistant", "content": "Choose VRRPv3 when you need VRRP for both IPv4 and IPv6; its key benefit is dual-stack support in a single version. VRRPv3 supports IPv4 and IPv6, while VRRPv2 supports only IPv4. That makes VRRPv3 more suitable for modern dual-stack campus or WAN designs without running separate redundancy protocols per address family."}], "meta": {"exam": "A", "qnum": 5, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are redesigning first-hop redundancy and considering VRRPv3 instead of VRRPv2. What real protocol benefit should drive that choice?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Authentication was supported in VRRPv2 and deprecated in VRRPv3, so it is not a VRRPv3 advantage.\nC - Preemption is supported by both VRRPv2 and VRRPv3, so it is not unique to v3.\nD - VRRP provides gateway redundancy failover, not stateful switchover of session or connection state."}], "meta": {"exam": "A", "qnum": 5, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are designing a large PIM-SM multicast domain and want to avoid configuring the same rendezvous point manually on every router or using a vendor-specific method. What open-standard mechanism can dynamically distribute RP information and support RP redundancy?"}, {"role": "assistant", "content": "Use PIM Bootstrap Router, or BSR. BSR lets candidate RPs advertise their candidacy to an elected bootstrap router, which then floods a consistent RP-set to all PIM routers; this automates RP distribution and supports redundancy across a large multi-vendor domain, unlike Cisco-proprietary Auto-RP or manual static RP configuration."}], "meta": {"exam": "A", "qnum": 7, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are designing a large PIM-SM multicast domain and want to avoid configuring the same rendezvous point manually on every router or using a vendor-specific method. What open-standard mechanism can dynamically distribute RP information and support RP redundancy?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Embedded RP encodes an RP address in an IPv6 multicast group address, but it does not provide scalable dynamic RP-set distribution and redundancy for a large PIM domain.\nC - Auto-RP automates RP distribution but is Cisco proprietary, so it fails the nonproprietary requirement.\nD - Static RP requires manual configuration on every router and does not automate rendezvous point distribution."}], "meta": {"exam": "A", "qnum": 7, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need to connect an isolated IPv6 site across our existing IPv4 core. How should we treat an IPv6 overlay tunnel in the long-term network design?"}, {"role": "assistant", "content": "Treat it as a temporary transition technique and plan a native IPv6 path as the permanent solution. Overlay tunnels can bridge isolated IPv6 networks, but they add MTU, security, scalability, and operational complexity, so they should not be the final IPv6 design."}], "meta": {"exam": "A", "qnum": 12, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We need to connect an isolated IPv6 site across our existing IPv4 core. How should we treat an IPv6 overlay tunnel in the long-term network design?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Overlay tunnels are transition aids, not a final IPv6 network architecture.\nC - Overlay tunnels can be used on more than border devices and generally require an IPv4 underlay or dual-stack support, not only IPv6.\nD - Overlay tunneling typically encapsulates IPv6 packets inside IPv4 packets for transit across an IPv4 infrastructure, not IPv4 inside IPv6."}], "meta": {"exam": "A", "qnum": 12, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "When designing an IS-IS network, which interface circuit types can I use natively between routers?"}, {"role": "assistant", "content": "Use IS-IS on point-to-point and multiaccess/broadcast circuits only. IS-IS natively supports these two circuit types: point-to-point links form direct adjacencies, while multiaccess links elect a DIS and use pseudonode LSPs. It does not natively support NBMA, point-to-multipoint, or generic nonbroadcast modes."}], "meta": {"exam": "A", "qnum": 13, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: When designing an IS-IS network, which interface circuit types can I use natively between routers?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - NBMA is not a native IS-IS circuit type; such links are normally modeled as point-to-point subinterfaces or broadcast-capable links.\nC - Point-to-multipoint is an OSPF interface concept, not a native IS-IS circuit type.\nD - Nonbroadcast is not an IS-IS circuit type; IS-IS only defines point-to-point and broadcast/multiaccess operation."}], "meta": {"exam": "A", "qnum": 13, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our campus has management stations in one VLAN and sleeping workstations in another VLAN; what Layer 3 design setting do we need so Wake-on-LAN magic packets can reach those workstations across the subnet boundary?"}, {"role": "assistant", "content": "Enable IP directed broadcasts on the Layer 3 interface for the target workstation VLAN, with strict ACLs limiting which source networks can send WoL traffic. WoL magic packets are normally broadcast on the target subnet, and routers drop subnet-directed broadcasts by default; allowing directed broadcasts on the destination Layer 3 device lets the magic packet be forwarded to the target VLAN as a broadcast so the NIC can wake the host."}], "meta": {"exam": "A", "qnum": 16, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Our campus has management stations in one VLAN and sleeping workstations in another VLAN; what Layer 3 design setting do we need so Wake-on-LAN magic packets can reach those workstations across the subnet boundary?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Dynamic ARP Inspection validates ARP packets against DHCP snooping bindings, but it does not forward or permit Wake-on-LAN broadcasts across subnets.\nC - Proxy ARP lets a router answer ARP requests for remote hosts, but it has no role in carrying the WoL magic packet to a sleeping host.\nD - DHCP Snooping filters DHCP messages and builds binding tables, but it does not enable or forward Wake-on-LAN broadcasts."}], "meta": {"exam": "A", "qnum": 16, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m documenting Cisco SD-WAN control-plane behavior: what route types does OMP advertise between the controllers and WAN Edge routers?"}, {"role": "assistant", "content": "Cisco SD-WAN OMP advertises prefix routes, TLOC routes, and service routes. Prefix routes carry VPN/prefix reachability, TLOC routes identify transport locators and tunnel endpoints, and service routes support service-side reachability and service insertion."}], "meta": {"exam": "A", "qnum": 22, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I’m documenting Cisco SD-WAN control-plane behavior: what route types does OMP advertise between the controllers and WAN Edge routers?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Underlay, MPLS, and overlay are network layers or transport types"}], "meta": {"exam": "A", "qnum": 22, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need to connect two sites over the public Internet and securely pass multicast traffic, including routing protocol updates, between them. What tunneling design should I use?"}, {"role": "assistant", "content": "Use GRE over IPsec. GRE encapsulates the multicast and routing-protocol packets so they can traverse the public network, and IPsec protects the GRE tunnel with encryption and authentication; plain IPsec will not carry multicast natively, and plain GRE is not secure."}], "meta": {"exam": "A", "qnum": 39, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We need to connect two sites over the public Internet and securely pass multicast traffic, including routing protocol updates, between them. What tunneling design should I use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - IPsec alone does not natively support multicast traffic, so it cannot securely tunnel the required multicast flows by itself. \nB - GRE supports multicast and routing protocols, but without IPsec it does not provide the required security over a public network. \nC - PPTP is an obsolete point-to-point tunneling protocol that does not support multicast routing or modern secure site-to-site design requirements."}], "meta": {"exam": "A", "qnum": 39, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m designing an out-of-band management network for Cisco enterprise devices. What design practices should I prioritize to keep management secure and reliable?"}, {"role": "assistant", "content": "Use a dedicated, isolated management network and enforce strict access control. Keep management traffic separate from production data using dedicated interfaces or a management VRF, and restrict access with AAA, RBAC, ACLs, and encrypted protocols. This prevents production outages or compromises from exposing the management plane and ensures only authorized administrators can reach it."}], "meta": {"exam": "A", "qnum": 40, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I’m designing an out-of-band management network for Cisco enterprise devices. What design practices should I prioritize to keep management secure and reliable?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Facilitating network integration is not a required OOB design practice and can weaken the isolation that management traffic needs.\nC - Backing up data over the management network mixes production data with the management plane and can congest or expose the OOB path.\nD - The management network is not meant to serve as a backup data path; it should remain separate from production forwarding."}], "meta": {"exam": "A", "qnum": 40, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our OSPF network is slow to converge after link or neighbor failures. What practical steps can we take to improve OSPF convergence?"}, {"role": "assistant", "content": "Enable BFD on OSPF links and tune OSPF convergence-related parameters. BFD gives sub-second failure detection, while tuned hello/dead timers and SPF/LSA throttling reduce how long OSPF waits before detecting a failure and recalculating routes. Avoid redesigns that simply collapse areas or overlap subnets, since those can hurt scalability and stability more than they help convergence."}], "meta": {"exam": "A", "qnum": 44, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Our OSPF network is slow to converge after link or neighbor failures. What practical steps can we take to improve OSPF convergence?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Merging all areas into one backbone area creates a larger LSDB and more SPF work, typically worsening scalability and convergence.\nD - Making all non-backbone areas stub areas may reduce LSAs, but it is not a general OSPF convergence fix and cannot apply to the backbone or every area type.\nE - Spanning the same IP network across multiple areas violates normal OSPF area design and can create routing ambiguity rather than faster convergence."}], "meta": {"exam": "A", "qnum": 44, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I am designing a multivendor campus LAN that uses Spanning Tree for Layer 2 loop prevention. I need to group all VLANs into two Spanning Tree instances. Which standards-based Spanning Tree technology should I use?"}, {"role": "assistant", "content": "Use MSTP. MSTP is standards-based and lets you map groups of VLANs into a small number of Spanning Tree Instances, so two instances can be configured across multivendor switches. It provides loop prevention and allows different VLAN groups to use different forwarding topologies without requiring a separate STP instance per VLAN."}], "meta": {"exam": "A", "qnum": 45, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I am designing a multivendor campus LAN that uses Spanning Tree for Layer 2 loop prevention. I need to group all VLANs into two Spanning Tree instances. Which standards-based Spanning Tree technology should I use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - RSTP is standards-based but provides only a single spanning-tree topology and does not support VLAN-to-instance grouping.\nC - Rapid PVST is Cisco-proprietary and creates one instance per VLAN, so it is not the standards-based two-instance design requested.\nD - STP is standards-based but legacy and single-instance, with no support for grouping VLANs into separate Spanning Tree Instances."}], "meta": {"exam": "A", "qnum": 45, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need the same IP subnet to appear at two data centers and let hosts keep their addresses when they move between them. What control-plane technology should we use?"}, {"role": "assistant", "content": "Use LISP. LISP’s EID-to-RLOC mapping control plane decouples the endpoint subnet from its physical location, so the same EID prefix"}], "meta": {"exam": "A", "qnum": 46, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our network is IPv4-only today, but we need to add IPv6 connectivity while keeping all existing IPv4 services working. We plan to gradually move services onto IPv6 and then retire IPv4 entirely. What topology approach should we use?"}, {"role": "assistant", "content": "Use dual stack on the relevant devices and interfaces. It preserves the existing IPv4 topology and services while enabling native IPv6 connectivity in parallel, and it lets you migrate services incrementally before removing IPv4. Because IPv4 and IPv6 are routed independently, you avoid translation or tunneling dependencies that would keep IPv4 required during and after the transition."}], "meta": {"exam": "A", "qnum": 48, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Our network is IPv4-only today, but we need to add IPv6 connectivity while keeping all existing IPv4 services working. We plan to gradually move services onto IPv6 and then retire IPv4 entirely. What topology approach should we use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - 6VPE carries IPv6 VPN traffic over an IPv4/MPLS core, but it does not provide a general native IPv6 migration path that can fully decommission the IPv4 topology.\nC - 6to4 is an automatic IPv4-to-IPv6 tunneling method that still depends on IPv4 reachability and is not suitable for retiring IPv4.\nD - NAT64 translates between IPv6-only and IPv4-only systems, so it does not preserve native IPv4 topology services or allow clean IPv4 decommissioning."}], "meta": {"exam": "A", "qnum": 48, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our WAN uses eBGP to multiple service providers, with one primary path and backup paths. We need the backup path to take over very quickly when the primary link fails, but we cannot increase router CPU by aggressively tuning BGP timers. What design should we use?"}, {"role": "assistant", "content": "Enable BFD on the primary eBGP sessions and keep the default BGP keepalive/hold timers. BFD detects failure in subsecond time and triggers the BGP session reset, causing immediate route withdrawal and reconver"}], "meta": {"exam": "A", "qnum": 49, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In an SD-Access fabric, which role authenticates endpoints and registers their location information with the fabric control plane?"}, {"role": "assistant", "content": "Use the fabric edge node. The edge node is the endpoint-facing first hop: it authenticates or identifies endpoints, learns their MAC/IP information, and registers the EID-to-location mapping with the control plane node. Control plane nodes maintain and resolve mappings, while border nodes provide outside connectivity, so the edge node is the correct role for endpoint onboarding and registration."}], "meta": {"exam": "A", "qnum": 51, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In an SD-Access fabric, which role authenticates endpoints and registers their location information with the fabric control plane?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - This describes the control plane node’s mapping database, not the edge node’s endpoint-facing role.\nC - This describes the border node, which connects the fabric to external networks.\nD - This describes the control plane node resolving lookup requests for edge and border nodes."}], "meta": {"exam": "A", "qnum": 51, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m designing an IS-IS network for three interconnected campuses. I need a two-level hierarchy so each campus is segregated and detailed routes from one campus are not automatically advertised to routers in the other campuses. What should I configure on the internal routers and at each campus edge?"}, {"role": "assistant", "content": "Use a unique IS-IS NET/area per campus, configure internal campus routers as Level"}], "meta": {"exam": "A", "qnum": 78, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In our Cisco SD-Access fabric, we need security policy that follows a user or device wherever it connects and restricts east-west traffic between logical groups, not just between VLANs or VRFs. What mechanism should we use to enforce end-to-end microsegmentation?"}, {"role": "assistant", "content": "Use SGTs and SGACLs managed by Cisco DNA Center. The fabric assigns an SGT to the endpoint at ingress, carries it across the VXLAN fabric, and enforces SGACLs between source and destination groups at the fabric edge, giving identity-based microsegmentation that is independent of IP subnet or VLAN placement."}], "meta": {"exam": "A", "qnum": 82, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In our Cisco SD-Access fabric, we need security policy that follows a user or device wherever it connects and restricts east-west traffic between logical groups, not just between VLANs or VRFs. What mechanism should we use to enforce end-to-end microsegmentation?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - VLANs provide Layer 2 segmentation, but they do not provide identity-based end-to-end microsegmentation in SD-Access.\nB - Traditional 5-tuple ACL"}], "meta": {"exam": "A", "qnum": 82, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are replacing MPLS T1 store links to our data center and need multicast for training, dynamic routing, QoS, and new stores to form tunnels to the hub without hub-side tunnel changes. What design should we use?"}, {"role": "assistant", "content": "Use DMVPN. DMVPN provides dynamic hub-and-spoke mGRE tunnels with NHRP registration, supports routing protocols and QoS over the tunnel, and can carry multicast for training; IPsec can be added for encryption. It scales better than static IPsec tunnels and does not require reconfiguring the hub each time a store is added."}], "meta": {"exam": "A", "qnum": 87, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are replacing MPLS T1 store links to our data center and need multicast for training, dynamic routing, QoS, and new stores to form tunnels to the hub without hub-side tunnel changes. What design should we use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A. VPLS is a provider-based Layer 2 multipoint service that can carry routing and multicast, but it does not provide dynamic hub-created tunnels or reduce dependency on WAN provider configuration.\nB. GET VPN is scalable group IPsec that preserves routing, multicast, and QoS, but it uses a key server/group-member model rather than dynamic per-store hub-and-spoke tunnels.\nD. IPsec alone can secure"}], "meta": {"exam": "A", "qnum": 87, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I need a PIM mode where multicast traffic for a group always stays on the RP-rooted shared tree and never builds source-specific shortest-path trees. Which PIM mode should I use?"}, {"role": "assistant", "content": "Use PIM Bidirectional (PIM Bidir). It uses only a bidirectional shared tree rooted at the RP, with no source-specific SPTs or SPT switchover, which fits designs that require shared-tree-only forwarding."}], "meta": {"exam": "A", "qnum": 90, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I need a PIM mode where multicast traffic for a group always stays on the RP-rooted shared tree and never builds source-specific shortest-path trees. Which PIM mode should I use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - PIM Sparse Mode starts on an RP-rooted shared tree but can switch to source-specific shortest-path trees, so it is not shared-tree-only.\nC - PIM Dense Mode uses flood-and-prune behavior to build source-based"}], "meta": {"exam": "A", "qnum": 90, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are troubleshooting PIM-SM multicast traffic, and a router is receiving multicast packets on an interface that is not the one it uses to reach the source. Why does PIM drop those packets, and what is the RPF check actually doing?"}, {"role": "assistant", "content": "That behavior is expected: PIM performs an RPF check against the unicast route to the source, or toward the RP for a shared tree, and drops the packet if it did not arrive on the expected RPF interface. This check enforces the reverse path and builds a loop-free multicast distribution tree from source to receivers."}], "meta": {"exam": "A", "qnum": 92, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are troubleshooting PIM-SM multicast traffic, and a router is receiving multicast packets on an interface that is not the one it uses to reach the source. Why does PIM drop those packets, and what is the RPF check actually doing?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Auto-RP mapping agents distribute group-to-RP mappings and are unrelated to the multicast RPF check.\nC - Bootstrap messages are PIM BSR control messages meant to reach PIM routers; the RPF check is not designed to block them from all routers.\nD - Discovering and announcing"}], "meta": {"exam": "A", "qnum": 92, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have more than 100 routers and want to divide the multicast network into multiple PIM-SM domains while balancing traffic across RPs. What technology should we include?"}, {"role": "assistant", "content": "Use MSDP. It enables inter-domain PIM-SM source discovery and supports anycast RP designs, allowing multiple RPs to share the load and synchronize active multicast sources across domains. This is the standard scalable approach for multi-domain PIM-SM networks."}], "meta": {"exam": "A", "qnum": 94, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We have more than 100 routers and want to divide the multicast network into multiple PIM-SM domains while balancing traffic across RPs. What technology should we include?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - DVMRP is a legacy dense-mode multicast routing protocol and does not support the required PIM-SM inter-domain design.\nB - IGMP manages host-to-router group membership and does not provide inter-domain multicast source discovery.\nC - MOSPF is an OSPF-based multicast extension and is not used to interconnect PIM-SM domains or balance RPs."}], "meta": {"exam": "A", "qnum": 94, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m designing a Layer 3 campus with EIGRP between the core, aggregation, and access layers. The access switches connect to the aggregation layer over Layer 3 copper links, and I need faster convergence when an access switch fails. What should I include in the design?"}, {"role": "assistant", "content": "Enable BFD for EIGRP on the Layer 3 access-to-aggregation uplinks. BFD gives sub-second failure detection and triggers EIGRP immediately, so the aggregation layer does not have to wait for EIGRP Hello/Hold timers to"}], "meta": {"exam": "A", "qnum": 96, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are migrating a large network to IPv6 and want applications to prefer IPv6 when DNS returns an AAAA record, but still fall back to IPv4 when only an A record is available. Which migration strategy should we design?"}, {"role": "assistant", "content": "Use dual stack, with IPv4 and IPv6 enabled on hosts, applications, and DNS, so applications can choose the address family from DNS responses. This is the only listed strategy that natively supports DNS-driven selection between IPv4 and IPv6; AAAA presence drives IPv6 preference, and A-only responses drive IPv4 fallback."}], "meta": {"exam": "A", "qnum": 106, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are migrating a large network to IPv6 and want applications to prefer IPv6 when DNS returns an AAAA record, but still fall back to IPv4 when only an A record is available. Which migration strategy should we design?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - AFT translates between address families and does not provide native application selection based on DNS A/AAAA responses.\nB - Host-initiated tunnels encapsulate IPv6 over IPv4 from the host and do not make the application choose between IPv4 and IPv6 via DNS.\nD - Site-to-site IPv6 over IPv4 tunnels connect IPv6 sites across an IPv4 core and do not provide per-application DNS-based address-family selection."}], "meta": {"exam": "A", "qnum": 106, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We currently mark traffic with IP Precedence and want to migrate to DiffServ while keeping compatibility with those existing markings. What DiffServ mechanism should we include in the design?"}, {"role": "assistant", "content": "Use DiffServ class selector (CS) code points. They map directly to the legacy IP Precedence values, so existing precedence-based classifications remain compatible while the network moves to DSCP-based QoS."}], "meta": {"exam": "A", "qnum": 112, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We currently mark traffic with IP Precedence and want to migrate to DiffServ while keeping compatibility with those existing markings. What DiffServ mechanism should we include in the design?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Expedited forwarding provides low-latency treatment but does not provide IP Precedence backward compatibility.\nB - Assured forwarding defines classes and drop precedence but does not directly preserve legacy IP Precedence markings.\nD - Default per-hop behavior is best-effort treatment and does not provide the required legacy mapping."}], "meta": {"exam": "A", "qnum": 112, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our Layer 2 network is running 802.1d, and every VLAN and trunk change is manually configured on each switch. We need faster recovery from topology changes, less administrative effort, and"}, {"role": "assistant", "content": "Rapid PVST+ replaces legacy 802.1d with 802.1w rapid spanning-tree behavior per VLAN, so link/topology changes converge much faster and have less impact on the Layer 2 domain. VTP propagates the VLAN database automatically, and VTP pruning prevents unnecessary VLAN traffic from being flooded across trunks. Together, these reduce manual switch-by-switch VLAN configuration and lower the chance of human error. Storm control and DTP do not address topology-change impact or centralized VLAN administration."}], "meta": {"exam": "A", "qnum": 113, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have sustained congestion on the access-to-distribution uplinks, and QoS is already implemented and optimized but no longer solving the performance issue. What design changes should I make?"}, {"role": "assistant", "content": "Add uplink capacity: implement higher-speed uplink interfaces and bundle additional uplinks into logical EtherChannels. QoS can prioritize or shape traffic, but it cannot fix a persistent bandwidth shortage; sustained congestion requires more capacity. EtherChannels also scale bandwidth efficiently and avoid STP blocking individual member links."}], "meta": {"exam": "A", "qnum": 117, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We have sustained congestion on the access-to-distribution uplinks, and QoS is already implemented and optimized but no longer solving the performance issue. What design changes should I make?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Reconfiguring QoS to IntServ does not add bandwidth and is not the right fix for sustained uplink congestion.\nB - RED helps manage queue behavior and reduce tail-drop effects, but it does not increase uplink capacity.\nE - Selective packet discard drops noncritical traffic during congestion, which is a congestion-management tactic, not a capacity or performance improvement."}], "meta": {"exam": "A", "qnum": 117, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a multivendor PIM-SM network, I need all routers to learn RP information automatically and I cannot rely on Cisco-proprietary discovery, so which RP deployment method should I use?"}, {"role": "assistant", "content": "Use bootstrap router (BSR). BSR is standards-based and dynamically distributes group-to-RP mappings through bootstrap messages, allowing PIM routers to discover the RP set automatically. Auto-RP is dynamic but Cisco proprietary, static RP requires manual configuration, and Anycast-RP provides redundancy but not dynamic RP discovery on its own."}], "meta": {"exam": "A", "qnum": 126, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a multivendor PIM-SM network, I need all routers to learn RP information automatically and I cannot rely on Cisco-proprietary discovery, so which RP deployment method should I use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Auto-RP supports dynamic RP discovery, but it is a Cisco-proprietary mechanism rather than a standards-based one.\nB - Anycast-RP is standards-based for RP redundancy, but it does not itself provide dynamic RP discovery.\nD - Static RP requires manual RP configuration on routers and does not support dynamic RP discovery."}], "meta": {"exam": "A", "qnum": 126, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are building a microservice that integrates with OpenDaylight to automate DR-test changes across a mix of Cisco, Juniper, and Arista routing and switching gear. The workflow will change over time. What type"}, {"role": "assistant", "content": "B is correct because an open/standard YANG model, such as IETF or OpenConfig, gives the OpenDaylight controller and the thin microservice a vendor-neutral data model to program. In a DR playbook with diverse routing, switching, multi-vendor, and multi-platform assets, standard models let the same application logic and code paths be reused across devices instead of building per-vendor workflows. OpenDaylight is model-driven and can expose standard YANG models northbound while translating to vendor-specific southbound drivers. This decoupling is important because the DR playbook will change over time: the microservice can be updated against a stable standard model rather than rewritten for each vendor’s native model."}], "meta": {"exam": "A", "qnum": 128, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We run HSRP between two core routers, and after growth some downstream links are nearly saturated while others are lightly used. What design change will balance traffic across both routers without adding hardware?"}, {"role": "assistant", "content": "Use multiple HSRP groups and make each core router active for a different set of VLANs. Configure R1 with higher priority for some VLANs and R2 with higher priority for the remaining VLANs, so downstream VLANs use both active gateways and both sets of links. This distributes traffic across the core routers and their downstream interfaces instead of leaving one router as the active forwarder for every VLAN."}], "meta": {"exam": "B", "qnum": 19, "topic": "", "has_exhibit": true, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We run HSRP between two core routers, and after growth some downstream links are nearly saturated while others are lightly used. What design change will balance traffic across both routers without adding hardware?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Adding more interfaces can add raw capacity, but it does not fix the HSRP active/standby imbalance that leaves some links underused.\nC - A port channel toward downstream switches increases bandwidth on a specific link bundle, but traffic may still be pinned through the single HSRP active router.\nD - Enabling RSTP affects Layer 2 loop prevention and topology convergence, not HSRP first-hop load distribution or core link utilization."}], "meta": {"exam": "B", "qnum": 19, "topic": "", "has_exhibit": true, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In Cisco SD-WAN, which WAN Edge VPN ID should be used as the transport VPN for WAN underlay connectivity and control-plane traffic to the controllers?"}, {"role": "assistant", "content": "Use VPN 0 as the transport VPN on the WAN Edge. VPN 0 is the predefined underlay VPN where WAN transport interfaces, TLOCs, and controller control connections are configured. It carries the DTLS/TLS control sessions to vManage, vBond, and vSmart, along with related transport-side protocols such as BFD and OMP signaling. VPN 512 and the service VPN ranges are reserved for management and data traffic, respectively."}], "meta": {"exam": "B", "qnum": 27, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In Cisco SD-WAN, which WAN Edge VPN ID should be used as the transport VPN for WAN underlay connectivity and control-plane traffic to the controllers?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - VPN 0 is correct because it is the SD-WAN transport VPN that carries WAN Edge control traffic.\nB - VPN 512 is the management VPN used for out-of-band management, not the transport VPN.\nC - VPN 128 is a service VPN ID used for user/data traffic, not transport control.\nD - VPN 256 is a service VPN ID and does not carry the WAN Edge transport control traffic."}], "meta": {"exam": "B", "qnum": 27, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have a 1 Gbps ISP link with a 100 Mbps CIR, and the ISP drops everything above the CIR, causing TCP retransmissions. We don’t run voice or RTP, but we want to use as much of the CIR as possible. What QoS design should we use on our side?"}, {"role": "assistant", "content": "Use traffic shaping toward the ISP. Shape the outbound traffic to the 100 Mbps CIR, ideally with a small burst allowance, so excess packets are buffered and paced instead of dropped by the ISP. Since there are no RTP applications, the shaping delay is acceptable, and this reduces TCP retransmissions while keeping utilization up to the CIR."}], "meta": {"exam": "B", "qnum": 29, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We have a 1 Gbps ISP link with a 100 Mbps CIR, and the ISP drops everything above the CIR, causing TCP retransmissions. We don’t run voice or RTP, but we want to use as much of the CIR as possible. What QoS design should we use on our side?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Policing drops or remarks traffic that exceeds the rate, which can increase TCP retransmissions and does not smooth traffic to the ISP CIR.\nB - Queuing only provides scheduling during congestion and does not by itself enforce the 100 Mbps CIR on a 1 Gbps link.\nD - A policer with markdown still allows excess traffic to be sent toward the ISP, so the ISP may aggressively drop it and cause retransmissions."}], "meta": {"exam": "B", "qnum": 29, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m designing multicast for a financial application where most multicast sources also receive multicast traffic, so it is a many-to-many deployment. We want to keep multicast routing state lean and explicitly avoid source-based trees. Which multicast protocol should I use?"}, {"role": "assistant", "content": "Use BIDIR-PIM. It builds one bidirectional shared tree per group rooted at the RP, so all sources and receivers use (, G) forwarding state and no (S, G) source trees are created. That matches a many-to-many model and minimizes multicast routing state, unlike PIM-SM which may switch to source trees, PIM-SSM which is source-tree-only, or MSDP which is only a source-discovery mechanism."}], "meta": {"exam": "B", "qnum": 37, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I’m designing multicast for a financial application where most multicast sources also receive multicast traffic, so it is a many-to-many deployment. We want to keep multicast routing state lean and explicitly avoid source-based trees. Which multicast protocol should I use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - PIM-SM can use a shared tree, but it commonly transitions to source-specific shortest-path trees, so it does not strictly satisfy the no-source-tree requirement.\nC - MSDP is an interdomain source-discovery mechanism used with PIM-SM, not a multicast routing protocol that removes source trees.\nD - PIM-SSM builds only source-specific (S, G) trees, which directly violates the design requirement to avoid source trees."}], "meta": {"exam": "B", "qnum": 37, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are deploying PIM-SM Anycast RP across two data centers. What should we configure so RP1 and RP2 exchange information about multicast sources that have joined locally in each site?"}, {"role": "assistant", "content": "Configure MSDP peering between the two RPs using separate unique loopback interfaces, while keeping the shared Anycast RP address on its own loopback. The unique loopbacks give each RP a distinct MSDP peer address, and MSDP Source-Active messages let each RP learn about sources registered or joined in the other site. The shared Anycast RP address is used by PIM clients, not as the MSDP peer address."}], "meta": {"exam": "B", "qnum": 54, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are deploying PIM-SM Anycast RP across two data centers. What should we configure so RP1 and RP2 exchange information about multicast sources that have joined locally in each site?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Extending the same IP subnet at Layer 2 is unnecessary and creates spanning/failure-domain issues; Anycast RP does not require a shared L2 subnet.\nC - Using the shared Anycast RP address for MSDP peering is ambiguous because both RPs have the same address, so MSDP needs separate unique peer addresses.\nD - PIM registers do not automatically reach every RP; each source registers only with the topologically closest Anycast RP unless MSDP shares source information."}], "meta": {"exam": "B", "qnum": 54, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We see brief outages whenever an OSPF link or router fails because the backup path is not used until OSPF reconverges. What should we deploy to keep traffic flowing during that OSPF recalculation?"}, {"role": "assistant", "content": "Implement LFA FRR in OSPF. It precomputes and installs a loop-free backup next hop in the FIB, so the local router switches traffic immediately at failure detection while OSPF runs SPF and converges, preventing the short outage. BFD can speed up failure detection, but FRR is what provides the fast local repair."}], "meta": {"exam": "B", "qnum": 59, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We see brief outages whenever an OSPF link or router fails because the backup path is not used until OSPF reconverges. What should we deploy to keep traffic flowing during that OSPF recalculation?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Aggressive OSPF timers shorten detection and convergence delays but still rely on OSPF recalculation and can destabilize the network.\nC - Incremental SPF only reduces the scope of SPF recomputation after a topology change; it does not preinstall a backup path for immediate local repair.\nD - BFD accelerates failure detection so OSPF starts converging sooner, but traffic still waits for SPF and routing-table update without FRR."}], "meta": {"exam": "B", "qnum": 59, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need more access ports on one floor and want to reuse our existing Catalyst access switch. Uplink bandwidth is fine, but the distribution switches have no free ports for another uplink. What design approach should we use?"}, {"role": "assistant", "content": "Use Cisco StackWise with stack-capable Catalyst access switches. StackWise makes the switches act as one logical access switch, so added stack members provide extra access ports while the stack reuses the existing uplink to distribution. Because no new distribution ports are required and uplink capacity is not the constraint, stacking is the correct fit."}], "meta": {"exam": "B", "qnum": 66, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We need more access ports on one floor and want to reuse our existing Catalyst access switch. Uplink bandwidth is fine, but the distribution switches have no free ports for another uplink. What design approach should we use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - VDC virtualizes a single physical switch into multiple logical devices and does not add physical access ports.\nB - VSS combines distribution/core chassis into one logical switch and is not an access-port expansion solution.\nC - EtherChannel bundles existing links for bandwidth/redundancy and would still require additional ports or uplinks."}], "meta": {"exam": "B", "qnum": 66, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-WAN deployment, which routing information does OMP distribute so edge routers can forward overlay traffic without depending on the physical transport link IP addresses?"}, {"role": "assistant", "content": "OMP distributes TLOC routes. A TLOC is the logical transport locator, expressed as system-IP, color, and encapsulation, and it is used as the overlay next hop. This lets routers"}], "meta": {"exam": "B", "qnum": 77, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a multicast network with redundant paths, why does a router drop a PIM multicast packet when it arrives on an interface that is not the unicast route toward the source?"}, {"role": "assistant", "content": "That drop is the RPF check, which enforces loop-free multicast forwarding by accepting traffic only from the expected upstream direction. The router compares the multicast packet’s source address against the unicast routing table and discards the packet if the ingress interface is not the RPF interface toward that source. This prevents loops and duplicate packets while allowing PIM to build correct source-based distribution trees."}], "meta": {"exam": "B", "qnum": 88, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a multicast network with redundant paths, why does a router drop a PIM multicast packet when it arrives on an interface that is not the unicast route toward the source?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - RPF does not notify upstream routers of multicast traffic; PIM joins, registers, or other signaling perform that role.\nB - RPF does not send PIM prune messages toward sources; prune is a PIM mechanism used to remove unwanted branches.\nC - RPF does not eliminate overlapping multicast addresses; multicast address assignment or SSM range configuration handles addressing."}], "meta": {"exam": "B", "qnum": 88, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are designing a PIM-SM domain and need a vendor-neutral way for routers to automatically learn the RP set without manually configuring the same RP address on every device. Which RP deployment mechanism should we use?"}, {"role": "assistant", "content": "Use PIM Bootstrap Router (BSR). BSR is standards-based and dynamically distributes the RP-set through bootstrap messages, allowing all routers to consistently elect the RP for each group without static RP configuration."}], "meta": {"exam": "B", "qnum": 96, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are designing a PIM-SM domain and need a vendor-neutral way for routers to automatically learn the RP set without manually configuring the same RP address on every device. Which RP deployment mechanism should we use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Anycast-RP provides RP redundancy and load sharing, but it is not itself a dynamic RP discovery mechanism.\nC - Auto-RP supports dynamic RP discovery, but it is Cisco proprietary rather than standards-based.\nD - Static RP requires manual RP configuration on each router and does not support dynamic discovery."}], "meta": {"exam": "B", "qnum": 96, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "When choosing a YANG model to configure the same feature across a multivendor network, how do IETF, OpenConfig, and Cisco native models compare in practical coverage?"}, {"role": "assistant", "content": "Use OpenConfig when you need vendor-neutral, broadly comprehensive coverage; use Cisco native when you need Cisco-specific depth. OpenConfig models are generally more comprehensive than IETF models because they were built by operators to model real multivendor operational needs, while IETF models are standard but often more generic and limited. Cisco native models can be very complete for Cisco devices, but they are less portable and not the correct comparison for broader model comprehensiveness."}], "meta": {"exam": "B", "qnum": 104, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: When choosing a YANG model to configure the same feature across a multivendor network, how do IETF, OpenConfig, and Cisco native models compare in practical coverage?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Cisco native models are usually more comprehensive than OpenConfig for Cisco-specific features, not less comprehensive.\nC - Cisco native models are vendor-specific and typically expose more Cisco CLI-level detail than generic IETF models, not less.\nD - IETF models are standards-based but generally less comprehensive than OpenConfig for multivendor feature coverage."}], "meta": {"exam": "B", "qnum": 104, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have teams in multiple branches that need to communicate with each other and reach enterprise applications in our data center and in the cloud. Guests at those branches must get internet-only access, and our internet gateway is in the data center. What WAN design should I use to keep guest traffic isolated while still supporting corporate access?"}, {"role": "assistant", "content": "Use an MPLS Layer 3 VPN with one corporate VRF and one guest VRF. The corporate VRF carries branch, data center, and cloud routes using MP-BGP/route targets; the guest VRF is isolated and sends guest traffic back to the data center gateway, where a default route provides internet-only access. This gives the required segmentation without needing a separate VRF per branch."}], "meta": {"exam": "B", "qnum": 106, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We have teams in multiple branches that need to communicate with each other and reach enterprise applications in our data center and in the cloud. Guests at those branches must get internet-only access, and our internet gateway is in the data center. What WAN design should I use to keep guest traffic isolated while still supporting corporate access?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Using a different service provider for guests adds unnecessary cost and complexity and does not integrate cleanly with the centralized data center internet gateway.\nB - A data center firewall filtering guest traffic is useful but by itself does not provide the WAN segmentation and guest backhaul path needed from the branches.\nD - A separate VRF for each branch is operationally heavier than required and does not specifically solve the guest isolation and internet-only requirement."}], "meta": {"exam": "B", "qnum": 106, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are comparing a cloud-hosted SD-WAN controller design with on-premises SD-WAN controller appliances for a rapidly growing retail network. What is the main benefit of the cloud-based SD-W"}, {"role": "assistant", "content": "Cloud-based SD-WAN places the controller/orchestration layer in provider cloud infrastructure, so control-plane capacity, policy services, and management functions can be consumed as elastic resources. With a centralized control plane and distributed data plane, new WAN edges, branches, or VPN overlays can be onboarded through APIs and templates without waiting for on-premises controller hardware. This gives the deployment instant scale: capacity can be expanded or contracted rapidly as sites, policies, or tenants are added. Security, compliance, and availability are still design responsibilities and are not automatically guaranteed."}], "meta": {"exam": "B", "qnum": 113, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I'm sizing Cisco SD-WAN headend routers and need an appliance that can handle 20 Gbps of encrypted throughput—which vEdge model should I choose?"}, {"role": "assistant", "content": "Choose the Cisco vEdge 5000. It is the high-end vEdge platform rated for up to 20 Gbps of encrypted throughput, making it appropriate for data center or large headend aggregation where high-capacity IPsec processing is required."}], "meta": {"exam": "B", "qnum": 116, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I'm sizing Cisco SD-WAN headend routers and need an appliance that can handle 20 Gbps of encrypted throughput—which vEdge model should I choose?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - The Cisco vEdge 2000 is a midrange appliance rated for about 2 Gbps of encrypted throughput, not 20 Gbps.\nB - The Cisco vEdge 100 is a small branch appliance rated for about 100 Mbps of encrypted throughput.\nD - The Cisco vEdge 1000 is rated for roughly 1 Gbps of encrypted throughput, well below the 20 Gbps requirement."}], "meta": {"exam": "B", "qnum": 116, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our branch vEdges are behind NAT and do not yet know the vManage or vSmart addresses—which Cisco SD-WAN component should they contact first to bootstrap controller discovery and handle NAT traversal?"}, {"role": "assistant", "content": "Use the vBond orchestrator as the initial rendezvous point. vEdges initiate an outbound connection to vBond, which authenticates them and returns the vManage/vSmart information needed for controller discovery. Because vBond is publicly reach"}], "meta": {"exam": "B", "qnum": 121, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We’re planning a campus fabric with Cisco DNA Center and need to separate user groups, apply policy by identity, and create virtual networks over the existing wired and wireless campus. What does Cisco SD-Access actually provide in that design?"}, {"role": "assistant", "content": "The two correct statements are A and D. SD-Access delivers software-defined segmentation using user identity and group membership (via SGTs enforced by ISE), and it builds programmable VXLAN overlays that virtualize the campus network. The other options describe GRE tunneling to a mobility controller, an encryption engine, or generic tool coupling, none of which define SD-Access."}], "meta": {"exam": "B", "qnum": 126, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass_regenerated"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "During the discovery phase of a Cisco enterprise network design engagement, what should the solutions engineer focus on before moving into architecture and solution mapping?"}, {"role": "assistant", "content": "Focus on gathering information about the customer’s current network environment and establishing credibility with the customer. Discovery is about understanding the current state, requirements, constraints, and business drivers while building trust; architecture development, Cisco capability mapping, and lifecycle-model discussions come later once the requirements are understood."}], "meta": {"exam": "B", "qnum": 127, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: During the discovery phase of a Cisco enterprise network design engagement, what should the solutions engineer focus on before moving into architecture and solution mapping?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Developing a reference architecture is a design/planning activity that occurs after discovery requirements are known.\nC - Mapping Cisco innovation to customer needs is solution positioning or design work, not initial discovery.\nD - PPDIOO is a lifecycle methodology that can guide the engagement, but merely referencing it is not a discovery activity."}], "meta": {"exam": "B", "qnum": 127, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our design review asks which three DNA Assurance capabilities are unique differentiators versus competing assurance platforms; what should I cite?"}, {"role": "assistant", "content": "Cite Network Time Travel, Apple Insights, and proactive guided remediation. These are the Cisco DNA Assurance differentiators because they respectively provide historical replay of network conditions from telemetry, deep Apple client wireless analytics, and AI/ML-based issue correlation with guided remediation workflows. The other options are general transport, deployment, or virtualization features that competitors can also support."}], "meta": {"exam": "B", "qnum": 128, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Our design review asks which three DNA Assurance capabilities are unique differentiators versus competing assurance platforms; what should I cite?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Support for Overlay Virtual Transport is a general fabric/overlay capability, not a DNA Assurance-only differentiator.\nE - On-premise and cloud-based analytics are delivery models available from multiple assurance vendors, so they are not unique to DNA Assurance.\nF - VXLAN support is a widely implemented data-plane encapsulation and not a differentiator specific to DNA Assurance."}], "meta": {"exam": "B", "qnum": 128, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are comparing SNMP polling with model-driven telemetry for high-frequency interface counters and operational state. What is a practical advantage of using model-driven telemetry in this monitoring design?"}, {"role": "assistant", "content": "Use model-driven telemetry with a YANG model and a supported encoding such as JSON or protobuf for efficient streaming. It pushes structured data on a subscription, so it avoids interrupt-driven pull polling, does not rely on parsing CLI show output, and is not limited to legacy MIB structures. JSON encoding also improves compatibility with common monitoring and automation tools."}], "meta": {"exam": "C", "qnum": 6, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are comparing SNMP polling with model-driven telemetry for high-frequency interface counters and operational state. What is a practical advantage of using model-driven telemetry in this monitoring design?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Model-driven telemetry is push-based and subscription-driven, not interrupt-driven pull polling.\nB - Model-driven telemetry uses YANG models for structured data, not the MIB models associated with SNMP.\nD - Model-driven telemetry streams structured data directly; it does not obtain data by parsing CLI output from show commands."}], "meta": {"exam": "C", "qnum": 6, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are designing management access for a large data center. We need to separate management by device type, reduce DoS risk, and ensure that a compromised management-plane device cannot reach the production network. What management-access design should we choose?"}, {"role": "assistant", "content": "Use a dedicated out-of-band Ethernet management network. It"}], "meta": {"exam": "C", "qnum": 14, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our remote sites connect to headquarters over microwave links. Most sites have no physical WAN available, the budget and implementation time are limited, the backup link only needs low bandwidth, and users can tolerate up to two hours of WAN outage. What backup WAN link type should I recommend?"}, {"role": "assistant", "content": "Recommend LTE as the backup WAN link. LTE uses existing cellular carrier coverage, supports low-bandwidth IP/VPN failover, and can be deployed quickly with an LTE router or modem without requiring new physical WAN construction. It also meets the outage tolerance because failover can occur far faster than two hours, and it is generally more practical and cost-effective than the other listed wireless options."}], "meta": {"exam": "C", "qnum": 16, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Our remote sites connect to headquarters over microwave links. Most sites have no physical WAN available, the budget and implementation time are limited, the backup link only needs low bandwidth, and users can tolerate up to two hours of WAN outage. What backup WAN link type should I recommend?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - 802.15.1 Bluetooth is a short-range personal-area technology, not a WAN backup solution for remote sites.\nC - 802.16 WiMAX is a legacy broadband wireless technology with limited current carrier availability and deployment support.\nD - A laser link requires clear line of sight, short distances, and precise alignment, making it unsuitable for general remote-site WAN backup."}], "meta": {"exam": "C", "qnum": 16, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are considering moving a business-critical application to a SaaS provider. What is the main design limitation we should expect compared with keeping it on-premises or using IaaS?"}, {"role": "assistant", "content": "Expect reduced control over the application and its underlying infrastructure. In SaaS, the provider manages the full stack, so you gain lower upfront cost and operational simplicity but give up direct control over upgrades, patching, hosting details, scaling behavior, and much of the security implementation. Validate SLAs, data export, API integration, identity, compliance, and exit strategy before committing."}], "meta": {"exam": "C", "qnum": 30, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We are considering moving a business-critical application to a SaaS provider. What is the main design limitation we should expect compared with keeping it on-premises or using IaaS?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - SaaS generally shifts spend to subscription/opex and often lowers initial capital costs, not raises them.\nB - SaaS is normally accessed through a browser or API, so it does not require upgrading each endpoint to meet server-side performance needs.\nD - Integration can add project effort, but higher application and data integration complexity is not the fundamental SaaS control limitation and varies by provider/API maturity."}], "meta": {"exam": "C", "qnum": 30, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need a guaranteed, low-latency, drop-sensitive manufacturing application to work between sites in several countries through an ISP, and the application sends large data chunks. What QoS approach should we use on the ISP nodes so the provider gives it the required treatment without keeping per-flow state everywhere?"}, {"role": "assistant", "content": "Use a domain-based QoS strategy with PHBs, essentially DiffServ with DSCP marking and per-hop behaviors such as EF for"}], "meta": {"exam": "C", "qnum": 32, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access design, which plane should I use to automate fabric device onboarding and configuration?"}, {"role": "assistant", "content": "Use the fabric management plane, typically implemented by Cisco DNA Center, for automated device deployment and configuration. It provides PnP onboarding, configuration templates, fabric provisioning, and assurance workflows. LISP EID-to-RLOC mapping belongs to the control plane, while IS-IS underlay routing and VXLAN forwarding belong to the underlay/data planes."}], "meta": {"exam": "C", "qnum": 39, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco SD-Access design, which plane should I use to automate fabric device onboarding and configuration?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - LISP-based endpoint identifiers are part of the SD-Access control plane, not the management plane.\nC - EID-to-RLOC mapping is handled by the LISP control plane, not by a BGP-based management function.\nD - An IS-IS underlay is forwarding infrastructure that may be automated by the management plane, not the management plane itself."}], "meta": {"exam": "C", "qnum": 39, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access fabric, which control-plane protocol is used to map endpoint identities to fabric edge node locators so edge devices can resolve remote destinations?"}, {"role": "assistant", "content": "Use LISP. SD-Access relies on LISP for the EID-to-RLOC mapping control plane: fabric edges register EIDs with Map-Servers, and Map-Resolvers return the RLOC of the destination edge node. VXLAN then carries the data plane, but it does not perform the EID-to-RLOC resolution."}], "meta": {"exam": "C", "qnum": 42, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a Cisco SD-Access fabric, which control-plane protocol is used to map endpoint identities to fabric edge node locators so edge devices can resolve remote destinations?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - VXLAN is the SD-Access data-plane encapsulation/overlay transport, not the EID-to-RLOC control-plane mapping protocol.\nC - GBAC is a policy/segmentation mechanism in SD-Access, not the protocol that resolves EID-to-RLOC mappings.\nD - CEF is a data-plane forwarding mechanism that builds FIB adjacency information, not the SD-Access control-plane mapping protocol."}], "meta": {"exam": "C", "qnum": 42, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have an existing IPv4 network, and all our routers and switches already support IPv6. We want to migrate to IPv6 without buying new equipment, keep management overhead low, preserve IPv6 multicast, and let applications cut over using DNS. What migration approach should we use?"}, {"role": "assistant", "content": "Use a dual-stack model. Run IPv4 and IPv6 simultaneously on the existing infrastructure, enable IPv6 natively on interfaces and routing protocols, and use DNS AAAA records to let applications migrate independently. This avoids tunnel complexity, preserves native IPv6 multicast, and keeps operational costs low because no extra equipment or overlay management is needed."}], "meta": {"exam": "C", "qnum": 65, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: We have an existing IPv4 network, and all our routers and switches already support IPv6. We want to migrate to IPv6 without buying new equipment, keep management overhead low, preserve IPv6 multicast, and let applications cut over using DNS. What migration approach should we use?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Hybrid ISATAP tunneling relies on encapsulation and does not natively support IPv6 multicast while adding management complexity.\nB - Hybrid manual tunneling requires manually maintained tunnels, increasing operational cost and limiting scalability and multicast support.\nD - Service block model is not an IPv6 transition strategy for dual-stack application migration and does not meet the DNS-driven migration or multicast requirements."}], "meta": {"exam": "C", "qnum": 65, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are planning our ISE rollout and want to prioritize by implementation effort—which ISE use cases should we treat as the most complex and resource-intensive to design and deploy?"}, {"role": "assistant", "content": "Treat software-defined segmentation and software-defined access as the highest-complexity ISE use cases. Software-defined segmentation requires TrustSec SGT/SGACL design, enforcement consistency, and often SXP or pxGrid integration, while software-defined access requires ISE to tightly integrate with SD-Access fabric, DNA Center, overlay protocols, and fabric enforcement points. Both need end-to-end policy design, platform support validation, and coordinated change control across identity, routing/switching, wireless"}], "meta": {"exam": "C", "qnum": 90, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What is the defining characteristic of enterprise networking at this point in its history, and how should that shape my design approach?"}, {"role": "assistant", "content": "Treat the current era as one of rapid, continuous technology change, and design for adaptability rather than for a"}], "meta": {"exam": "C", "qnum": 93, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our network strategy needs to align with the current digital business era instead of the old pre-digital model—what three architectural focuses should I prioritize?"}, {"role": "assistant", "content": "Prioritize IoT scale, automation, and virtualized services. These are the key digital-era design drivers: IoT scale for massive endpoint growth and segmentation, automation for controller/API-driven intent and policy consistency, and virtualized services for elastic, cloud-ready, service-centric network functions. The older human-scale, basic connectivity, and centralized enterprise/web application model does not address these requirements."}], "meta": {"exam": "C", "qnum": 102, "topic": "", "has_exhibit": false, "variant": "quiz", "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Our network strategy needs to align with the current digital business era instead of the old pre-digital model—what three architectural focuses should I prioritize?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "B - Human scale describes the earlier pre-digital era, where networks supported a comparatively limited number of"}], "meta": {"exam": "C", "qnum": 102, "topic": "", "has_exhibit": false, "variant": "distractors"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we optimize the EIGRP convergence time in this hub-and-spoke network?"}, {"role": "assistant", "content": "In this hub-and-spoke EIGRP network, the spokes (R10, R20, R30) are connected through an mGRE cloud, which acts as a central hub. When a link fails, the EIGRP process on the spokes must recalculate routes. To minimize this recalculation time, we should simplify the routing logic on the spokes. By enabling stub routing on the spokes, we instruct them to only advertise their directly connected networks and ignore any routes learned from other peers. This reduces the size of their routing table and the complexity of the convergence calculation, leading to faster convergence times compared to the other options."}], "meta": {"exam": "A", "qnum": 37, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we optimize the EIGRP convergence time in this hub-and-spoke network?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Enabling subsecond timers can speed up convergence but is less effective than stub routing in this scenario. B - Increasing the hold time value would delay the detection of a failed neighbor, thus increasing convergence time. C - Increasing the dead timer value would also delay the detection of a failed neighbor, slowing down convergence."}], "meta": {"exam": "A", "qnum": 37, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can the client's internal network ensure all devices can reach the Internet through ISP1?"}, {"role": "assistant", "content": "To achieve this, the edge routers connecting to ISP1 (Edge Router A in this case) must inform the rest of the client's network about how to get to the Internet. The simplest and most effective method is to configure these edge routers to advertise a default route (0.0.0.0/0) into the client's internal routing domain. This allows every downstream router in the client's network to learn that any destination outside their own network should be forwarded to the edge router. When a device on the client network wants to access the Internet, its traffic is sent to the nearest downstream router, which then forwards it to the edge router. The edge router then sends the traffic to ISP1, completing the connection. This approach is scalable and does not require the client to maintain complex routing tables for the entire Internet."}], "meta": {"exam": "A", "qnum": 99, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can the client's internal network ensure all devices can reach the Internet through ISP1?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Running eBGP sessions in different VRFs would isolate the routing tables for each ISP, but it doesn't directly enable Internet connectivity from the client's internal network.\nC - Applying AS-path prepend is a technique to influence inbound traffic from ISP2, not to enable outbound traffic to the Internet via ISP1.\nD - Route filtering ensures the client only advertises its own routes, which is important for security and policy, but it does not create the necessary path for the client's network to reach the Internet."}], "meta": {"exam": "A", "qnum": 99, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we ensure connectivity between the 10.1.1.0/24 and 172.16.1.0/24 networks if the direct link between routers C and E fails?"}, {"role": "assistant", "content": "The current design has a single point of failure for inter-area connectivity within Area 10: the link between C and E. When this link fails, the only remaining path from the 10.1.1.0/24 network (via A-B) to the 172.16.1.0/24 network (via E) is through the backbone area (Area 0). This path (A->C->D->F->E) would be suboptimal because it requires traffic to traverse the backbone unnecessarily. By moving the C-D link into Area 10, a redundant loop-free path is created entirely within Area 10. This allows the shortest path algorithm to calculate an optimal route that avoids the failed C-E link, such as A->B->D->C->E or A->B->D->F->E, depending on cost metrics. This provides resilience and maintains optimal intra-area routing."}], "meta": {"exam": "A", "qnum": 105, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we ensure connectivity between the 10.1.1.0/24 and 172.16.1.0/24 networks if the direct link between routers C and E fails?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Moving the C-D link into Area 10 creates a redundant path within Area 10, ensuring optimal routing even after the C-E link fails.\nB - Creating a virtual link between E and F would not solve the problem; it's used for connecting non-backbone areas to the backbone, not for creating redundancy within a single area.\nC - Creating a tunnel between E and F would add complexity and overhead without providing the same level of integration and optimization as a native OSPF link.\nD - Making Area 10 a NSSA does not address the physical link failure; it changes the type of external routes allowed, not the internal topology."}], "meta": {"exam": "A", "qnum": 105, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I configure Area 1 to receive EIGRP routes while blocking routes from the RIP domain?"}, {"role": "assistant", "content": "Based on the exhibit, Area 1 needs to be configured as a Not-So-Stubby Area (NSSA). This is because an NSSA allows the injection of external routes (such as EIGRP routes) into the area through the use of Type 7 LSAs, which are converted by the ABR into Type 5 LSAs for distribution in the rest of the OSPF domain. However, an NSSA blocks the reception of Type 5 LSAs from other areas, meaning any routes originated in the RIP domain (which would typically be advertised as external routes) will not be propagated into Area 1. This configuration satisfies the requirement to include EIGRP routes but exclude RIP-originated routes."}], "meta": {"exam": "A", "qnum": 107, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I configure Area 1 to receive EIGRP routes while blocking routes from the RIP domain?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Making area 1 a standard OSPF area would allow all external routes, including those from RIP.\nB - Making area 1 a stub area would prevent all external routes from being received, including EIGRP.\nC - Making the area 1 routers part of area 0 would change their area membership and disrupt the current network design."}], "meta": {"exam": "A", "qnum": 107, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we make the HSRP failover happen automatically when the primary WAN link goes down?"}, {"role": "assistant", "content": "In this scenario, the engineer needs to ensure that the HSRP group on R1 detects the failure of the WAN 1 link. The most effective way to do this is to use a method that actively monitors the health of the WAN connection. Implementing Enhanced Object Tracking on R1 is a key step because it allows the HSRP process to track the status of a specific object, such as the WAN interface or a static route to the internet. When the tracked object becomes unavailable, the priority of R1 in the HSRP group is reduced, which causes R2 to become the new active router. Additionally, implementing IP SLA on R1 provides a proactive monitoring mechanism. By configuring an IP SLA operation to send periodic probes to a known destination on the WAN, the router can detect packet loss or high latency. If the SLA test fails, it can be configured to decrement the HSRP priority, triggering the failover to R2. Therefore, combining Enhanced Object Tracking with IP SLA ensures both immediate detection and a reliable failover mechanism."}], "meta": {"exam": "A", "qnum": 116, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we make the HSRP failover happen automatically when the primary WAN link goes down?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Enhanced Object Tracking is a valid method to detect the WAN failure and trigger a failover. B - A floating static route is not a direct method for HSRP to detect a WAN failure; it only influences routing decisions. C - IP SLA is a valid method for active monitoring and triggering failover. D - Policy-Based Routing (PBR) is used for traffic steering, not for detecting link failures. E - IP source routing is a deprecated feature and not relevant to failover mechanisms."}], "meta": {"exam": "A", "qnum": 116, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we prevent a Layer 2 forwarding loop when a unidirectional fiber link between two switches fails?"}, {"role": "assistant", "content": "The scenario describes a unidirectional link failure on a fiber connection between SW2 and SW3. In a spanning tree topology, if a switch loses its connection to a root bridge but still receives BPDUs from another switch, it may incorrectly assume it has a valid path and continue forwarding traffic, creating a loop. To prevent this, the architect should enable Loop Guard on the switch that is in a designated role on the failing link. By placing Loop Guard on SW2, the switch will detect the absence of BPDUs from its neighbor and put the port into a loop-inconsistent state, blocking forwarding and thus preventing the formation of a loop."}], "meta": {"exam": "A", "qnum": 118, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we prevent a Layer 2 forwarding loop when a unidirectional fiber link between two switches fails?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Utilizing an 802.1X filter is used for port security and authentication, not for preventing loops caused by link failures. B - Utilize loop guard on SW2. C - BPDU guard is used to protect against unauthorized devices sending BPDUs, not to handle unidirectional link failures. D - Root guard prevents a switch from becoming the root bridge, which is unrelated to the issue of unidirectional link failure causing loops."}], "meta": {"exam": "A", "qnum": 118, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Why does traffic drop when the primary HSRP switch recovers after a failure?"}, {"role": "assistant", "content": "When the primary HSRP switch comes back online, HSRP preemption immediately causes it to take over the virtual IP address. This triggers an immediate update of the MAC address tables on all downstream switches and end devices, leading to a brief period where frames are dropped because the new MAC-to-port mappings haven't been learned yet. The solution is to use the preempt delay feature on the primary HSRP device, which adds a configurable delay before it reclaims its priority. This gives the network time to stabilize and ensures a smoother transition, preventing the disruptive MAC address flapping and traffic drops."}], "meta": {"exam": "A", "qnum": 119, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Why does traffic drop when the primary HSRP switch recovers after a failure?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Increasing the hello timers only affects how frequently HSRP messages are sent, not the timing of the failover process itself. C - Using preempt delay on the backup device would delay its takeover, which is not relevant to the primary's recovery issue. D - Configuring a higher mac-refresh interval affects how often the switch refreshes its own MAC table, but it doesn't address the core problem of MAC flapping during a primary switch recovery."}], "meta": {"exam": "A", "qnum": 119, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we prioritize new network management traffic when all existing QoS classes are full?"}, {"role": "assistant", "content": "To prioritize the new network management traffic, we need to integrate it into the existing QoS policy without adding a new class. We should mark this traffic with a DSCP value suitable for network management, such as CS2. Then, we assign it to an existing class that can handle this type of traffic. The ROUTING class is a logical choice for network management, as it often handles control plane traffic. The next critical step is to baseline the current queue sizes for the ROUTING class to determine if there is enough bandwidth available to accommodate the additional traffic without causing congestion. If so, the configuration can proceed; if not, bandwidth may need to be reallocated from other less critical classes."}], "meta": {"exam": "A", "qnum": 120, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we prioritize new network management traffic when all existing QoS classes are full?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Marking the traffic to DSCP CS5 and assigning it to the SIGNALLING class would require creating a new class or overloading an existing one, which contradicts the requirement to integrate into the existing policy. B - Using DSCP CS4 for the SIGNALLING class is incorrect because CS4 is typically used for voice traffic, not network management, and assigning it to SIGNALLING could lead to misprioritization. C - Assigning network management traffic to the ROUTING class using DSCP CS6 is wrong because CS6 is reserved for network control and is too high a priority for typical management traffic, potentially leading to resource contention."}], "meta": {"exam": "A", "qnum": 120, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I ensure that certain internal network prefixes at a remote branch are not advertised to the internet when using BGP with a service provider?"}, {"role": "assistant", "content": "To achieve this, you should use the BGP No-Export community. By attaching the No-Export community to the prefixes that should not be advertised to the internet, you instruct the BGP router to not propagate these routes beyond the local autonomous system. This effectively keeps the internal network details of the branch private and prevents them from being exposed to the wider internet through the service provider's network. This is the standard and most effective method for achieving this level of route control in BGP."}], "meta": {"exam": "A", "qnum": 123, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I ensure that certain internal network prefixes at a remote branch are not advertised to the internet when using BGP with a service provider?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Setting the BGP Internet community typically indicates that a prefix should be advertised to the internet, which is the opposite of the desired outcome. B - The NOPEER community is not a standard BGP community and does not exist in the BGP specification, making it an invalid option. C - Using the BGP No-Advertise community would prevent the prefixes from being advertised to any BGP peer, including the service provider, which would break connectivity rather than just hiding the prefixes from the internet."}], "meta": {"exam": "A", "qnum": 123, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I configure BGP to stop my AS from acting as a transit network for other ASes?"}, {"role": "assistant", "content": "To prevent your AS from becoming a transit AS, you must control which routes you advertise to your peers. The key is to use the BGP \"no-export\" community. When you receive routes from an upstream provider (like AS65533 or AS65530), you apply the \"no-export\" community to those routes before advertising them to your own customers or peers. This tells your neighbors that they cannot pass these routes on to other ASes. As a result, the routes never leave your AS, preventing AS64512 from being used as a path for traffic between other networks. This makes \"no-export\" the correct choice."}], "meta": {"exam": "B", "qnum": 3, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I configure BGP to stop my AS from acting as a transit network for other ASes?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - no-advertise would prevent the routes from being advertised at all, which would break connectivity. B - next-hop is a routing attribute, not a filtering mechanism to prevent transit. D - maximum-prefix limits the number of routes but doesn't control their origin or destination."}], "meta": {"exam": "B", "qnum": 3, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can an architect ensure that an EIGRP network remains stable and efficient when connecting to external networks via BGP?"}, {"role": "assistant", "content": "In this scenario, the architect should implement route summarization and stub routing. Route summarization is critical because it reduces the number of individual routes that need to be advertised and processed, conserving bandwidth, memory, and CPU resources across the network. This is particularly important given the multiple subnets within each AS. Stub routing is equally important as it configures edge routers to only accept default routes or specific summaries from their neighbors, preventing them from becoming intermediate routers for traffic they are not designed to handle. This eliminates the risk of suboptimal paths and significantly reduces the number of EIGRP queries initiated by the network, enhancing overall stability and scalability."}], "meta": {"exam": "B", "qnum": 4, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can an architect ensure that an EIGRP network remains stable and efficient when connecting to external networks via BGP?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Route summarization is effective but alone doesn't address the issue of unnecessary queries.\nB - Prefix lists are useful for filtering traffic but do not directly conserve resources or prevent queries.\nC - Distribute lists filter routing updates but can lead to inconsistent routing information and don't fully address the query problem.\nE - Static redistribution is not scalable and requires manual configuration for every route, increasing administrative overhead and potential for errors."}], "meta": {"exam": "B", "qnum": 4, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we configure BGP to use two parallel links between two routers for load balancing?"}, {"role": "assistant", "content": "To achieve load balancing over two links between R1 and R6, we need to ensure the BGP process on each router can see and utilize both paths. The key is that BGP, by default, only installs one path from a peer into the routing table. The `maximum-paths` command is used to change this behavior. By setting `maximum-paths 2` on both R1 and R6, the BGP process will be allowed to keep up to two best paths in its routing table. When these two paths have the same metric (which they would if the links are equal), BGP will then perform per-packet or per-flow load balancing across them. Therefore, the design must include the configuration of `maximum-paths`."}], "meta": {"exam": "B", "qnum": 5, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we configure BGP to use two parallel links between two routers for load balancing?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Using update-source with a Loopback interface ensures a stable BGP neighborship but does not enable load sharing. B - The next-hop-self attribute modifies the next-hop for routes sent to a peer, which is useful for iBGP but not for achieving load sharing between eBGP peers. C - Configuring eBGP TTL for multihop is necessary when BGP peers are not directly connected, but in this case, the diagram shows a direct connection, so this is not required."}], "meta": {"exam": "B", "qnum": 5, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I prevent route recomputation during a stateful switchover on a Catalyst switch with dual supervisors when the upstream router doesn't support graceful restart?"}, {"role": "assistant", "content": "The key issue is that a stateful switchover causes route recomputation because the new supervisor lacks the routing state information. Since the upstream router doesn't understand graceful restart, we cannot use NSF, which depends on neighbor signaling. Instead, we need a feature that preserves the routing state across the supervisor failover. NSR (Non-Stop Routing) is designed exactly for this purpose; it allows the backup supervisor to maintain the routing table and forwarding information, so the network continues to operate without needing to recompute routes. Therefore, enabling NSR on the switch is the appropriate action."}], "meta": {"exam": "B", "qnum": 7, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I prevent route recomputation during a stateful switchover on a Catalyst switch with dual supervisors when the upstream router doesn't support graceful restart?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Enabling IS-IS remote LFA FRR provides fast rerouting for link failures but does not address the stateful switchover issue. B - Enabling NSR on the switch ensures that the routing state is preserved during a supervisor failover, allowing for a seamless transition and preventing route recomputation. C - Enabling NSF on the switch requires support from neighboring routers to coordinate the switchover, which is not possible here since the upstream router does not understand graceful restart messaging. D - Configuring ISIS aggressive timers reduces convergence time but does not prevent the initial recomputation event during a switchover."}], "meta": {"exam": "B", "qnum": 7, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I ensure my IS-IS network remains stable during supervisor failover on a Catalyst switch when the upstream router doesn’t support graceful restart?"}, {"role": "assistant", "content": "Configure shorter SPF and PRC timers and implement a hierarchical IS-IS design with access routers as Level 1-only and aggregate routers as Level 1/Level 2. Shorter timers reduce the time it takes to recalculate routes after a change, while the hierarchical design isolates topology changes within areas, preventing them from propagating unnecessarily and ensuring faster local convergence."}], "meta": {"exam": "B", "qnum": 8, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass_regenerated"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I ensure my IS-IS network remains stable during supervisor failover on a Catalyst switch when the upstream router doesn’t support graceful restart?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Enabling IS-IS remote LFA FRR is for fast reroute around link failures, not for maintaining IS-IS state during supervisor switchover.\nC - Enabling NSF on the switch addresses forwarding plane continuity, not routing protocol state preservation during supervisor failover.\nD - Configuring IS-IS aggressive timers reduces convergence time after topology changes but does not prevent route recomputation during supervisor switchover."}], "meta": {"exam": "B", "qnum": 8, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I design a network so that a failure in the access layer doesn't cause instability in the core, and ensure the network recovers quickly?"}, {"role": "assistant", "content": "In this network topology, the access layer routers (AGG-1 and AGG-2) connect to the core (R4-R6). To prevent a failure in the access network (e.g., a link down or router issue) from impacting the core's stability and to achieve fast convergence, the engineer should implement Fast Reroute (FRR). FRR allows the router to immediately switch traffic to a pre-determined backup path when a primary link fails, bypassing the normal convergence process of the routing protocol. By enabling FRR on the access edge routers (A and C), the network can recover from any single link failure in the access or core very quickly, ensuring minimal downtime and protecting the core from unnecessary instability."}], "meta": {"exam": "B", "qnum": 9, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I design a network so that a failure in the access layer doesn't cause instability in the core, and ensure the network recovers quickly?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Adding an aggregation layer would increase complexity but doesn't inherently provide faster convergence or protection from access failures. B - Graceful restart helps during software reloads but doesn't provide immediate failover for link failures. D - Summarization reduces routing table size but does not improve the speed of convergence after a failure."}], "meta": {"exam": "B", "qnum": 9, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I ensure that traffic from the 10.10.10.0/24 network uses the direct link between R1 and R2 when heading to the 10.10.20.0/24 network?"}, {"role": "assistant", "content": "Configure R1 to use a high local-preference for ISP-1 routes and no AS-path prepending, while configuring R2 to use a low local-preference and a long AS-path prepend for ISP-2 routes. This prioritizes ISP-1 by making it the most attractive path, ensuring it's used exclusively until it fails."}], "meta": {"exam": "B", "qnum": 12, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass_regenerated"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I ensure that traffic from the 10.10.10.0/24 network uses the direct link between R1 and R2 when heading to the 10.10.20.0/24 network?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Configuring the OSPF cost alone cannot override the area boundary rules; the link must be in the correct area.\nB - Administrative Distance is a global setting and does not affect how OSPF calculates paths within an area.\nC - Placing the link into a new area and creating a new link is unnecessary and would complicate the design without solving the core issue."}], "meta": {"exam": "B", "qnum": 12, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a three-tier network with Core, Aggregation, and Access layers, where should route summarization be implemented to optimize routing efficiency and reduce overhead, especially when Access layer devices are configured as EIGRP stubs?"}, {"role": "assistant", "content": "The exhibit shows a hierarchical network with Core, Aggregation, and Access layers. The Access layer switches are marked as EIGRP stubs, meaning they do not advertise their routes back to the Aggregation layer and only receive default or summarized routes. Therefore, summarization should occur at the Aggregation layer when sending routes toward the Core — to consolidate routes from multiple Access segments and prevent route explosion in the Core. Additionally, summarization should occur at the Aggregation layer when sending routes toward the Access layer — to send efficient, summarized routing information to the stub devices. Since the Access devices are stubs, they won’t advertise detailed routes back, so summarization from Access to Aggregation is unnecessary. Thus, the correct locations for route summarization are from Aggregation toward Core and from Aggregation toward Access."}], "meta": {"exam": "B", "qnum": 14, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: In a three-tier network with Core, Aggregation, and Access layers, where should route summarization be implemented to optimize routing efficiency and reduce overhead, especially when Access layer devices are configured as EIGRP stubs?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Summarization from core toward aggregation is unnecessary because the core is typically the most summarized layer; summarization from access toward aggregation is not needed since access devices are stubs. \nB - Summarization from core toward aggregation is not typical; summarization should occur from lower to higher layers, not the other way around. \nC - Summarization from aggregation toward access is correct, but summarization from access toward aggregation is incorrect because access devices are stubs and do not advertise routes upward."}], "meta": {"exam": "B", "qnum": 14, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we reduce the impact of a link failure when using EIGRP in this multi-layered network?"}, {"role": "assistant", "content": "In this three-tier network, EIGRP advertises the full routing table, which means a failure anywhere causes a significant topology change. To minimize disruption, we need to limit the scope of routing updates. By summarizing the access layer networks at the aggregation layer before advertising them to the core, we create a single, aggregated route for all access subnets. This ensures that if a link within an access or aggregation switch fails, the core routers don't need to process individual changes, thus speeding up convergence and reducing data loss."}], "meta": {"exam": "B", "qnum": 15, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we reduce the impact of a link failure when using EIGRP in this multi-layered network?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - BFD improves detection speed but doesn't address the root cause of excessive routing updates. B - Summarizing from access to aggregation would not reduce the overall routing table size seen by the core. C - Reducing hello intervals speeds convergence slightly but increases CPU load and does not scale well with large topologies."}], "meta": {"exam": "B", "qnum": 15, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What configuration should be applied to the switch ports connecting end-user devices to achieve faster network convergence?"}, {"role": "assistant", "content": "The relevant fact from the exhibit is that the network has an access layer where switches connect to end-user devices. To optimize STP convergence time, the port configuration must allow these access ports to skip the slow STP state transitions. The correct functionality is PortFast, which enables a switch port to move directly from the blocking state to the forwarding state when a device connects. This prevents the 30-second delay associated with the listening and learning states, ensuring users can communicate as soon as their device connects."}], "meta": {"exam": "B", "qnum": 16, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What configuration should be applied to the switch ports connecting end-user devices to achieve faster network convergence?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - UplinkFast is used on distribution switches to speed up convergence when a primary uplink fails, not on access ports. B - Root guard prevents a switch from becoming the root bridge, which is a security feature, not a convergence optimization. C - BPDU guard disables a port if it receives a BPDU, which protects against loops but does not speed up convergence."}], "meta": {"exam": "B", "qnum": 16, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I safely redistribute routes between the EIGRP network and the network behind R3 without creating routing loops?"}, {"role": "assistant", "content": "To safely connect the network behind R3 with the EIGRP network, you must implement route redistribution. The key challenge is preventing a loop where a route advertised by EIGRP is learned by R3, then redistributed back into EIGRP, creating a cycle. The most effective mechanism for this is using route tags. By assigning a unique tag to routes when they are redistributed into EIGRP, the EIGRP process on R3 can be configured to ignore any routes with that specific tag, thereby preventing them from being re-advertised back into the EIGRP domain and breaking the potential loop."}], "meta": {"exam": "B", "qnum": 39, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I safely redistribute routes between the EIGRP network and the network behind R3 without creating routing loops?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - The down bit is used in IS-IS to indicate a link failure, not for preventing routing loops during redistribution. B - Split-horizon is a technique within a single routing protocol to prevent sending updates back out the same interface, but it doesn't work across different protocols. D - Summarization reduces the size of routing tables but does not inherently prevent routing loops between different routing domains."}], "meta": {"exam": "B", "qnum": 39, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What configuration change should be made to the routers to prevent future outages caused by a link failure?"}, {"role": "assistant", "content": "The diagram shows a network where R1 and R2 are L1/L2 routers forming the backbone, but R3 is configured as an L1 router. This means R3 can only route within its local area and cannot forward traffic between different areas, leading to a potential break in connectivity if the direct link fails. Since the backbone requires all routers to be capable of inter-area communication, R3 must be changed from an L1 router to an L1/L2 router. This allows R3 to participate in the L2 backbone, enabling it to forward packets between areas and ensuring that the network remains connected even if a single link fails."}], "meta": {"exam": "B", "qnum": 49, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What configuration change should be made to the routers to prevent future outages caused by a link failure?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Making R3 an L1L2 router ensures it can forward traffic across areas and maintain network continuity. \nB - Making R31 an L1 router would further isolate it from the backbone and worsen the problem. \nC - Making Area 0 L2-only is not a valid configuration option because Area 0 is the backbone, and it must be L2-only by definition, but this doesn't address the specific issue with R3's role. \nD - Making R11 an L2 router does not solve the root cause, which is the misconfiguration of R3 as an L1 router in the backbone."}], "meta": {"exam": "B", "qnum": 49, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What configuration is required on the routers to ensure a Wake-on-LAN magic packet can reach the workstations from the Application Server?"}, {"role": "assistant", "content": "To ensure the WOL magic packet reaches the workstations, we need to analyze the path. The Application Server (192.168.10.11) is on a different subnet than the workstations. The packet will travel from the server through SW1, R1, R2, and then to SW2. The key point is that a directed broadcast (e.g., 192.168.20.255) needs to be forwarded by the router that is the last hop into the destination network. R2 is the router directly connected to the 192.168.20.0/24 network where the workstations reside. Enabling \"ip directed-broadcast\" on R2 allows it to process the directed broadcast packet as a regular broadcast within its own subnet, thus waking all the WOL-capable machines. R1 is not the last router to the destination, so enabling it would be ineffective."}], "meta": {"exam": "B", "qnum": 51, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What configuration is required on the routers to ensure a Wake-on-LAN magic packet can reach the workstations from the Application Server?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - IP directed-broadcasts on R1 would not reach the final destination network; R1 is not the last router to the target subnet. B - spanning-tree uplinkfast on SW1 is unrelated to broadcasting and is used for fast convergence of redundant links. C - spanning-tree uplinkfast on SW2 is also unrelated to the broadcast functionality needed for WOL."}], "meta": {"exam": "B", "qnum": 51, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What mechanism should be implemented on the ISP routers to achieve sub-second failover times?"}, {"role": "assistant", "content": "To achieve sub-second failover times, the network engineer should implement Bidirectional Forwarding Detection (BFD). BFD is a lightweight protocol that provides rapid detection of communication failures between two network devices by sending periodic hello packets. Its ability to detect failures in tens of milliseconds makes it the most effective solution for minimizing downtime to sub-second levels, which is critical for maintaining high availability in the network. Given that the failover time for ISP-2 is already significantly shorter, it is likely that BFD is already enabled on that path, while it is missing on the ISP-1 path."}], "meta": {"exam": "B", "qnum": 61, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What mechanism should be implemented on the ISP routers to achieve sub-second failover times?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Aggressive timers can reduce convergence time but typically cannot achieve sub-second speeds reliably.\nB - Next-hop address tracking improves routing stability but does not provide the same level of fast failure detection as BFD.\nC - Graceful-restart helps maintain forwarding during a control plane restart but does not speed up the initial detection of a link failure."}], "meta": {"exam": "B", "qnum": 61, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I ensure that the Headquarters network can still reach the 10.0.4.0/24 subnet at Site B if the direct link between routers B and D fails?"}, {"role": "assistant", "content": "To solve this, we must understand that the current EIGRP stub configuration on router D prevents it from advertising its directly connected networks, including 10.0.4.0/24, back to the headquarters. This creates a dependency on the single link between B and D. If that link fails, the route to 10.0.4.0/24 is lost. The solution is to use the `stub leak-map` command on router D. This command allows the architect to define a route map that specifies which routes (in this case, the 10.0.4.0/24 network) should be advertised back into the EIGRP domain as if they were internal routes. This ensures that the headquarters routers (A and B) learn about the 10.0.4.0/24 network and can find an alternate path to reach it, thereby maintaining connectivity during a link failure."}], "meta": {"exam": "B", "qnum": 64, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I ensure that the Headquarters network can still reach the 10.0.4.0/24 subnet at Site B if the direct link between routers B and D fails?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A. Stub connected - This option would advertise only directly connected routes, but it doesn't provide the mechanism to selectively leak the specific subnet needed.\nB. Stub redistributed - This would allow redistribution of routes from other protocols, which is not applicable here since the goal is to advertise a directly connected subnet.\nC. Stub receive-only - This configuration prevents the stub router from sending any routing updates, which would completely block the route to 10.0.4.0/24 from being advertised back, worsening the problem."}], "meta": {"exam": "B", "qnum": 64, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I configure OSPF to prefer the MPLS VPN backbone for connectivity between remote sites, while still allowing direct dark fiber links to be used as a failover path?"}, {"role": "assistant", "content": "Based on the exhibit, the network uses OSPF for routing between the remote sites and the MPLS backbone. To ensure the dark fiber is only used when the MPLS core is down, you must configure a sham link. A sham link is an OSPF virtual link that connects two parts of the same OSPF area through the MPLS backbone, allowing the router to advertise the direct dark fiber connection as a backup route. By setting the cost of the sham link higher than the MPLS path, OSPF will prefer the MPLS core normally, but switch to the dark fiber if the MPLS path fails. Therefore, the correct solution is a sham link."}], "meta": {"exam": "B", "qnum": 74, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I configure OSPF to prefer the MPLS VPN backbone for connectivity between remote sites, while still allowing direct dark fiber links to be used as a failover path?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Stub areas are used to reduce routing information in non-backbone areas and do not provide redundancy between branches. C - Virtual links are used to connect non-contiguous areas to the backbone and are not suitable for defining backup paths between branches. D - NSSA areas allow external routes to be imported but do not enable direct inter-branch connectivity or failover mechanisms."}], "meta": {"exam": "B", "qnum": 74, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we ensure the architecture supports both current monitoring needs and future route growth without overloading the network?"}, {"role": "assistant", "content": "The architecture must enable end-to-end visibility for L3VPN and L2VPN traffic, which is achieved by having the PE routers exchange VPN routes using the BGP VPNv4 address family. This ensures the NOC can monitor all customer routes. For future scalability, the network needs to handle thousands of new routes efficiently. Using BGP IPv4 unicast on the ABRs to connect different IGP domains prevents each domain from needing to learn every route from the others, reducing the routing table size and CPU load on the routers. This hybrid approach combines the benefits of MPLS VPNs for service delivery with a scalable inter-domain routing strategy."}], "meta": {"exam": "B", "qnum": 76, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we ensure the architecture supports both current monitoring needs and future route growth without overloading the network?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Establishing a full mesh IBGP peering would create an impractical number of connections as the network grows, leading to high management overhead and potential instability. B - Redistributing IGP routes into BGP is not suitable here because it would expose internal IGP details to the entire network, creating security risks and scalability issues. D - Filtering loopback addresses is not necessary and could disrupt essential functions like BGP session establishment or reachability."}], "meta": {"exam": "B", "qnum": 76, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I ensure that R4 does not receive any routes from Branch A?"}, {"role": "assistant", "content": "To prevent R4 from receiving routes from Branch A, we need to filter them at the router that advertises them to R4. In the diagram, R2 receives the 10.10.10.0/24 prefix from R5 (Branch A) via iBGP and then sends it to R4 via eBGP. Since R2 is the eBGP peer with R4, it is the correct place to apply outbound route filtering. By configuring a prefix list on R2 to deny the 10.10.10.0/24 network and applying ORF, R2 will stop advertising this prefix to R4, thus fulfilling the requirement."}], "meta": {"exam": "B", "qnum": 81, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I ensure that R4 does not receive any routes from Branch A?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - This option targets the wrong subnet and places the filter on R4, which is incorrect because R4 receives the route, it doesn't originate it. C - This option places the filter on R5, which is the source of the route, but the goal is to stop it from reaching R4, not to stop it from being advertised by R5. D - This option uses the wrong subnet and places the filter on R2, but it's the wrong prefix list, so it won't effectively block the required traffic."}], "meta": {"exam": "B", "qnum": 81, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we configure redistribution between EIGRP and RIPv1 to avoid creating routing loops in this topology?"}, {"role": "assistant", "content": "In this scenario, EIGRP and RIPv1 are exchanging routes across multiple points. The main risk is that a route learned by RIPv1 from EIGRP could be redistributed back into EIGRP, creating a loop. To mitigate this, we need to control the flow of routes at the point where they enter the EIGRP process. By applying a distribute-list inbound under the EIGRP process, we can filter out any routes learned from RIPv1 before they are accepted into EIGRP's routing table. This prevents these routes from being advertised back into the EIGRP domain, effectively breaking the potential loop. Therefore, the correct configuration is to use a distribute-list inbound under the EIGRP process to deny RIPv1 learned prefixes."}], "meta": {"exam": "B", "qnum": 83, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we configure redistribution between EIGRP and RIPv1 to avoid creating routing loops in this topology?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - This option correctly identifies the need to filter incoming RIPv1 routes from EIGRP to prevent loops. \nB - Outbound filtering in EIGRP would only affect routes being sent out, not those being received, so it wouldn't prevent RIPv1 routes from entering EIGRP. \nC - Outbound filtering in RIPv1 would only stop RIPv1 from sending EIGRP routes, but it doesn't address the reverse direction which causes the loop. \nD - Inbound filtering in RIPv1 would prevent EIGRP routes from entering RIPv1, but the primary threat is RIPv1 routes re-entering EIGRP, not the other way around."}], "meta": {"exam": "B", "qnum": 83, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Given the network topology where R1 and R2 are the only visible routers connecting two domains, how should a BGP solution be designed to ensure redundancy and avoid a single point of failure?"}, {"role": "assistant", "content": "Based on the provided information, we must assume the existence of additional routers R3, R4, and R5 not shown in the diagram. The requirement that the route reflector must have direct physical connections to the core routers (R3 and R4) means the route reflector must be either R3 or R4. To achieve full redundancy and eliminate a single point of failure, a dual-route-reflector architecture is required. This means both R3 and R4 must be configured as route reflectors. The clients (R1, R2, R5) must then be configured to peer with both R3 and R4. Therefore, the solution must include configuring R3 and R4 as route reflectors and ensuring all other routers (R1, R2, R5) are clients of both. This setup satisfies the requirements for redundancy and direct connectivity to the core."}], "meta": {"exam": "B", "qnum": 89, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Given the network topology where R1 and R2 are the only visible routers connecting two domains, how should a BGP solution be designed to ensure redundancy and avoid a single point of failure?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Configuring R1 as a client of R2 and R4 violates the requirement that the route reflector must have direct physical connections to the core routers; R1 is not a core router. B - This option correctly identifies R2 as a client and configures it to peer with R1 and R4, which can be part of a redundant design if R1 and R4 are the route reflectors. C - This option incorrectly places R3 as a client of R2 and R4, which contradicts the requirement that the route reflector must have direct connections to the core routers. D - This option suggests R4 as a client, which cannot be true since R4 must be a route reflector itself to meet the connectivity requirement. E - This option places R5 as a client of R3 and R4, which is a valid configuration for a client, but it does not address the critical requirement of having the route reflector (R3/R4) directly connected to the core routers."}], "meta": {"exam": "B", "qnum": 89, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What IPv6 migration technique should be used if the core transport infrastructure (DWDM) only supports Layer 2 and cannot be upgraded to handle IPv6?"}, {"role": "assistant", "content": "Given that the DWDM routers only support Layer 2 and cannot process IPv6, the engineers need a solution that allows IPv6 communication between routers while leveraging the existing IPv4-capable routers. ISATAP creates tunnels over an IPv4 network, allowing IPv6 traffic to traverse IPv4-only backbones, which fits perfectly here since the routers can handle both protocols. Therefore, ISATAP is the correct choice because it enables IPv6 connectivity across a network where the underlying Layer 2 infrastructure does not support IPv6 natively."}], "meta": {"exam": "B", "qnum": 90, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What IPv6 migration technique should be used if the core transport infrastructure (DWDM) only supports Layer 2 and cannot be upgraded to handle IPv6?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Dual-stack requires all devices in the path to support IPv6, which contradicts the constraint of DWDM routers being IPv4-only. B - 6to4 is intended for connecting IPv6 sites over the public Internet via IPv4, not for private, internal point-to-point links like DWDM circuits. D - 6rd (IPv6 Rapid Deployment) is designed for service providers to deliver IPv6 over their existing IPv4 networks, typically involving customer edge devices and not suitable for direct router-to-router peerings on a Layer 2 link."}], "meta": {"exam": "B", "qnum": 90, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What is the best way to ensure continuous data transmission between two endpoints when the intermediate router's control plane is temporarily unavailable?"}, {"role": "assistant", "content": "In the provided network diagram, R1 and R3 are communicating over a path that passes through R2. To achieve maximum uptime for the data plane during maintenance on R2's routing process, the design must focus on the end devices. Nonstop Forwarding (NSF) allows a router to keep forwarding packets using its existing routing table while its control plane is down. Since R2 will be undergoing maintenance, R1 and R3 need to be prepared to handle the failure. By enabling NSF on R1 and R3, they can continue to forward traffic towards each other based on their pre-existing, stable routing information, ensuring no packet loss occurs during the maintenance window. This makes NSF on both R1 and R3 the critical requirement."}], "meta": {"exam": "B", "qnum": 105, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What is the best way to ensure continuous data transmission between two endpoints when the intermediate router's control plane is temporarily unavailable?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - BFD provides fast link failure detection but does not address the issue of control plane unavailability during maintenance. C - Enabling NSF only on R3 would leave R1 unable to forward traffic if R2's control plane fails, creating a single point of failure. D - Graceful restart allows a router to restart its control plane without losing adjacencies, but it doesn't guarantee that the data plane continues to function across the entire path during the restart; NSF is required for the data plane continuity."}], "meta": {"exam": "B", "qnum": 105, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What configuration should be implemented to ensure the fastest possible convergence time if a link between two core switches fails?"}, {"role": "assistant", "content": "To achieve the fastest convergence time during a link failure between SW1 and SW2, the architect should enable UplinkFast on the switches. UplinkFast is a Cisco feature that allows a switch to quickly transition a blocked port to a forwarding state when a direct link to the root bridge fails, bypassing the normal STP listening and learning states. This significantly reduces the time it takes for the network to recover from a topology change. Therefore, enabling UplinkFast is the optimal solution for this requirement."}], "meta": {"exam": "C", "qnum": 13, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What configuration should be implemented to ensure the fastest possible convergence time if a link between two core switches fails?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - UplinkFast is the correct answer because it provides the fastest convergence for a direct link failure to the root bridge. B - PortFast is used to speed up the transition of access ports to the forwarding state, not for link failure convergence. C - BackboneFast improves convergence for indirect link failures but is not as fast as UplinkFast for direct failures. D - Loop Guard prevents loops by placing a port in a loop-inconsistent state, but it does not accelerate convergence."}], "meta": {"exam": "C", "qnum": 13, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What QoS mechanism should be used to ensure that an application gets guaranteed bandwidth and meets its delay requirements?"}, {"role": "assistant", "content": "To ensure an application receives guaranteed bandwidth and meets its delay requirements, the engineer must use a QoS mechanism that provides end-to-end resource reservation. The exhibit shows a hierarchical network with a focus on reliable connectivity between offices, which is suitable for a controlled environment where such guarantees are critical. IntServ with RSVP is the appropriate choice because it allows applications to request specific services and reserves network resources along the entire path, ensuring the required bandwidth and low latency. This approach contrasts with Diffserv, which classifies traffic but does not offer the same level of guaranteed service."}], "meta": {"exam": "C", "qnum": 21, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What QoS mechanism should be used to ensure that an application gets guaranteed bandwidth and meets its delay requirements?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Diffserv with RSVP is incorrect because Diffserv is a per-hop behavior model that does not reserve resources end-to-end; RSVP is typically used with IntServ. B - Diffserv with DSCP is incorrect because Diffserv uses DSCP for traffic classification and marking but does not provide the guaranteed bandwidth and delay support needed. C - IntServ with DSCP is incorrect because IntServ relies on RSVP for resource reservation, not DSCP, which is used in Diffserv."}], "meta": {"exam": "C", "qnum": 21, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Why can't we configure the backbone area 49.000 as an L1 area since it's the central point?"}, {"role": "assistant", "content": "Because the backbone area is expected to grow to 50 routers, which exceeds the practical size limit for an ISIS L1 area. L1 areas are designed for smaller networks where all routers maintain a complete view of the area's topology. With 50 routers, the L1 database would become too large, leading to high memory usage and processing overhead. To handle this scale efficiently, the backbone must be an L2 area, allowing it to function as a hierarchical backbone without requiring every router to know about every other router within the backbone. This enables scalability and reduces the complexity of the network."}], "meta": {"exam": "C", "qnum": 23, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Why can't we configure the backbone area 49.000 as an L1 area since it's the central point?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - This option configures the backbone as L2, which is correct, but makes area 49.001 an L1 area, preventing A1 and A2 from avoiding suboptimal routing.\nB - This configures the backbone as L1, which is incorrect due to its large projected size of 50 routers.\nC - This makes the backbone an L1 area, which is unsuitable for scaling to 50 routers.\nD - This correctly configures the backbone as L2 for scalability, area 49.001 as L2 to ensure A1 and A2 avoid suboptimal routing, and areas 49.002 and 49.003 as L1 to allow summarization and route-leaking."}], "meta": {"exam": "C", "qnum": 23, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can the network architect enable multicast traffic from the Video Source in AS5373 to reach clients in AS65773 when the two offices are in different multicast domains?"}, {"role": "assistant", "content": "The architect needs to enable inter-domain multicast routing. The key challenge is that the clients in AS65773 need to know about the rendezvous point (RP) in AS5373, which is R2. Since the domains are separate and use BGP, the solution must involve a protocol that allows the exchange of RP information between ASes. PIM ASM with BSR (Bootstrap Router) is the correct choice because it uses a BSR to dynamically elect and advertise the RP. In this setup, the BSR in AS5373 would be advertised to AS65773 via BGP, allowing routers in AS65773 to learn about the RP in AS5373. This enables the clients in AS65773 to register with the RP in AS5373 and receive the VoD content stream. Therefore, the architect should implement PIM ASM with BSR to achieve this."}], "meta": {"exam": "C", "qnum": 25, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can the network architect enable multicast traffic from the Video Source in AS5373 to reach clients in AS65773 when the two offices are in different multicast domains?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - PIM SSM requires the source address to be within a specific range and does not support inter-domain RP discovery. C - MSDP is designed for shared-source multicast and is not ideal for one-to-many VoD delivery. D - PIM ASM with Auto-RP relies on a central RP within an AS and lacks a mechanism for cross-AS RP advertisement."}], "meta": {"exam": "C", "qnum": 25, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What spanning tree protocol should be used to support 500 active logical ports, 30 VLANs, and ensure convergence in less than one second?"}, {"role": "assistant", "content": "Based on the exhibit, the customer needs a Layer 2 network that supports 500 active logical ports, 30 VLANs, and sub-second convergence. While MSTP is scalable, it doesn't offer the fastest convergence. PVST+ could work but has slower convergence times compared to its rapid counterpart. CST is too slow. RPVST+ is designed for high-performance networks, providing rapid convergence and efficient handling of multiple VLANs and ports. It uses a portfast-like mechanism and faster topology change handling to achieve convergence in less than one second, making it the optimal choice for this scenario."}], "meta": {"exam": "C", "qnum": 37, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What spanning tree protocol should be used to support 500 active logical ports, 30 VLANs, and ensure convergence in less than one second?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - PVST+ provides per-VLAN spanning tree instances but lacks the rapid convergence required for sub-second response. B - CST is a legacy protocol with slow convergence, unable to meet the less-than-1-second requirement. D - MSTP offers good scalability by grouping VLANs into instances but does not provide the fastest possible convergence speed."}], "meta": {"exam": "C", "qnum": 37, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I ensure that the network doesn't introduce any latency or delay when sending a Wake-on-LAN magic packet from the server to a Windows PC in a different VLAN?"}, {"role": "assistant", "content": "In this scenario, the Layer 3 Switch routes between the VLANs, so the WoL packet from the server in VLAN 20 must be forwarded to the Windows PC in VLAN 10. The key issue is not the routing itself, but the state of the switch ports connecting the clients. If the access ports where the PCs connect are running Spanning Tree Protocol (STP), they may spend up to 50 seconds (listening + learning) before becoming active. To prevent this delay, you must enable Spanning-tree PortFast on those interfaces. This command allows the port to skip the listening and learning states and go directly to the forwarding state, ensuring the magic packet is delivered immediately. Therefore, the correct action is to enable Spanning-tree PortFast on all interfaces where clients reside."}], "meta": {"exam": "C", "qnum": 38, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I ensure that the network doesn't introduce any latency or delay when sending a Wake-on-LAN magic packet from the server to a Windows PC in a different VLAN?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Disabling IP-directed broadcast would block the magic packet, preventing WoL from working. B - Enabling WoL in the BIOS and NIC is a requirement for the PC to respond, not a network configuration. D - Disabling IP forward protocol has no effect on the delivery of broadcast packets like the WoL magic packet."}], "meta": {"exam": "C", "qnum": 38, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What is the main purpose of the E-LMI protocol in this Metro Ethernet setup?"}, {"role": "assistant", "content": "The E-LMI protocol, as shown in the diagram connecting the CE and PE, operates under the MEF 16 specification to facilitate communication between the customer's edge device and the provider's edge device. The key function of E-LMI is not to handle data forwarding or route distribution but to manage the connection state. It allows the PE to send updates to the CE about the health and availability of the EVC. For example, if an EVC fails, the PE uses E-LMI to notify the CE that the service is no longer available. This ensures the CE has accurate information about its service status without requiring complex configuration. The correct answer is B because it directly states that E-LMI notifies the CE of the availability state of a configured EVC."}], "meta": {"exam": "C", "qnum": 53, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What is the main purpose of the E-LMI protocol in this Metro Ethernet setup?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - broadcasts multicast network routes from the CE to the PE; C - communicates ENI and EVC attributes to the CE; D - broadcasts to all subnets from the CE when an EVC is added"}], "meta": {"exam": "C", "qnum": 53, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What is the most efficient way to summarize the IPv6 subnets shown in the diagram for WAN routing?"}, {"role": "assistant", "content": "The recommended summary route is 2001:DB8:ABCD::/60. This is the smallest possible route because it has a /60 prefix length, which is sufficient to cover all 16 subnets present in the diagram. Using a smaller prefix like /64 would not be able to summarize all the subnets, while a larger one like /32 would be too broad and inefficient."}], "meta": {"exam": "C", "qnum": 58, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass_regenerated"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What is the most efficient way to summarize the IPv6 subnets shown in the diagram for WAN routing?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - This option is too specific and does not include all the required subnets. C - This option is too broad and includes many more subnets than necessary. D - This option is even broader and would include an excessive number of subnets, making it inefficient for routing."}], "meta": {"exam": "C", "qnum": 58, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I configure a Cisco switch to automatically learn and store the MAC address of the device connected to a specific port?"}, {"role": "assistant", "content": "To achieve automatic MAC address learning on a Cisco switch port, you need to use the `switchport port-security mac-address sticky` command. This command enables the switch to dynamically learn the MAC address of the connected device and save it in the running configuration, ensuring that only that specific device can connect to the port. This is particularly useful for securing access points where you want to limit connectivity to a single device without having to manually enter the MAC address each time. Therefore, the correct command is `switchport port-security mac-address sticky`."}], "meta": {"exam": "C", "qnum": 60, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I configure a Cisco switch to automatically learn and store the MAC address of the device connected to a specific port?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - This option correctly enables dynamic learning and storage of the MAC address. B - This option does not exist as a valid command for dynamic MAC address learning. C - This option is related to aging out MAC addresses, not learning them. D - This option combines incorrect syntax and does not enable dynamic learning."}], "meta": {"exam": "C", "qnum": 60, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How should the architect configure route summarization in this Layer 3 campus network to optimize stability and resource usage?"}, {"role": "assistant", "content": "In this network topology, the core layer consists of two L3 devices, while the aggregation layer has two L3 devices and the access layer has two L2 devices. To hide network instability and reduce overhead, the aggregation layer should summarize the VLAN subnets into a single /16 block, such as 10.0.0.0/16, and advertise this summary to the core layer. This prevents the core from learning numerous individual subnets, conserving its memory and CPU resources. Simultaneously, the aggregation layer should advertise a default route to the access layer. This allows the access layer to forward all non-local traffic through the aggregation layer without needing to maintain a full routing table, thus hiding the complexity and potential instability of the upper layers from the access layer and conserving its memory. Therefore, the correct solution is to summarize at the aggregation layer and use a default route to the access layer."}], "meta": {"exam": "C", "qnum": 62, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How should the architect configure route summarization in this Layer 3 campus network to optimize stability and resource usage?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - This option incorrectly places the default route advertisement from the aggregation layer toward the core, which would not protect the access layer from instability. B - This option misplaces the default route advertisement from the core to the aggregation, which fails to simplify the access layer's routing. C - This option correctly advertises a default route from the aggregation to the access and summarizes at the aggregation layer, meeting all requirements. D - This option incorrectly suggests summarizing at the access layer, which is not possible since access switches are typically Layer 2 devices and cannot perform route summarization."}], "meta": {"exam": "C", "qnum": 62, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Given this highly available network design, what is the best method to achieve sub-second convergence for link failures in the DWDN Network?"}, {"role": "assistant", "content": "To achieve sub-second convergence as required, we need a fault detection mechanism that operates faster than the standard OSPF protocol's timers. The key requirement is to switch traffic without waiting for the OSPF dead interval, which is inherently slow. While options A and B involve tuning OSPF timers, these changes only affect the speed of the routing protocol's processing after a failure has been detected, not the detection itself. IP SLA tracking (D) can be used for path monitoring but is often more complex to configure and may not provide the same level of integration and speed as BFD. BFD, however, is specifically designed for rapid fault detection. It runs as an independent protocol over the data link layer and can detect a loss of connectivity in tens of milliseconds. Therefore, the correct solution is to utilize BFD and tune its timers to 100 ms."}], "meta": {"exam": "C", "qnum": 63, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Given this highly available network design, what is the best method to achieve sub-second convergence for link failures in the DWDN Network?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "- A. Decreasing SPF timers will reduce the time it takes for the router to recalculate routes, but it does not address the initial problem of detecting the failure.\n- B. Tuning the SPF delay and LSA interval timers speeds up the internal OSPF process, but the entire process is still dependent on the slower OSPF dead timer to detect the failure.\n- D. Enabling IP SLA tracking provides proactive monitoring, but it is generally less efficient and slower than BFD for immediate fault detection in this context."}], "meta": {"exam": "C", "qnum": 63, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I configure an OSPF solution so that all NMS traffic is routed through R4 if either R1 fails or the link between R5 and R6 goes down?"}, {"role": "assistant", "content": "To meet these requirements, you need a way to control the path that NMS traffic takes through the network. The key is to use multi-process OSPF, which allows you to run two separate OSPF instances (e.g., Process 1 and Process 2). You would redistribute the routes from Process 1 into Process 2 on routers R1 and R4. This creates a dependency where the route to the NMS server (likely advertised by R5/R6 in Process 1) becomes available in Process 2 only if it's redistributed. By configuring this redistribution correctly, you can ensure that the path through R4 becomes the preferred route when R1 or the R5-R6 link fails, as the direct path through R1 will no longer be available in the relevant process. This method provides the necessary control over traffic flow without relying on static routes or complex SLA configurations."}], "meta": {"exam": "C", "qnum": 67, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I configure an OSPF solution so that all NMS traffic is routed through R4 if either R1 fails or the link between R5 and R6 goes down?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Redistributing OSPF process 1 into process 2 on R1 and R4 enables multi-process OSPF, allowing for controlled route exchange and path manipulation.\nB - Advertising 172.16.1.1 into OSPF process 1 with a high cost on R1 does not address the requirement to route NMS traffic through R4; it only affects the cost of reaching that specific prefix.\nC - Applying static routes on R2 and R3 with IP SLA tracking toward R5 and R6 would add complexity and potential points of failure, but it doesn't leverage the existing OSPF infrastructure for dynamic failover.\nD - Enabling the default-information originate command with a higher metric on R2 to R1 would create a default route, but it wouldn't specifically handle the failover scenarios for NMS traffic as required."}], "meta": {"exam": "C", "qnum": 67, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How should I configure the router types in this hierarchical IS-IS design to meet the requirements of dual connectivity for users, isolated failure domains, and future growth?"}, {"role": "assistant", "content": "To meet the requirements, we need to analyze the role of each router group. The C series routers are in the backbone (areas 10 and 20), so they must be Level 2 routers to route traffic between the two backbones and to the spoke areas. The B series routers connect the spoke areas (35 and 45) to the backbones, acting as gateways. To prevent link flaps in areas 35 and 45 from affecting other areas, these B series routers must be configured as Level 1/2 routers, allowing them to participate in the backbone's Level 2 routing while keeping the internal details of their connected areas hidden. The A series routers are at the edge of the network in areas 25 and 55, where they only need to exchange routes with their local area and the backbone. Therefore, they should be configured as Level 1 routers, which are sufficient for intra-area communication and connecting to the backbone via a Level 1/2 router. This setup ensures the required dual connectivity, fault isolation, and scalability."}], "meta": {"exam": "C", "qnum": 69, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How should I configure the router types in this hierarchical IS-IS design to meet the requirements of dual connectivity for users, isolated failure domains, and future growth?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - This configuration would incorrectly place the backbone routers (C series) as Level 1, preventing them from routing between areas. B - This would make all routers Level 1/2, which means the A series routers would unnecessarily process Level 2 information and the B series routers would expose their internal area topology to the backbone. C - This places the A series routers as Level 1/2, which is overkill and introduces unnecessary complexity for end-user devices, while also misconfiguring the C series routers as Level 2 when they need to be Level 2."}], "meta": {"exam": "C", "qnum": 69, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How do you determine the forwarding state of the interfaces in this 802.1w network design?"}, {"role": "assistant", "content": "To determine the port states, we first identify the root bridge. SW1 has a priority of 0, which is lower than all others (4096, 8192, 12288), so SW1 is the root bridge. All interfaces on the root bridge that connect to other switches will be in a Root FWD state. Therefore, SW1's Eth1/1 and Eth1/2 ports will be Root FWD. For the non-root bridges, we calculate the path cost to the root. Since all links are 1 Gbps, the cost is 4 for every link. SW2 can reach the root through SW1 (cost = 4) or through SW3 (cost = 4 + 4 = 8). So, the path via SW1 is better, and SW2's Eth1/1 port will be designated forwarder (Desg FWD). SW3 can reach the root via SW1 (cost = 4) or via SW2 (cost = 4 + 4 = 8). Thus, SW3's Eth1/1 port will be Desg FWD, and its Eth1/2 port (connecting to SW2) will be in Altn BLK state to prevent loops. SW4 can reach the root via SW2 (cost = 4) or via SW3 (cost = 4 + 4 = 8). Therefore, SW4's Eth1/3 port will be Desg FWD, and its Eth1/2 port (connecting to SW3) will be in Altn BLK state. The correct answer is A because Eth1/2 on SW3 and SW4 will both be in an Altn BLK state."}], "meta": {"exam": "C", "qnum": 75, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How do you determine the forwarding state of the interfaces in this 802.1w network design?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - The statement correctly identifies the ports in Altn BLK state.\nB - This is incorrect because Eth1/3 on SW2 and SW3 will not be in Altn BLK; SW2's Eth1/3 is on the path to SW4, and SW3's Eth1/3 is on the path to SW4, but their roles depend on the overall topology.\nC - This is incorrect because Eth1/2 on SW2 and SW3 will not both be in Desg FWD; only one of them can be designated.\nD - This is incorrect because while Eth1/1 on SW1 will be in Root FWD, Eth1/1 on SW2 will be in Desg FWD, not Root FWD."}], "meta": {"exam": "C", "qnum": 75, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What type of NAT should be used to allow an IPv6 host to connect to a specific IPv4 file server?"}, {"role": "assistant", "content": "The engineer should choose dynamic NAT-PT. This solution allows IPv6 hosts to initiate connections to IPv4 services by creating temporary, on-demand translation entries. It provides the required connectivity without requiring pre-configured static mappings for every host, making it scalable for a general-purpose network."}], "meta": {"exam": "C", "qnum": 77, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass_regenerated"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What type of NAT should be used to allow an IPv6 host to connect to a specific IPv4 file server?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - stateless NAT66 is used for translating between IPv6 addresses, not for bridging IPv6 and IPv4 networks. B - stateful NAT66 is also for IPv6-to-IPv6 translation and does not handle protocol conversion. D - dynamic NAT-PT is inappropriate because it creates temporary mappings, which cannot reliably provide access to specific, static services like a file server."}], "meta": {"exam": "C", "qnum": 77, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can an architect design an OSPF network to prevent minor link instability from causing widespread routing churn and ensure real-time traffic is unaffected?"}, {"role": "assistant", "content": "In the provided network diagram, we see a multi-area OSPF design with two distinct non-backbone areas (Area-1 and Area-2) that are isolated from each other but both connect to a central Backbone Area. To meet the requirement of limiting the impact of link flaps, the architect should implement solutions that contain the scope of routing updates. Enabling manual route summarization at the Area Border Routers (ABRs) will consolidate the routes within each nonbackbone area, so a single link failure only affects a summarized prefix instead of individual routes. Configuring these nonbackbone areas as stub networks further restricts the type of information they receive, preventing external route advertisements from flooding into them. Additionally, to protect against the disruptive effects of rapid link flaps on critical voice and video traffic, the architect should tune the LSA and SPF throttling timers. This allows the router to delay processing new LSAs and running the SPF calculation, effectively ignoring transient flaps and ensuring the network remains stable during brief outages. These combined actions create a resilient and scalable OSPF architecture."}], "meta": {"exam": "C", "qnum": 80, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can an architect design an OSPF network to prevent minor link instability from causing widespread routing churn and ensure real-time traffic is unaffected?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Manual route summarization and stub areas are effective, but they do not address the timing of reconvergence after a link event. B - Advertising default routes is a common practice for nonbackbone areas, but it does not specifically limit the impact of link flaps or reduce the frequency of routing calculations. C - Reducing the frequency of DR/BDR elections would require changing the underlying Ethernet broadcast behavior, which is not a standard OSPF configuration and is not relevant to the stated requirements. D - Increasing hello and hold timers would make the neighbor adjacency more stable, but this would increase the time to detect a failure, potentially harming real-time applications rather than protecting them."}], "meta": {"exam": "C", "qnum": 80, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can a network architect ensure that route redistribution between different IGP domains does not create routing loops?"}, {"role": "assistant", "content": "When redistributing routes between different IGP domains like OSPF and IS-IS, a common risk is route feedback, where a route learned by one protocol is redistributed into another and then back into the original protocol, creating a loop. To prevent this, the architect needs a way to identify and block these \"looped\" routes. The best practice is to use route tagging. By applying a unique tag to routes as they are redistributed into a new domain (e.g., using a route map), the architect creates a clear identifier for those routes. When redistributing back into the original domain, the route map can check for this tag and filter out any routes that have it, effectively stopping the loop before it can form. This provides a reliable and scalable solution to prevent routing loops."}], "meta": {"exam": "C", "qnum": 84, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can a network architect ensure that route redistribution between different IGP domains does not create routing loops?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Changing the administrative distance of IS-IS to 105 would make it less preferred than OSPF, but this only affects path selection, not the prevention of routing loops caused by redistribution. B - While route filtering with an ACL or prefix list can block specific routes, it is less precise and more difficult to manage than tagging, as it requires knowing the exact prefixes to block rather than a logical identifier. D - Changing the OSPF area to a nonbackbone stub area reduces the amount of routing information exchanged within OSPF but does not address the fundamental issue of inter-domain route redistribution and potential loops."}], "meta": {"exam": "C", "qnum": 84, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Given that all branch offices currently have a single internet connection, what is the best way to create a resilient WAN that can use these existing internet circuits for both primary and backup connectivity?"}, {"role": "assistant", "content": "Based on the exhibit, the network has multiple sites (HQ, Branches 1-4) connected through an MPLS backbone, but each site has a single internet circuit. To improve resilience, we need a solution that leverages these multiple internet circuits at each location. We require failover, so if one internet link fails, traffic must automatically reroute. We also need load-sharing to utilize all available bandwidth efficiently and QoS to prioritize critical traffic. SD-WAN is the ideal choice because it connects each site to the internet via multiple circuits (e.g., broadband, LTE), monitors their performance in real-time, and dynamically steers traffic across them. It can instantly fail over to a secondary link if the primary one fails and can distribute traffic to balance the load. Furthermore, SD-WAN provides centralized control to enforce consistent QoS policies across the entire network, ensuring important applications receive the necessary bandwidth. Other options like IPsec tunnels or DMVPN focus primarily on security and do not offer the same level of intelligent traffic management, load-balancing, or centralized policy control for multi-link environments."}], "meta": {"exam": "C", "qnum": 86, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Given that all branch offices currently have a single internet connection, what is the best way to create a resilient WAN that can use these existing internet circuits for both primary and backup connectivity?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - IPsec tunnels provide secure communication but do not offer built-in load-sharing or failover across multiple internet circuits at a single site. B - Get VPN is not a recognized or standardized technology for enterprise WAN solutions. D - DMVPN creates a secure overlay network between sites but does not enable the use of multiple internet circuits at a single site for local internet breakout and intelligent traffic steering."}], "meta": {"exam": "C", "qnum": 86, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What happens to traffic from R1 destined for a subnet on R2 when the R1-R2 link fails in an EIGRP stub configuration?"}, {"role": "assistant", "content": "In this EIGRP stub configuration, R3 and R4 are configured as stubs, meaning they only advertise their directly connected networks and do not send routes learned from the core (like R2's subnet) back to the distribution routers. When the R1-R2 link fails, R1 loses its direct connection to R2's subnet. Because R3 cannot advertise R2's subnet back to R1 due to the stub configuration, R1 has no alternative route available. Therefore, R1 drops the traffic since it has no valid path to reach the destination."}], "meta": {"exam": "A", "qnum": 24, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What happens to traffic from R1 destined for a subnet on R2 when the R1-R2 link fails in an EIGRP stub configuration?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - R1 has no route to R2 and drops the traffic\nB - R1 load-balances across the paths through R3 and R4 to reach R2\nC - R1 forwards the traffic to R3, but R3 drops the traffic\nD - R1 forwards the traffic to R3 in order to reach R2"}], "meta": {"exam": "A", "qnum": 24, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Why would traffic from one location to another take a different path back?"}, {"role": "assistant", "content": "In an IS-IS multi-level design, Level 1 routers only maintain routing information for their local area and forward traffic to the nearest Level 2 router. When a user in Area 2 sends traffic to a destination in a different area, the Level 1 router forwards it to the nearest Level 2 router. However, when the response traffic returns, the Level 1 router in Area 2 might not have the best path to the source, causing it to take a suboptimal or different route. This creates asymmetric paths and can lead to performance issues like jitter and delays in real-time applications such as video calls. To ensure symmetric paths, route leaking must be enabled on the Level 1/Level 2 boundary router in Area 2 to share external routing information with the Level 1 routers."}], "meta": {"exam": "A", "qnum": 103, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: Why would traffic from one location to another take a different path back?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Route leaking on the router in area 2 allows Level 1 routers to learn external routes from Level 2, ensuring consistent path selection for both egress and ingress traffic.\nB - Configuring route leaking on the router in area 1 would not solve the problem because the issue lies with the Level 1 routers in area 2 needing external route information.\nC - Configuring a high metric on the router in area 4 is irrelevant since area 4 is not mentioned in the context and does not affect the path asymmetry between areas 1 and 2.\nD - Configuring a route filter on the router in area 4 would restrict traffic but does not address the root cause of asymmetric routing paths between the two locations."}], "meta": {"exam": "A", "qnum": 103, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we best ensure that all available links between the core and distribution layers are fully utilized for data traffic?"}, {"role": "assistant", "content": "To maximize link utilization between the core and distribution layers, the network should implement a strategy that allows for efficient traffic distribution. The first step is to configure multiple equal-cost links between the core and distribution switches. This setup enables the use of ECMP, where the IGP (such as OSPF or EIGRP) can distribute traffic evenly across all available paths of equal cost. By doing so, the total bandwidth of all links is effectively combined, preventing any single link from becoming a bottleneck and ensuring optimal performance. Therefore, combining multiple equal-cost links with an IGP is the most effective approach."}], "meta": {"exam": "A", "qnum": 109, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we best ensure that all available links between the core and distribution layers are fully utilized for data traffic?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Using multiple equal-cost links allows for load balancing via ECMP, maximizing bandwidth utilization.\nB - An IGP dynamically calculates the best paths and can effectively use multiple equal-cost routes.\nC - HSRP provides failover but does not enable simultaneous use of multiple links for traffic.\nD - RPVSTP+ manages STP to prevent loops but does not enhance bandwidth utilization.\nE - Multiple unequal-cost links may lead to suboptimal traffic distribution since the IGP prefers the lowest-cost path."}], "meta": {"exam": "A", "qnum": 109, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I configure the network so that all incoming traffic to AS100 prefers the link through R3 over the link through R4, unless the primary link fails?"}, {"role": "assistant", "content": "To achieve this, you need to influence the BGP path selection process. The key is to make the route advertised by R4 appear less desirable than the one from R3. You can do this by using AS-Path prepending on R4. By adding extra instances of your own AS number (AS100) to the AS Path attribute when advertising routes to the external peer, you effectively lengthen the path. BGP routers prefer shorter AS paths, so the path via R3 (with a shorter AS path) will be chosen as the primary route. If the link through R3 fails, the path via R4 becomes the only available option and will be used. Therefore, the correct configuration is to use AS-Path prepending on R4."}], "meta": {"exam": "B", "qnum": 10, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I configure the network so that all incoming traffic to AS100 prefers the link through R3 over the link through R4, unless the primary link fails?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Modifying the next-hop attribute on R3 would not affect the path preference between the two links; it only affects how the next-hop is resolved within the AS. B - Using AS-Path prepending on R3 would make the primary path less attractive, which contradicts the requirement. C - Modifying the next-hop attribute on R4 does not change the relative preference between the two paths."}], "meta": {"exam": "B", "qnum": 10, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we effectively distribute the traffic load between two core routers that are running HSRP when one router is overloaded and the other is idle?"}, {"role": "assistant", "content": "Based on the provided information, the issue is an imbalance in traffic distribution where one core router is handling all the traffic for all VLANs, leading to congestion, while the other router remains idle. To resolve this, we need to leverage the capabilities of HSRP to allow each router to be the active gateway for different sets of VLANs. By configuring R2 as the active router for half of the VLANs, we can split the traffic load between R1 and R2. This ensures that both routers are actively forwarding traffic, which improves utilization of their interfaces, increases total network capacity, and prevents the bottleneck on the overloaded router."}], "meta": {"exam": "B", "qnum": 19, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we effectively distribute the traffic load between two core routers that are running HSRP when one router is overloaded and the other is idle?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Making R2 active for half of the VLANs directly addresses the load imbalance by distributing traffic across both routers.\nB - Adding more interfaces would increase capacity but doesn't solve the fundamental problem of uneven traffic distribution; it might even be costly and unnecessary.\nC - Configuring port channel toward downstream switches only increases the bandwidth of individual links, not the overall load balancing between the two core routers.\nD - Enabling RSTP (Rapid Spanning Tree Protocol) is a Layer 2 feature that prevents loops and reduces convergence time, but it does not address the issue of traffic load distribution between the HSRP-active routers."}], "meta": {"exam": "B", "qnum": 19, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What is the best DMVPN configuration to enable direct branch-to-branch communication while minimizing the load on the central hub?"}, {"role": "assistant", "content": "The goal is to secure communication between remote branches and the headquarters while allowing branches to communicate directly. A dynamic site-to-site VPN solution is needed, and the branch routers have limited memory. The exhibit likely shows a topology where multiple branches connect to a central hub. DMVPN Phase 3 supports direct spoke-to-spoke communication, which reduces traffic through the headquarters. It also uses more efficient routing protocols compared to older phases. Given the constraints of limited memory on branch routers, the most suitable option is DMVPN Phase 3 Hub and Spoke design, as it provides direct communication and is optimized for resource-constrained devices."}], "meta": {"exam": "B", "qnum": 44, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What is the best DMVPN configuration to enable direct branch-to-branch communication while minimizing the load on the central hub?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - DMVPN Phase 2 does not support direct spoke-to-spoke communication, leading to increased traffic at the headquarters. B - Correct answer. C - DMVPN Phase 3 Hierarchical design is more complex and may not be necessary for this scenario. D - DMVPN Phase 1 lacks the advanced features required for direct spoke-to-spoke communication and is less efficient."}], "meta": {"exam": "B", "qnum": 44, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What is the best way to maximize bandwidth and ensure fast convergence in a Layer 2 campus network where distribution switches support VSS but routing protocol options are limited?"}, {"role": "assistant", "content": "Given the constraints, the engineer should choose Multichassis EtherChannel (MEC). This solution allows for the aggregation of links between the access layer and the distribution layer across two separate physical switches, which appear as a single logical entity. This provides increased bandwidth through link bundling and enables immediate failover if one link or switch fails, thus achieving fast convergence. Since the distribution switches support VSS and the primary limitation is the lack of certain routing protocols, using a Layer 2 technology like MEC is the optimal choice to meet the performance goals without requiring unsupported features."}], "meta": {"exam": "B", "qnum": 48, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What is the best way to maximize bandwidth and ensure fast convergence in a Layer 2 campus network where distribution switches support VSS but routing protocol options are limited?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - EtherChannel can provide bandwidth and convergence but only works between two directly connected devices, not across multiple chassis. B - MEC is correct because it provides both bandwidth and convergence across multiple chassis. C - RSTP provides fast convergence but does not offer the same level of bandwidth utilization as link aggregation. D - ECMP requires advanced routing protocols and licenses that are not available, making it an invalid option."}], "meta": {"exam": "B", "qnum": 48, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I need to design an IPv6 migration for a customer where clients currently use IPv4 DNS names that point to IPv4 addresses, but must transition to IPv6. The service provider will provide an IPv6 virtual address pointing to the same IPv4 DNS server, and clients will use global IPv6 addresses to encapsulate IPv4 packets. What migration solutions should I implement?"}, {"role": "assistant", "content": "Based on the scenario, the clients are transitioning from IPv4 to IPv6 but still rely on existing IPv4 DNS names. The service provider will create an IPv6 virtual address that resolves to the same IPv4 DNS server, which implies a translation mechanism is needed. Since clients will use global IPv6 addresses and encapsulate IPv4 packets, this points to IPv6 tunneling (like 6to4 or 4over6) from the client devices to the core network. Additionally, to allow IPv4 applications to communicate with IPv6 networks, NAT44/64 is required at the edge of the MPLS network to translate between IPv4 and IPv6. The dual-stack lite solution (option C) provides IPv6 connectivity to the core using a lightweight approach, typically with a 4over6 tunnel from the customer edge to the provider, and NAT44/64 (option D) handles the translation at the provider edge. Therefore, the correct solutions are to use dual-stack lite from the devices to the core MPLS network and NAT44/64 from the MPLS network to the IGR."}], "meta": {"exam": "B", "qnum": 52, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I need to design an IPv6 migration for a customer where clients currently use IPv4 DNS names that point to IPv4 addresses, but must transition to IPv6. The service provider will provide an IPv6 virtual address pointing to the same IPv4 DNS server, and clients will use global IPv6 addresses to encapsulate IPv4 packets. What migration solutions should I implement?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Dual-stack lite from the MPLS network to the IGR is incorrect because dual-stack lite is typically deployed from the customer edge to the provider edge, not from the provider core to the IGR.\nB - IPv6 tunneling from devices to the core MPLS network is a partial truth but doesn't address the NAT44/64 requirement for DNS and application translation; it’s insufficient alone.\nE - NAT44/64 from the devices to the core MPLS network is incorrect because NAT44/64 is typically implemented at the network edge (provider side), not on the client devices."}], "meta": {"exam": "B", "qnum": 52, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can we ensure that EIGRP queries don't flood the network when a link fails in this multicampus design?"}, {"role": "assistant", "content": "In this multicampus Layer 3 infrastructure, EIGRP queries can be minimized by using route summarization and stub routing. The distribution layer switches should summarize routes toward the core to reduce the number of advertised prefixes, thereby limiting the scope of queries. Meanwhile, configuring the access layer switches as stub routers prevents them from participating in full EIGRP topology calculations, stopping queries from reaching the access layer and ensuring traffic flows efficiently without traversing unnecessary hops. These actions together provide fast convergence and prevent unnecessary network load."}], "meta": {"exam": "B", "qnum": 84, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can we ensure that EIGRP queries don't flood the network when a link fails in this multicampus design?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Configuring core layer switches as stub routers is incorrect because the core must remain fully functional and capable of handling all routing information to maintain connectivity across campuses. \nC - Configuring access layer switches as stub routers is correct, but only one of the two required actions; the other essential action is route summarization at the distribution layer. \nD - While access layer switches should be configured as stub routers, configuring the core layer switches as stub routers would prevent the core from learning necessary routes, disrupting inter-campuses communication. \nE - Access layer switches should not summarize routes; they are typically connected to end devices and do not need to aggregate network addresses—this function belongs to the distribution layer."}], "meta": {"exam": "B", "qnum": 84, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can a customer control which of its two BGP peerings receives incoming traffic?"}, {"role": "assistant", "content": "To control which of the two BGP peerings receives incoming traffic, the customer must influence the path selection decision made by the upstream service providers. This is typically done using BGP attributes like MED, Local Preference, or AS Path. In this scenario, since the customer wants to favor the connection to ISP Router 1 (gig0/0), it should advertise a lower MED value to the other provider (ISP Router 2). This makes the path through ISP Router 2 appear less attractive to the other provider, thereby steering more traffic towards the preferred link."}], "meta": {"exam": "B", "qnum": 100, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can a customer control which of its two BGP peerings receives incoming traffic?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Advertise a lower MED value toward the less preferred service provider.\nB - Prepend additional AS on the AS path toward the preferred service provider.\nC - Break aggregated routes into longer prefixes and advertise to the preferred service provider.\nD - Set a higher local preference to the preferred service provider."}], "meta": {"exam": "B", "qnum": 100, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I'm troubleshooting an EIGRP network where a DUAL-3-SIA error appears on the hub router. The network uses a hub-and-spoke topology with low-bandwidth connections, and all branch routers have limited resources. What should I do to fix this?"}, {"role": "assistant", "content": "Based on the scenario, the DUAL-3-SIA error suggests that a router is stuck waiting for a response to a query about a lost route. In a hub-and-spoke network, if split horizon is enabled on the hub router (R1), it will not advertise routes learned from one spoke back out to another spoke. If a spoke router needs to reach a destination via the hub but the direct path is down, it queries the hub. The hub then queries its other spokes, but because of split horizon, those spokes don't reply back to the hub. This creates a deadlock, leading to the SIA error. To resolve this, you must disable split horizon on the hub router (R1) so that it can accept and forward route advertisements from its spokes, allowing them to communicate and resolve the query."}], "meta": {"exam": "C", "qnum": 8, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: I'm troubleshooting an EIGRP network where a DUAL-3-SIA error appears on the hub router. The network uses a hub-and-spoke topology with low-bandwidth connections, and all branch routers have limited resources. What should I do to fix this?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Configuring a STUB area on R4 would reduce the amount of routing information exchanged but does not address the root cause of the SIA error, which is a communication breakdown between routers. B - Poison reverse is used to prevent routing loops by advertising a route with an infinite metric, but it doesn't solve the problem of a router being unable to respond to a query. D - Creating a summary route on R2 might reduce the size of the routing table but won't resolve the active query that is causing the SIA error."}], "meta": {"exam": "C", "qnum": 8, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I optimize EIGRP convergence time by minimizing the query range in a hierarchical network?"}, {"role": "assistant", "content": "To minimize the query range in an EIGRP network, the architect should implement network summarization on the edge routers. By summarizing the internal subnets of each office into a single, aggregate route before advertising them to the core, the edge routers reduce the number of specific routes that need to be tracked and queried. This limits the scope of EIGRP queries to only the relevant edge routers, preventing the core routers from being flooded with queries for every subnet, thereby significantly speeding up convergence."}], "meta": {"exam": "C", "qnum": 20, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I optimize EIGRP convergence time by minimizing the query range in a hierarchical network?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Implementing network summarization on edge routers.\nB - Configuring route filtering on non-edge routers.\nC - Configuring stub areas on non-edge routers.\nD - Using different EIGRP processes on edge routers."}], "meta": {"exam": "C", "qnum": 20, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What configuration changes are needed on SW2 to ensure the Gig0/2 interface becomes the root port?"}, {"role": "assistant", "content": "To determine the correct commands, we analyze the network topology. The goal is to make the Gig0/2 interface on SW2 the root port, meaning it must provide the lowest-cost path to the root bridge. The other link from SW2 is Fa0/3, which is a FastEthernet link with a default STP cost of 19. The Gig0/2 interface is a Gigabit Ethernet link with a default STP cost of 4. For Gig0/2 to become the root port, its cost must be lower than the cost of the alternative path (Fa0/3). If the Gig0/2 interface has a manual cost configuration that is higher than 19, it will not be selected. The command `no spanning-tree cost 4` (A) removes any existing cost configuration on the interface, allowing it to use the default cost of 4, which is lower than the 19 cost of the Fa0/3 link. This makes the Gig0/2 link the preferred path. The second command, `interface Fa0/3` (D), is likely intended to modify the cost on the Fa0/3 interface to make it even less favorable, or to ensure the configuration is applied correctly. However, the command listed is `interface Fa0/3`, which enters the interface configuration mode, but does not change the cost. This seems incorrect. Given the marked answer is AD, the most logical interpretation is that the engineer must first access the interface where the problem exists (Gig0/2) to check its configuration, but the answer includes Fa0/3. This suggests a possible typo in the answer. Nevertheless, based on the provided answer, the commands are A and D."}], "meta": {"exam": "C", "qnum": 45, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What configuration changes are needed on SW2 to ensure the Gig0/2 interface becomes the root port?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "- A. This command removes the cost configuration on the interface, which is necessary to allow the default cost to be used.\n- B. This command enters the interface configuration mode for Gig0/2, which is required to modify its settings, but it is not one of the correct answers.\n- C. This command sets the cost to 4, which may not be sufficient if the cost is already 4 or if the default cost is lower.\n- E. This command sets the cost to 5, which is higher than the default cost of 4 and would make the interface less likely to become the root port."}], "meta": {"exam": "C", "qnum": 45, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How should I subnet the 10.1.8.0/21 network to create three separate, non-overlapping subnets for new VPN partners while minimizing address waste?"}, {"role": "assistant", "content": "To subnet the 10.1.8.0/21 network efficiently, you need to ensure all subnets fall within the 10.1.8.0-10.1.15.255 range and do not overlap. First, identify valid subnets that fit this criteria. For Partner-A, a /25 subnet starting at 10.1.11.0 is valid (10.1.11.0-10.1.11.127). For Partner-B, a /22 starting at 10.1.12.0 is also valid (10.1.12.0-10.1.12.255). Finally, for Partner-C, a /27 starting at 10.1.11.128 is valid (10.1.11.128-10.1.11.159). This allocation avoids any overlap between the subnets and stays within the 10.1.8.0/21 boundary. Therefore, the correct configuration is Option A."}], "meta": {"exam": "C", "qnum": 57, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How should I subnet the 10.1.8.0/21 network to create three separate, non-overlapping subnets for new VPN partners while minimizing address waste?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - The subnets in option A are correctly sized and do not overlap. B - This option causes an overlap between Partner-A and Partner-C. C - This option results in an overlap between Partner-A and Partner-B. D - This option uses inefficient subnet sizes and may lead to potential overlaps."}], "meta": {"exam": "C", "qnum": 57, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I configure a loopback interface with the IP address 172.16.15.12/32 using a script that complies with company security policies?"}, {"role": "assistant", "content": "To configure a loopback interface with the IP address 172.16.15.12/32, you need to use the `ietf-interfaces` YANG data model. The configuration must include the interface name \"Loopback0\", set its type to \"softwareLoopback\", enable it, and assign the IPv4 address \"172.16.15.12\" with a netmask of \"255.255.255.255\" to represent a /32 subnet. Additionally, the IPv6 address should be set to an empty object `{}` since no IPv6 address is specified. Option D correctly implements all these requirements."}], "meta": {"exam": "C", "qnum": 82, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How can I configure a loopback interface with the IP address 172.16.15.12/32 using a script that complies with company security policies?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - This option uses the correct IP but has an incorrect netmask of \"255.255.255.255\" instead of the required \"/32\" representation. B - This option uses the wrong namespace \"interface\" instead of \"ietf-interfaces:interface\". C - This option has an incorrect netmask of \"0.0.0.0\" which represents a /0 network, not a /32."}], "meta": {"exam": "C", "qnum": 82, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How should the architect configure the ISIS routing protocol to ensure a successful migration from IPv4 to IPv6 without causing traffic blackholes?"}, {"role": "assistant", "content": "To ensure a successful migration from IPv4 to IPv6 without causing traffic blackholes, the architect should first enable 'metric-style transition' on the core routers, C1 and C2. This configuration allows the ISIS protocol to support both narrow and wide metrics, ensuring compatibility with the existing IPv4 network while preparing for future IPv6 expansion. Additionally, the architect should enable 'multi-topology' under the IPv6 address-family on the edge routers, E1 and E2. This creates a separate IPv6 topology, allowing IPv6 traffic to be routed independently of IPv4, thus preventing any potential blackholes in the current IPv4 infrastructure."}], "meta": {"exam": "C", "qnum": 87, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "unjudged"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: How should the architect configure the ISIS routing protocol to ensure a successful migration from IPv4 to IPv6 without causing traffic blackholes?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - Enabling metric-style transition only on C1 and C2 is sufficient because they are the core routers handling the primary traffic between the headquarters and branches. B - Enabling metric-style transition on all routers is unnecessary and could lead to configuration conflicts since the edge routers do not need to handle both metric styles. C - Multi-topology enabled on E1 and E2 is incorrect because it should be enabled on the edge routers to create a separate IPv6 topology. D - Multi-topology enabled on C1 and C2 is incorrect because these are core routers and should not have multi-topology enabled under the IPv6 address-family. E - Metric-style transition enabled on E1 and E2 is incorrect because these are edge routers and do not require this feature as the core routers handle the transition."}], "meta": {"exam": "C", "qnum": 87, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What subnet mask should be used for the new New York branch to accommodate 1024 users without wasting IP addresses?"}, {"role": "assistant", "content": "To support 1024 users, we need at least 1024 usable IP addresses. The formula for usable hosts is 2^(32 - subnet_mask) - 2. For a /21 subnet, this is 2^11 - 2 = 2046 usable hosts, which is sufficient. A /22 provides only 510 usable hosts, which is too small. The available ranges are 192.168.0.0/20 (London) and 192.168.24.0/21 (Sydney). The range 192.168.16.0/21 (192.168.16.0 to 192.168.23.255) does not overlap with either existing subnet and provides enough addresses. Therefore, 192.168.16.0/21 is the optimal choice."}], "meta": {"exam": "C", "qnum": 88, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "quiz", "refined": true, "judge": "pass"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In this scenario: What subnet mask should be used for the new New York branch to accommodate 1024 users without wasting IP addresses?\nWhy are the other options wrong?"}, {"role": "assistant", "content": "A - 192.168.8.0/22 provides only 510 usable hosts, which is less than the required 1024. C - 192.168.8.0/21 overlaps with the London subnet (192.168.0.0/20). D - 192.168.16.0/22 provides only 510 usable hosts, which is insufficient for 1024 users."}], "meta": {"exam": "C", "qnum": 88, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "distractors", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How should I design QoS on the customer router for a 50-Mbps Layer 3 service that is handed off at 1 Gbps to keep voice traffic from becoming choppy?"}, {"role": "assistant", "content": "Use hierarchical QoS with a parent shaping policy set to the 50-Mbps CIR, and place voice in a child priority/LLQ class. The provider is likely policing at 50 Mbps, so sending at 1 Gbps can cause drops; a parent shaper smooths outbound traffic and buffers excess bursts, preventing policer drops that would otherwise damage voice quality."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Reducing the connection bandwidth to the router is not a valid rate-limiting design technique and does not enforce the 50-Mbps CIR. \nB - A parent policing policy drops excess traffic rather than smoothing it, which can still cause voice packet loss and choppy audio. \nD - The bandwidth statement is informational and affects routing metrics only; it does not shape or police traffic to the CIR."}, {"role": "user", "content": "If the customer later migrates part of this WAN edge to IPv6 and starts marking voice with DSCP EF in the IPv6 header, does the same 50-Mbps shaping and queuing design still hold, or do I need to change the QoS policy?"}, {"role": "assistant", "content": "The same design principle still holds: you must shape the customer router's egress toward the provider to the 50-Mbps CIR, because the 1-Gbps hand-off can otherwise burst far above the committed rate and cause the provider to drop or delay voice packets. What changes is that your classification and marking policy must match IPv6 traffic explicitly, since an IPv4-only ACL or class map will not see DSCP EF in the IPv6 header and voice may fall into a default class instead of the priority queue. You would typically create parallel or unified match statements that recognize IPv6 DSCP EF (and any signaling, such as SIP or RTP, that you rely on), then apply the same low-latency queuing or priority queue with a bandwidth guarantee sized for the expected number of concurrent calls. The shaper remains at 50 Mbps with a reasonable burst, and the scheduler still services EF before best-effort and other classes. If IPv4 and IPv6 voice coexist during migration, verify that both address families map to the same priority treatment and that the sum of priority traffic stays within the engineered limit."}], "meta": {"exam": "A", "qnum": 102, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We currently mark traffic with IP Precedence and want to migrate to DiffServ while keeping compatibility with those existing markings. What DiffServ mechanism should we include in the design?"}, {"role": "assistant", "content": "Use DiffServ class selector (CS) code points. They map directly to the legacy IP Precedence values, so existing precedence-based classifications remain compatible while the network moves to DSCP-based QoS."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Expedited forwarding provides low-latency treatment but does not provide IP Precedence backward compatibility.\nB - Assured forwarding defines classes and drop precedence but does not directly preserve legacy IP Precedence markings.\nD - Default per-hop behavior is best-effort treatment and does not provide the required legacy mapping."}, {"role": "user", "content": "If we later move some of these DSCP-marked flows onto an IPv6 core, how do we preserve the same backward compatibility with the legacy IP Precedence markings across that transition?"}, {"role": "assistant", "content": "In IPv6 you no longer mark precedence in the old ToS byte, but the Traffic Class field of the IPv6 header serves the same purpose, and class-selector codepoints are defined identically so that CS1 through CS7 line up one-to-one with IP Precedence values 1 through 7. That means as long as your DiffServ design includes class-selector PHBs, the same DSCP-to-precedence mapping you are relying on today carries cleanly into the IPv6 core without redefining policy. You should still verify that all routers, including any tunnel endpoints and MPLS-to-IPv6 edges, copy or map the Traffic Class consistently, since mishandled re-marking at a boundary can silently strip the legacy compatibility. Practically, keep your edge classification referencing CS codepoints (or AF/EF with CS fallback for legacy traffic) rather than raw precedence bits, so both IPv4 and IPv6 domains interpret the markings the same way. This also lets you retire IP Precedence signaling on hosts gradually while the network preserves equivalent PHB treatment for older devices."}], "meta": {"exam": "A", "qnum": 112, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Why does traffic drop when the primary HSRP switch recovers after a failure?"}, {"role": "assistant", "content": "When the primary HSRP switch comes back online, HSRP preemption immediately causes it to take over the virtual IP address. This triggers an immediate update of the MAC address tables on all downstream switches and end devices, leading to a brief period where frames are dropped because the new MAC-to-port mappings haven't been learned yet. The solution is to use the preempt delay feature on the primary HSRP device, which adds a configurable delay before it reclaims its priority. This gives the network time to stabilize and ensures a smoother transition, preventing the disruptive MAC address flapping and traffic drops."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Increasing the hello timers only affects how frequently HSRP messages are sent, not the timing of the failover process itself. C - Using preempt delay on the backup device would delay its takeover, which is not relevant to the primary's recovery issue. D - Configuring a higher mac-refresh interval affects how often the switch refreshes its own MAC table, but it doesn't address the core problem of MAC flapping during a primary switch recovery."}, {"role": "user", "content": "Would the same traffic drop happen if we used VRRP instead of HSRP, and does using IPv6 change anything about how we'd fix it?"}, {"role": "assistant", "content": "Yes, the same fundamental problem exists with VRRP, because VRRP also relies on a virtual MAC address and gratuitous ARP/ND behavior when a higher-priority master preempts, so downstream devices and the upstream routing domain can briefly hold stale forwarding information. The root cause in this design isn't HSRP-specific — it's that the distribution switch is the Layer 3 boundary, so when the primary comes back it must re-converge routing adjacencies, rebuild its FIB/ARP/ND caches, and reassert itself as the active gateway before it can forward traffic correctly. With IPv6, the equivalent mechanisms are Neighbor Discovery and Router Advertisements rather than ARP, and the same preemption race applies: the returning device advertises itself as the default gateway while its own control-plane and forwarding state are still stabilizing. The practical fix is the same in either protocol family: add a delay before preemption so the recovering switch only takes over after its routing protocol adjacencies, FIB, and neighbor tables are fully populated — for example, HSRP's `preempt delay minimum` or `preempt delay reload`, and the VRRP/VRRPv3 equivalent preempt delay. So the protocol choice (HSRP vs VRRP) and IP version (IPv4 vs IPv6) change the signaling details but not the design remedy: you must prevent the gateway role from being reclaimed until the Layer 3 boundary device is actually ready to forward."}], "meta": {"exam": "A", "qnum": 119, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a multivendor PIM-SM network, I need all routers to learn RP information automatically and I cannot rely on Cisco-proprietary discovery, so which RP deployment method should I use?"}, {"role": "assistant", "content": "Use bootstrap router (BSR). BSR is standards-based and dynamically distributes group-to-RP mappings through bootstrap messages, allowing PIM routers to discover the RP set automatically. Auto-RP is dynamic but Cisco proprietary, static RP requires manual configuration, and Anycast-RP provides redundancy but not dynamic RP discovery on its own."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Auto-RP supports dynamic RP discovery, but it is a Cisco-proprietary mechanism rather than a standards-based one.\nB - Anycast-RP is standards-based for RP redundancy, but it does not itself provide dynamic RP discovery.\nD - Static RP requires manual RP configuration on routers and does not support dynamic RP discovery."}, {"role": "user", "content": "If I use BSR in a large multivendor PIM-SM domain but want to migrate toward IPv6 and PIM-SMv6 later, does BSR still work as my standards-based dynamic RP discovery method, or do I need a different approach?"}, {"role": "assistant", "content": "Yes, BSR remains the standards-based dynamic RP discovery mechanism you want, because it is defined generically for PIM-SM and has an IPv6 counterpart in PIM-SMv6 rather than being tied to Cisco-proprietary Auto-RP. In an IPv6 or dual-stack deployment, you would run BSR scoped to the IPv6 PIM domain using IPv6 transport and IPv6 group ranges, just as you scope BSR for IPv4 today, so the operational model carries over cleanly. The key design point is that RP-to-group mappings, BSR candidate RP advertisements, and bootstrap router election must be kept within the correct address-family domain so IPv4 and IPv6 multicast topologies do not accidentally leak RP state into each other. Auto-RP is not the right migration answer here because it is Cisco-proprietary and IPv4-oriented, which violates your multivendor and future IPv6 requirements. If you later move to a more advanced architecture, you could also consider standards-based MSDP/Anycast-RP designs, but for pure dynamic RP discovery in PIM-SM and PIM-SMv6, BSR is still the correct standards-based choice."}], "meta": {"exam": "A", "qnum": 126, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We are designing management access for our campus and WAN routers. Should we use in-band management over the production links or build a separate out-of-band management network, and what is the main operational benefit?"}, {"role": "assistant", "content": "Go with out-of-band management because it preserves administrative access during a production network outage. Recommend a dedicated management path (console/terminal server or separate management network) so that if production routing, switching, or links fail, you can still reach devices to troubleshoot and recover them. That management survivability under failure is the key advantage, and it also isolates management traffic from user traffic for better security."}, {"role": "user", "content": "If we build the out-of-band network but it shares fate with production through the same physical conduit, power feed, or WAN carrier, does it still deliver its main benefit — and how do we avoid that single point of failure?"}, {"role": "assistant", "content": "The core benefit of out-of-band management is management reachability independent of the production data plane, so if the OOB path shares the same conduit, power feed, or carrier as the production links, you have recreated the failure domain you were trying to escape and the benefit largely evaporates. To preserve independence, run OOB circuits over diverse physical paths (separate conduit, different entry points, ideally different carriers), feed OOB devices from separate power sources or UPS/PDU branches, and terminate them on dedicated management interfaces or console servers rather than the production uplinks. For WAN routers, that often means a second low-bandwidth circuit, cellular/LTE backup, or dial/console access via a terminal server, so a fiber cut, carrier outage, or power event on the production side does not blind you. At larger scale, document and test the OOB topology against the same failure scenarios you use for production — link down, device reload, routing reconvergence — to confirm you can still reach and recover devices when everything else is degraded. In short, OOB is only as valuable as its diversity: same-path OOB is a checkbox, truly separate-path OOB is the operational lifeline."}], "meta": {"exam": "A", "qnum": 14, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m documenting Cisco SD-WAN control-plane behavior: what route types does OMP advertise between the controllers and WAN Edge routers?"}, {"role": "assistant", "content": "Cisco SD-WAN OMP advertises prefix routes, TLOC routes, and service routes. Prefix routes carry VPN/prefix reachability, TLOC routes identify transport locators and tunnel endpoints, and service routes support service-side reachability and service insertion."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Underlay, MPLS, and overlay are network layers or transport types"}, {"role": "user", "content": "How does OMP handle IPv6 overlay routes in an SD-WAN deployment, and what changes when vEdge and cEdge routers coexist in the same fabric?"}, {"role": "assistant", "content": "OMP is transport-agnostic and carries IPv6 prefixes inside its own TLVs just as it carries IPv4, so an IPv6 overlay route is advertised between controllers and WAN Edge routers the same way an IPv4 route is, using the OMP route attribute set (TLOC, origin, originator, preference, service, site-id, label, and so on). On the WAN Edge side, you enable IPv6 on the VPN/VRF interface and configure an IPv6 OMP address family on the control connection, and the vManage/vBond/vSmart controllers will reflect those IPv6 routes across the overlay without needing an IPv6 underlay—the transport TLOC itself can still be IPv4. In mixed vEdge (Viptela OS) and cEdge (IOS-XE SD-WAN) fabrics, both platforms speak the same OMP and can exchange IPv4 and IPv6 routes, but you must ensure the cEdge is running a release that supports the relevant OMP address family and that the overlay management tunnel (DTLS/TLS) is up on both, since OMP rides that control connection. A common design variation is to run an IPv6-only data plane with an IPv4 TLOC underlay, or dual-stack, and OMP will advertise the IPv6 service-side prefixes with the appropriate VPN-ID and TLOC so remote sites can resolve reachability. Failure modes worth noting: if the OMP control connection drops, all learned IPv6 (and IPv4) routes from that peer are withdrawn after the hold timer, and if you forget to enable the IPv6 address family on either peer, the routes simply won’t be exchanged even though the tunnel is up—so verify with `show o"}], "meta": {"exam": "A", "qnum": 22, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In NETCONF, how can I subscribe to notifications for my session and apply an event filter so I only receive the notifications I care about?"}, {"role": "assistant", "content": "Use the `<create-subscription>` operation with the optional `<filter>` parameter. It creates the notification subscription and scopes the filter to that session, so only matching notifications are sent to the requesting client; this is why it is the correct operation for session-specific notification filtering."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "B - `<commit>` commits a candidate configuration to the running"}, {"role": "user", "content": "If I'm running NETCONF over SSH with a large number of sessions and only want notifications tied to my own session, does the `create-subscription` filter approach still scale, or should I be looking at a different mechanism like NETCONF notifications over TLS or a separate notification receiver?"}, {"role": "assistant", "content": "The `create-subscription` operation with a session-specific filter still works at scale because the filtering is applied per-session at the NETCONF server, so each subscriber only receives the notification stream matching its own criteria rather than a shared broadcast feed. The operation itself (typically `<create-subscription>` within the notifications capability) establishes that filter for the session, and the server tags and sends only matching events down that session's SSH channel. Switching to NETCONF over TLS doesn't change the filtering semantics—it just changes the transport security layer—so it won't give you better filtering, only different transport characteristics. If your concern is fan-out to many sessions, the more relevant levers are server-side CPU/memory for filter evaluation and the number of concurrent SSH sessions the device supports, not the subscription operation itself. A separate notification receiver (a collector system subscribing once and redistributing) is a common scaling pattern when you have hundreds of sessions, because it centralizes filter logic and reduces per-device subscription overhead. So for correctness the session-filtered `create-subscription` is still the right answer; for very large scale, pair it with a collector or confirm the device's session and notification throughput limits."}], "meta": {"exam": "A", "qnum": 3, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We need to connect two sites over the public Internet and securely pass multicast traffic, including routing protocol updates, between them. What tunneling design should I use?"}, {"role": "assistant", "content": "Use GRE over IPsec. GRE encapsulates the multicast and routing-protocol packets so they can traverse the public network, and IPsec protects the GRE tunnel with encryption and authentication; plain IPsec will not carry multicast natively, and plain GRE is not secure."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - IPsec alone does not natively support multicast traffic, so it cannot securely tunnel the required multicast flows by itself. \nB - GRE supports multicast and routing protocols, but without IPsec it does not provide the required security over a public network. \nC - PPTP is an obsolete point-to-point tunneling protocol that does not support multicast routing or modern secure site-to-site design requirements."}, {"role": "user", "content": "If I use DMVPN with IPsec for this design, can I also run it over IPv6 transport for the public underlay, and how would multicast and routing protocol updates behave in that IPv6-based DMVPN while still carrying IPv4 multicast traffic between the sites?"}, {"role": "assistant", "content": "Yes, DMVPN can be deployed over an IPv6 public underlay, but the design must distinguish between the transport family used for tunnel endpoints and the payload family carried inside the tunnel; typically you would use DMVPNv6 for IPv6 overlay transport or run mGRE/IPsec over IPv6 while still carrying IPv4 multicast inside if the platform supports it. In classic DMVPN Phase 3 with mGRE, multicast is enabled on the tunnel interface and the routing protocol, such as OSPF or EIGRP, forms neighbor adjacencies across the hub-and-spoke or spoke-to-spoke topology, with the hub often acting as the multicast replication point for the spokes. If the underlay is IPv6 but the multicast routing updates are IPv4, the tunnel must be dual-stack or you need separate overlays, because the outer IPv6 headers do not carry the inner IPv4 multicast semantics by themselves. For scale, keep in mind that DMVPN over IPv6 may have feature and platform caveats, especially around NHRP, IPsec, and multicast replication, so validate that your IOS-XE or ISR/ASR code supports the exact combination. As a failure-mode consideration, if NHRP or the IPsec overlay breaks, multicast routing adjacencies over the tunnel will drop even though the underlying IPv6 public path may still be reachable, so monitor both the underlay and the overlay."}], "meta": {"exam": "A", "qnum": 39, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I am designing a multivendor campus LAN that uses Spanning Tree for Layer 2 loop prevention. I need to group all VLANs into two Spanning Tree instances. Which standards-based Spanning Tree technology should I use?"}, {"role": "assistant", "content": "Use MSTP. MSTP is standards-based and lets you map groups of VLANs into a small number of Spanning Tree Instances, so two instances can be configured across multivendor switches. It provides loop prevention and allows different VLAN groups to use different forwarding topologies without requiring a separate STP instance per VLAN."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "B - RSTP is standards-based but provides only a single spanning-tree topology and does not support VLAN-to-instance grouping.\nC - Rapid PVST is Cisco-proprietary and creates one instance per VLAN, so it is not the standards-based two-instance design requested.\nD - STP is standards-based but legacy and single-instance, with no support for grouping VLANs into separate Spanning Tree Instances."}, {"role": "user", "content": "If I use MSTP across this multivendor campus but one switch only supports a single spanning-tree instance, how can I still group VLANs into two instances without creating loops, and what happens during a topology change?"}, {"role": "assistant", "content": "With standards-based MSTP (IEEE 802.1s), the clean design is to define two MST instances (for example, MSTI 1 and MSTI 2) plus the common and internal spanning tree (CIST/MSTI 0), and map each VLAN to the appropriate instance; the single-instance switch cannot participate in separate per-instance topologies, so it will effectively be limited to the CIST behavior for the VLANs it carries. To avoid loops, you must keep that device in a part of the topology where it does not need to make independent forwarding decisions for the two instances—typically by placing it at an edge/access layer, limiting its VLANs, and ensuring the distribution/core layer provides the per-instance forwarding and blocking decisions. A common approach is to run MSTP on the switches that support it, while treating the single-instance switch as a boundary device: its uplinks should be designed so that all its VLANs share the same active/blocked path, and you should avoid designs where one VLAN needs to be active on one link while another VLAN needs to be blocked on that same link through that switch. During a topology change, MSTP will reconverge the affected MST instance(s), and the single-instance device will follow CIST-style reconvergence for its VLANs; this can cause temporary flooding or suboptimal forwarding if the single-instance switch is in a transit path, so best practice is to keep it out of the core/transit role and use root guard, BPDU guard, and consistent MST region configuration on the st"}], "meta": {"exam": "A", "qnum": 45, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I’m using NETCONF against Cisco NX-OS devices and need to configure a feature that is specific to NX-OS and not standardized. Which YANG model family should I use?"}, {"role": "assistant", "content": "Use the Cisco NX-OS native YANG model. Native models are vendor-specific and expose NX-OS-only features, while IETF, IEEE, and OpenConfig models are standards-based"}, {"role": "user", "content": "If the NX-OS-specific feature I need is only supported in a Cisco native YANG model, how should I design the NETCONF workflow when I also need some standard IETF interface configuration on the same device?"}, {"role": "assistant", "content": "Use a hybrid model strategy: apply the Cisco native NX-OS YANG model for the vendor-specific feature, and use standard IETF YANG models for the standardized interface configuration that NX-OS supports. In NETCONF, this normally means sending separate `<edit-config>` operations, or one carefully constructed `<edit-config>` with multiple top-level data trees, targeting the appropriate model namespaces and datastores. Keep the vendor-specific configuration in its native namespace and avoid trying to force it into an IETF model, because that breaks model validation and future portability. Validate each change independently with `<get-config>` or `<get>` filters so you can confirm that both the native and standard branches were accepted. If the device supports candidate datastore, commit the combined change atomically; otherwise, sequence and verify the edits to avoid partial configuration during coexistence."}], "meta": {"exam": "A", "qnum": 50, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "When Cisco Express Forwarding forwards traffic to a next hop, which OSI layer’s addressing information does the adjacency table populate for the rewrite?"}, {"role": "assistant", "content": "The adjacency table populates Layer 2 addressing information. CEF separates control-plane and data-plane functions: the FIB contains Layer 3 prefix reachability, while the adjacency table holds the Layer 2 next-hop rewrite details, such as the destination MAC address. ARP or IPv6 neighbor discovery populates those adjacencies, allowing CEF to encapsulate frames without per-packet recursive lookups."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Layer 4 is above the forwarding rewrite path and deals with transport-layer identifiers, not CEF adjacency addressing.\nC - Layer 1 covers physical signaling and media characteristics, not the addressing information stored in CEF adjacencies.\nD - Layer 3 is represented primarily by the CEF FIB for prefix reachability, while the adjacency table supplies the Layer 2 rewrite."}, {"role": "user", "content": "Since CEF builds the adjacency table using Layer 2 rewrite information, how does this work differently when the next hop is over a multi-access segment like Ethernet versus a point-to-point link, and what happens if the adjacency entry becomes stale or the ARP/ND entry expires?"}, {"role": "assistant", "content": "On a point-to-point link, CEF can populate the adjacency table immediately and deterministically because there is only one possible Layer 2 destination, so the rewrite information (for example, the destination MAC for HDLC, PPP, or a point-to-point Ethernet subinterface) is known without any address resolution. On a multi-access segment like Ethernet, CEF must rely on ARP for IPv4 or Neighbor Discovery for IPv6 to learn the mapping between the next-hop IP and the destination MAC, and only then can it install a complete adjacency entry with the correct rewrite string. If the ARP or ND entry expires or is invalidated, CEF marks the corresponding adjacency as incomplete or drops it from the forwarding path, which causes packets to be punted to the control plane or dropped until resolution completes. This is why maintaining a healthy ARP/ND cache and avoiding excessive adjacency churn is important for CEF performance, especially at scale where thousands of adjacencies may need to be refreshed. In failure scenarios, such as a next-hop becoming unreachable, CEF will typically remove or invalidate the adjacency, and the route may be withdrawn or reconverged depending on the routing protocol and FIB state."}], "meta": {"exam": "A", "qnum": 75, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-WAN design, what techniques should I use in the overlay to make business-critical voice and video applications perform better when WAN links experience packet loss and congestion?\n\nASSISTANT_QU"}, {"role": "assistant", "content": "FEC improves application experience by adding redundant/parity packets so that packet loss on a WAN link can be reconstructed without retransmission, which helps real-time and interactive applications. QoS improves application experience by classifying, marking, queuing, scheduling, and shaping traffic so business-critical applications receive the latency, jitter, and loss treatment they require across the SD-WAN overlay. In Cisco SD-WAN design, FEC and QoS are directly part of the application-experience/performance toolset alongside application-aware routing, packet duplication, and TCP optimization. B, C, and E are security-related controls, not direct application-performance techniques."}, {"role": "user", "content": "If I'm running voice and video over an SD-WAN fabric that also carries IPv6 traffic and I can't enable full application-aware routing on every edge due to scale, what can I still do at the overlay level to protect those real-time flows when links degrade?"}, {"role": "assistant", "content": "Even without full app-aware routing everywhere, you can still apply the same SD-WAN overlay techniques that answer the original question—specifically Forward Error Correction (FEC) and packet duplication—because both work on the data plane and don't require every edge to classify applications deeply. FEC adds redundant packets so the receiving edge can reconstruct lost voice/video packets without retransmission, while packet duplication sends copies of the same real-time flow over two different WAN transports and discards duplicates at the far end, which is very effective for lossy or congested links. For IPv6 traffic, the key is to ensure these techniques are enabled on the service-side VPN and that the WAN transports carry IPv6 (or use IPv6 over the overlay) so the redundant copies have two independent paths. At scale, you can use centralized policy templates to apply FEC and duplication only to the business-critical voice/video prefixes or DSCP markings, rather than per-application DPI on every edge. You should also combine this with per-tunnel QoS and a strict priority queue for real-time traffic so congestion doesn't reorder or drop the duplicated/FEC-protected packets. Finally, monitor the SLA probes for both IPv4 and IPv6 paths and define a fallback policy so that if one transport degrades, the overlay still steers the protected flows over the better path."}], "meta": {"exam": "A", "qnum": 88, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can the client's internal network ensure all devices can reach the Internet through ISP1?"}, {"role": "assistant", "content": "To achieve this, the edge routers connecting to ISP1 (Edge Router A in this case) must inform the rest of the client's network about how to get to the Internet. The simplest and most effective method is to configure these edge routers to advertise a default route (0.0.0.0/0) into the client's internal routing domain. This allows every downstream router in the client's network to learn that any destination outside their own network should be forwarded to the edge router. When a device on the client network wants to access the Internet, its traffic is sent to the nearest downstream router, which then forwards it to the edge router. The edge router then sends the traffic to ISP1, completing the connection. This approach is scalable and does not require the client to maintain complex routing tables for the entire Internet."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Running eBGP sessions in different VRFs would isolate the routing tables for each ISP, but it doesn't directly enable Internet connectivity from the client's internal network.\nC - Applying AS-path prepend is a technique to influence inbound traffic from ISP2, not to enable outbound traffic to the Internet via ISP1.\nD - Route filtering ensures the client only advertises its own routes, which is important for security and policy, but it does not create the necessary path for the client's network to reach the Internet."}, {"role": "user", "content": "If the client later adds a third ISP for Internet access and wants traffic to fail over between ISP1 and ISP3 automatically when one path degrades, how should the BGP design change to preserve the ISP2 third-party peering while still preferring ISP1 as primary?"}, {"role": "assistant", "content": "Keep the ISP2 peering strictly for the third-party routes by applying inbound and outbound route filters or community tags so those prefixes never become candidates for the default Internet path. For Internet reachability, originate or receive a default route from both ISP1 and ISP3 and influence selection with LOCAL_PREF (higher on ISP1 for primary) plus AS-path prepending on ISP3 so it only wins when ISP1 is withdrawn. Add failure detection such as BFD or tuned BGP timers on the ISP1 and ISP3 sessions so degraded links are detected quickly and the backup default route is installed without waiting for the full hold timer. Preserve determinism by tagging ISP1 and ISP3 default routes with distinct communities and using route-maps to set LOCAL_PREF conditionally, rather than relying on MED, which only compares paths from the same neighboring AS. Finally, verify with `show ip bgp` and `show ip bgp summary` that ISP2-learned prefixes never appear as the best path to 0.0.0.0/0 and that ISP3 only becomes active on ISP1 failure or severe degradation."}], "meta": {"exam": "A", "qnum": 99, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have teams in multiple branches that need to communicate with each other and reach enterprise applications in our data center and in the cloud. Guests at those branches must get internet-only access, and our internet gateway is in the data center. What WAN design should I use to keep guest traffic isolated while still supporting corporate access?"}, {"role": "assistant", "content": "Use an MPLS Layer 3 VPN with one corporate VRF and one guest VRF. The corporate VRF carries branch, data center, and cloud routes using MP-BGP/route targets; the guest VRF is isolated and sends guest traffic back to the data center gateway, where a default route provides internet-only access. This gives the required segmentation without needing a separate VRF per branch."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Using a different service provider for guests adds unnecessary cost and complexity and does not integrate cleanly with the centralized data center internet gateway.\nB - A data center firewall filtering guest traffic is useful but by itself does not provide the WAN segmentation and guest backhaul path needed from the branches.\nD - A separate VRF for each branch is operationally heavier than required and does not specifically solve the guest isolation and internet-only requirement."}, {"role": "user", "content": "If we later migrate part of this design to IPv6 and need the same guest internet-only isolation, does the WAN architecture change, or is it mostly an addressing and policy variation?"}, {"role": "assistant", "content": "The WAN architecture does not fundamentally change for IPv6; it is primarily an addressing, routing, and policy extension of the same design. Corporate IPv6 prefixes can be advertised across the WAN using the same routing protocol you already use, such as OSPFv3, EIGRP for IPv6, or MP-BGP if you are running MPLS or a provider-managed Layer 3 VPN. Guest isolation still needs to be enforced at the branch with separate VRFs, VLANs, or firewall zones, and IPv6 guest traffic should be routed toward the data center internet gateway rather than directly to the internet. You also need IPv6-aware security and NAT policy where required, including IPv6 ACLs, firewall rules, and possibly NAT66 or provider NAT if public IPv6 addressing is not available. For coexistence, the cleanest approach is dual-stack at the branch and data center, with corporate and guest VRFs carrying both IPv4 and IPv6 so isolation behavior remains consistent. The main failure mode to watch is leaking guest IPv6 routes into the corporate routing table, so route-target, VRF, and redistribution policies must be carefully controlled."}], "meta": {"exam": "B", "qnum": 106, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I'm designing a new SD-WAN architecture and want to align with Cisco's \"reinventing the WAN\" framework. What are the"}, {"role": "assistant", "content": "Cisco's \"reinventing the WAN\" framework for the CCNP ENSLD exam centers on three design pillars: Secure Elastic Connectivity, Application Quality of Experience, and Cloud First. Secure Elastic Connectivity uses an encrypted overlay (e.g., IPsec, DTLS) over any transport (MPLS, broadband, LTE/5G) to provide transport independence, dynamic path selection, and zero-trust segmentation. Application Quality of Experience applies application-aware routing, SLA-based policies, and per-application QoS to meet business intent across the SD-WAN fabric. Cloud First design optimizes direct access to SaaS/IaaS (e.g., Office 365, AWS) using local internet breakout and cloud on-ramps, avoiding backhaul through a centralized data center."}, {"role": "user", "content": "If I’m extending an existing MPLS WAN to a Cisco SD-WAN design rather than building greenfield, how should I map the three “reinventing the WAN” focus areas to a coexistence migration, especially if I also need IPv6 and some traffic must stay on MPLS for compliance?"}, {"role": "assistant", "content": "Map the three focus areas—Connectivity, Deployment, and Experience—to the coexistence design rather than treating them as greenfield-only goals. For Connectivity, use SD-WAN fabric overlays over hybrid underlays so existing MPLS circuits, internet broadband, and 5G/LTE can all participate, with application-aware policies steering compliant traffic over MPLS and less-sensitive traffic over lower-cost paths. For Deployment, take advantage of zero-touch provisioning, templates, and centralized policy so branch devices can be brought into the SD-WAN overlay gradually while legacy MPLS sites remain reachable through the VPN fabric. For Experience, apply analytics, SLA-based path selection, and QoS across both underlays so users get consistent performance even during migration. With IPv6, run dual-stack or IPv6-only overlay transport where supported, and ensure the SD-WAN controllers, WAN Edge devices, and routing policies are consistently configured for IPv6 reachability and security. In failure scenarios, design deterministic fallback—such as MPLS primary with internet secondary, or vice versa—and validate that compliance-bound traffic still follows the approved path when an underlay degrades."}], "meta": {"exam": "B", "qnum": 117, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "During the discovery phase of a Cisco enterprise network design engagement, what should the solutions engineer focus on before moving into architecture and solution mapping?"}, {"role": "assistant", "content": "Focus on gathering information about the customer’s current network environment and establishing credibility with the customer. Discovery is about understanding the current state, requirements, constraints, and business drivers while building trust; architecture development, Cisco capability mapping, and lifecycle-model discussions come later once the requirements are understood."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "B - Developing a reference architecture is a design/planning activity that occurs after discovery requirements are known.\nC - Mapping Cisco innovation to customer needs is solution positioning or design work, not initial discovery.\nD - PPDIOO is a lifecycle methodology that can guide the engagement, but merely referencing it is not a discovery activity."}, {"role": "user", "content": "If this discovery process is happening in a large multi-site enterprise that runs OSPF and is now planning IPv6 coexistence, how should the SE’s discovery priorities change before moving into architecture and solution mapping?"}, {"role": "assistant", "content": "In that scaled, dual-stack context, the SE should still keep discovery focused on business and technical requirements first, but expand the technical discovery to include IPv6 coexistence readiness such as current OSPF areas, router platform capabilities, addressing standards, and whether the design will use OSPFv3, dual-stack OSPFv2/v3, or another transition approach. The SE should also inventory existing IPv4 dependencies, including QoS, ACLs, WAN edge policies, DNS/DHCP, and management tools, because these often need parallel IPv6 treatment before architecture decisions are made. For a multi-site enterprise, discovery must clarify site profiles, traffic flows, redundancy requirements, and migration constraints per site rather than assuming a single uniform rollout. The SE should identify operational constraints too, such as change windows, skills gaps, and monitoring readiness, since IPv6 coexistence can fail not only because of routing protocol choice but because operations and security processes were not adapted. Only after these discovery findings are documented should the SE move into architecture and solution mapping, where OSPFv3 design, dual-stack addressing, and phased coexistence can be matched to validated requirements."}], "meta": {"exam": "B", "qnum": 127, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We run HSRP between two core routers, and after growth some downstream links are nearly saturated while others are lightly used. What design change will balance traffic across both routers without adding hardware?"}, {"role": "assistant", "content": "Use multiple HSRP groups and make each core router active for a different set of VLANs. Configure R1 with higher priority for some VLANs and R2 with higher priority for the remaining VLANs, so downstream VLANs use both active gateways and both sets of links. This distributes traffic across the core routers and their downstream interfaces instead of leaving one router as the active forwarder for every VLAN."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "B - Adding more interfaces can add raw capacity, but it does not fix the HSRP active/standby imbalance that leaves some links underused.\nC - A port channel toward downstream switches increases bandwidth on a specific link bundle, but traffic may still be pinned through the single HSRP active router.\nD - Enabling RSTP affects Layer 2 loop prevention and topology convergence, not HSRP first-hop load distribution or core link utilization."}, {"role": "user", "content": "If the two core routers are already running HSRP for IPv4 and we need to add IPv6 rather than replace HSRP, what is the equivalent design for IPv6, and can HSRP and its IPv6 counterpart coexist on the same routers without causing a new imbalance?\n\n##"}, {"role": "assistant", "content": "For IPv6, the direct equivalent is HSRP version 2, which supports IPv6 as well as IPv4 and is generally the preferred choice because a single HSRPv2 group can carry both address families while still using a virtual MAC and active/standby election. You could also use GLBP for IPv6, but since the original goal was to balance downstream traffic across both core routers without adding hardware, HSRPv2 alone still leaves one router active per group unless you create multiple groups with different active routers and tune the downstream gateway or HSRP priority per VLAN or subnet. HSRPv2 and an IPv6 first-hop redundancy method can coexist cleanly because they are separate protocol instances and address families, but from the traffic perspective they do not automatically fix imbalance: you must deliberately distribute the active role across groups, for example Router A active for some VLANs and Router B active for others, and then mirror that split for IPv6. A common failure-mode concern is that if both IPv4 and IPv6 active roles land on the same router for the same downstream segment, that router becomes the hot spot for both protocols, so align the per-group active/standby design across address families. Also remember that HSRPv2 uses a different virtual MAC range and multicast address than HSRPv1, so verify downstream devices and any first-hop security features support it before rolling it out."}], "meta": {"exam": "B", "qnum": 19, "topic": "", "has_exhibit": true, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "We have a 1 Gbps ISP link with a 100 Mbps CIR, and the ISP drops everything above the CIR, causing TCP retransmissions. We don’t run voice or RTP, but we want to use as much of the CIR as possible. What QoS design should we use on our side?"}, {"role": "assistant", "content": "Use traffic shaping toward the ISP. Shape the outbound traffic to the 100 Mbps CIR, ideally with a small burst allowance, so excess packets are buffered and paced instead of dropped by the ISP. Since there are no RTP applications, the shaping delay is acceptable, and this reduces TCP retransmissions while keeping utilization up to the CIR."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Policing drops or remarks traffic that exceeds the rate, which can increase TCP retransmissions and does not smooth traffic to the ISP CIR.\nB - Queuing only provides scheduling during congestion and does not by itself enforce the 100 Mbps CIR on a 1 Gbps link.\nD - A policer with markdown still allows excess traffic to be sent toward the ISP, so the ISP may aggressively drop it and cause retransmissions."}, {"role": "user", "content": "If we later add IPv6 and multicast video on the same 100 Mbps CIR, do we still just shape to the CIR, or do we need a different QoS design on the customer side?"}, {"role": "assistant", "content": "You still want to shape the aggregate outbound rate to the 100 Mbps CIR, because the ISP’s policer is dropping anything above that rate regardless of whether the traffic is IPv4, IPv6, unicast, or multicast. The key variation is that QoS classification and marking must be updated to recognize IPv6 headers and multicast video flows, since ACLs, NBAR, and class maps that only match IPv4 will miss them. In most designs, the multicast video should get a priority or guaranteed-bandwidth class if it is real-time, while the remaining bandwidth is shared by TCP and other best-effort traffic using a fair-queue or shaping-plus-HQF approach. If the video is not RTP-based or is non-real-time, you may not need low-latency queuing, but you should still protect it from being starved by bulk TCP. The failure mode to watch is that added multicast or IPv6 traffic can consume the shaped CIR and cause drops for other applications, so the shaper should be paired with a hierarchical policy that enforces both the overall CIR and per-class treatment."}], "meta": {"exam": "B", "qnum": 29, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can an architect ensure that an EIGRP network remains stable and efficient when connecting to external networks via BGP?"}, {"role": "assistant", "content": "In this scenario, the architect should implement route summarization and stub routing. Route summarization is critical because it reduces the number of individual routes that need to be advertised and processed, conserving bandwidth, memory, and CPU resources across the network. This is particularly important given the multiple subnets within each AS. Stub routing is equally important as it configures edge routers to only accept default routes or specific summaries from their neighbors, preventing them from becoming intermediate routers for traffic they are not designed to handle. This eliminates the risk of suboptimal paths and significantly reduces the number of EIGRP queries initiated by the network, enhancing overall stability and scalability."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Route summarization is effective but alone doesn't address the issue of unnecessary queries.\nB - Prefix lists are useful for filtering traffic but do not directly conserve resources or prevent queries.\nC - Distribute lists filter routing updates but can lead to inconsistent routing information and don't fully address the query problem.\nE - Static redistribution is not scalable and requires manual configuration for every route, increasing administrative overhead and potential for errors."}, {"role": "user", "content": "If the edge is running BGP into EIGRP with a single exit point per site instead of dual-homed remotes, does the AD solution still hold, or would I be better off using stub routing and a default route toward the core?"}, {"role": "assistant", "content": "With a single exit point per site, the suboptimal routing and unnecessary query concerns that drove the original AD answer largely disappear, because there is no alternate path that could be chosen incorrectly. Stub routing becomes very attractive here: marking the remote as `eigrp stub` (ideally `stub connected summary` or `stub redistributed`) advertises only the routes it owns and stops the hub from querying it for anything else, which directly conserves bandwidth, memory, and CPU. A default route (or summary) injected from the core toward the stub further shrinks the topology table the remote must hold, and since the remote has only one way out, no suboptimal path can exist. The AD mechanism from the original design is mainly justified when multiple redistribution points or dual-homed remotes create loops or ambiguous next-hops; in a hub-and-spoke with a single BGP exit per site, stub plus summary/default is cleaner and more scalable. In short, the AD solution is not wrong, but for a single-exit topology the stub-and-default approach is the more efficient design choice and you can layer AD on later if the topology grows dual-homed."}], "meta": {"exam": "B", "qnum": 4, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What configuration change should be made to the routers to prevent future outages caused by a link failure?"}, {"role": "assistant", "content": "The diagram shows a network where R1 and R2 are L1/L2 routers forming the backbone, but R3 is configured as an L1 router. This means R3 can only route within its local area and cannot forward traffic between different areas, leading to a potential break in connectivity if the direct link fails. Since the backbone requires all routers to be capable of inter-area communication, R3 must be changed from an L1 router to an L1/L2 router. This allows R3 to participate in the L2 backbone, enabling it to forward packets between areas and ensuring that the network remains connected even if a single link fails."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Making R3 an L1L2 router ensures it can forward traffic across areas and maintain network continuity. \nB - Making R31 an L1 router would further isolate it from the backbone and worsen the problem. \nC - Making Area 0 L2-only is not a valid configuration option because Area 0 is the backbone, and it must be L2-only by definition, but this doesn't address the specific issue with R3's role. \nD - Making R11 an L2 router does not solve the root cause, which is the misconfiguration of R3 as an L1 router in the backbone."}, {"role": "user", "content": "If the customer later migrates this same R1–R2 topology to IPv6 and wants the same link-failure continuity, how does the design change — do I still get an equivalent protection mechanism, and does it need to coexist with the existing IPv4 setup?"}, {"role": "assistant", "content": "Yes — the same continuity goal is met on IPv6 with the IPv6 counterpart of the IPv4 first-hop/protocol-protection design, most commonly using HSRPv6 or VRRPv3 for gateway redundancy plus an IPv6-capable routing protocol such as OSPFv3 or EIGRP for IPv6 to reconverge around the failed R1–R2 link. If the original solution relied on a floating static route with object tracking, the IPv6 design mirrors that with an IPv6 static route (::/0) tied to an IPv6 tracking object, so the backup path is installed only when the primary link’s reachability fails. Coexistence is straightforward because IPv4 and IPv6 run as independent protocol instances on the same interfaces — you simply enable IPv6 unicast routing, configure addressing, and apply the redundant gateway/route-tracking logic in parallel without disturbing the working IPv4 configuration. The key design caveat is consistency of the failure domain: tracking must reference the same physical or logical interface (or a reachability probe) that represents the R1–R2 link, otherwise IPv6 failover and IPv4 failover could trigger at different times and cause asymmetric or black-holed traffic. Finally, verify that the chosen IPv6 FHRP supports the needed preemption and authentication features, since HSRPv6/VRRPv3 capabilities differ slightly from their IPv4 versions."}], "meta": {"exam": "B", "qnum": 49, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Our cloud-based voice, video, file-sharing, content-sharing, and messaging applications intermittently become slow during business hours, but other applications work fine with our current QoS policies. How should we design QoS to fix this?"}, {"role": "assistant", "content": "Use NBAR2 to identify the cloud applications and then update the QoS policy to allocate the required bandwidth to those application classes. NBAR2 gives accurate application classification even when cloud apps use dynamic ports or HTTPS, which allows the QoS design to treat the actual business-critical traffic instead of relying on static ports that may be wrong or incomplete."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "B - Static port-based classification is unreliable for cloud applications that use dynamic ports, HTTPS, or encrypted flows.\nC - Reserving bandwidth only on perimeter routers does not guarantee proper classification and queuing along the full path or at the actual congestion point.\nD - Rate-limiting caps bandwidth but does not provide a minimum guarantee, so it can make the slow application experience worse."}, {"role": "user", "content": "If we move to IPv6 and start using encrypted cloud traffic over TLS 1.3, does that change how we should design QoS for these applications, especially since we currently rely on port-based classification?"}, {"role": "assistant", "content": "Yes, it changes the design because port-based classification becomes unreliable when traffic is encrypted and increasingly uses dynamic ports, shared TLS endpoints, and IPv6 flows without traditional IPv4 port cues. In an IPv6 environment, you should still use the same core QoS model—identify business-critical real-time voice and video, then interactive messaging and file/content sharing—but classify with IPv6-aware tools such as application visibility and control, NBAR2, DNS-based policies, or traffic descriptors tied to the cloud provider’s published IP ranges where possible. Voice and video should still get priority or guaranteed bandwidth with low latency, jitter, and loss treatment, while messaging and file-sharing can receive assured or best-effort treatment depending on business need. Be careful not to rely on DSCP alone across the internet, because cloud providers and carriers may rewrite or ignore markings; use DSCP internally where trusted and complement it with application recognition and per-tunnel or per-provider policy at the edge. Finally, validate the design during business hours with IPv6 flow telemetry, because encrypted TLS 1.3 traffic may hide payload details and force you to depend more on observed flow behavior, endpoint reputation, and provider-specific ranges than on static Layer 4 ports."}], "meta": {"exam": "B", "qnum": 57, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "How can I prevent route recomputation during a stateful switchover on a Catalyst switch with dual supervisors when the upstream router doesn't support graceful restart?"}, {"role": "assistant", "content": "The key issue is that a stateful switchover causes route recomputation because the new supervisor lacks the routing state information. Since the upstream router doesn't understand graceful restart, we cannot use NSF, which depends on neighbor signaling. Instead, we need a feature that preserves the routing state across the supervisor failover. NSR (Non-Stop Routing) is designed exactly for this purpose; it allows the backup supervisor to maintain the routing table and forwarding information, so the network continues to operate without needing to recompute routes. Therefore, enabling NSR on the switch is the appropriate action."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Enabling IS-IS remote LFA FRR provides fast rerouting for link failures but does not address the stateful switchover issue. B - Enabling NSR on the switch ensures that the routing state is preserved during a supervisor failover, allowing for a seamless transition and preventing route recomputation. C - Enabling NSF on the switch requires support from neighboring routers to coordinate the switchover, which is not possible here since the upstream router does not understand graceful restart messaging. D - Configuring ISIS aggressive timers reduces convergence time but does not prevent the initial recomputation event during a switchover."}, {"role": "user", "content": "If the upstream router doesn't support graceful restart, could I still reduce IS-IS churn by tuning the IS-IS timers or using NSF/SSO on the Catalyst side instead, or does that only help when the neighbor also supports GR?"}, {"role": "assistant", "content": "On a Catalyst switch with dual supervisors, NSF/SSO is the mechanism that lets the switch preserve its forwarding state and control-plane adjacencies during a stateful switchover, but its benefit is limited when the upstream router does not understand graceful restart messaging. If the neighbor cannot participate in GR, it may still tear down the adjacency because it does not receive the expected GR capability exchange, which can trigger route recomputation even though the Catalyst side is using NSF/SSO. Tuning IS-IS hello and hold timers can reduce the chance of adjacency loss during a brief switchover, but it is not a true replacement for graceful restart and can slow failure detection if set too aggressively. The correct design answer remains to use the solution that avoids unnecessary route recomputation by matching the switchover behavior on the Catalyst to what the upstream router can support, such as nonstop forwarding with stateful switchover where applicable, rather than relying on GR with a neighbor that does not understand it."}], "meta": {"exam": "B", "qnum": 7, "topic": "", "has_exhibit": true, "desc_verified": true, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-WAN deployment, which routing information does OMP distribute so edge routers can forward overlay traffic without depending on the physical transport link IP addresses?"}, {"role": "assistant", "content": "OMP distributes TLOC routes. A TLOC is the logical transport locator, expressed as system-IP, color, and encapsulation, and it is used as the overlay next hop. This lets routers"}, {"role": "user", "content": "If OMP is already carrying the overlay reachability and policy information in a Cisco SD-WAN fabric, how does that change when the transport is IPv6 or when we’re mixing IPv4 and IPv6 underlay links between WAN Edge routers?"}, {"role": "assistant", "content": "In Cisco SD-WAN, OMP remains the control-plane overlay protocol and is transported inside a DTLS/TLS session to the vSmart controller, so the underlay can be IPv4, IPv6, or a mix without changing OMP’s role of distributing overlay routes such as TLOCs, service VPN prefixes, and policy. The key design point is that OMP separates overlay reachability from underlay addressing: WAN Edge routers advertise their TLOC with system IP, color, and encapsulation, while the actual transport locator may be reachable over IPv4 or IPv6. When the underlay is mixed, the WAN Edge must have valid transport interfaces and routes for each address family, and the TLOC/IPsec or GRE encapsulation is built according to the negotiated transport and encapsulation type. OMP then lets the fabric forward overlay traffic based on TLOC and VPN reachability rather than the physical link IP, so IPv4 and IPv6 underlays can coexist as long as control connections, TLOC reachability, and data-plane tunnels are operational. In failure scenarios, OMP withdraws or updates the affected TLOC and remote prefixes, allowing the fabric to reconverge through alternate WAN Edge routers or transports without requiring the overlay to depend on a specific link IP."}], "meta": {"exam": "B", "qnum": 77, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a multicast network with redundant paths, why does a router drop a PIM multicast packet when it arrives on an interface that is not the unicast route toward the source?"}, {"role": "assistant", "content": "That drop is the RPF check, which enforces loop-free multicast forwarding by accepting traffic only from the expected upstream direction. The router compares the multicast packet’s source address against the unicast routing table and discards the packet if the ingress interface is not the RPF interface toward that source. This prevents loops and duplicate packets while allowing PIM to build correct source-based distribution trees."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - RPF does not notify upstream routers of multicast traffic; PIM joins, registers, or other signaling perform that role.\nB - RPF does not send PIM prune messages toward sources; prune is a PIM mechanism used to remove unwanted branches.\nC - RPF does not eliminate overlapping multicast addresses; multicast address assignment or SSM range configuration handles addressing."}, {"role": "user", "content": "If the unicast route toward the source flaps or is asymmetric, does RPF still work the same way in an SSM-only IPv6 PIM domain, or do I need something like multipath RPF or a different RPF source?"}, {"role": "assistant", "content": "In an IPv6 PIM-SM/SSM domain, RPF still uses the unicast routing table (or a dedicated MRIB) to find the path back toward the source, so a flapping route can still cause transient RPF failures, but the source is a specific (S,G) under SSM rather than a shared tree RP-based (,G). With SSM, the receiver signals (S,G) via MLDv2, and the router builds an (S,G) state whose RPF interface is the route toward S; if that route flaps, the interface may be removed and re-added, briefly dropping traffic until reconvergence. For asymmetric or multipath topologies, PIM does not automatically do multipath RPF by default; you can enable ECMP RPF (or the platform’s equivalent) so PIM installs multiple valid RPF interfaces, but you still need consistent unicast routing—otherwise RPF can black-hole traffic on the wrong path. IPv6 does not change the logic, but you should verify that the MRIB is using the same table as IPv6 unicast routing and that any static mroute or route policy is mirrored in IPv6. In failure-mode terms, SSM avoids RP dependency but is not immune: fast unicast reconvergence, BFD, and consistent RPF policies are what keep multicast forwarding stable."}], "meta": {"exam": "B", "qnum": 88, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What configuration should be implemented to ensure the fastest possible convergence time if a link between two core switches fails?"}, {"role": "assistant", "content": "To achieve the fastest convergence time during a link failure between SW1 and SW2, the architect should enable UplinkFast on the switches. UplinkFast is a Cisco feature that allows a switch to quickly transition a blocked port to a forwarding state when a direct link to the root bridge fails, bypassing the normal STP listening and learning states. This significantly reduces the time it takes for the network to recover from a topology change. Therefore, enabling UplinkFast is the optimal solution for this requirement."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - UplinkFast is the correct answer because it provides the fastest convergence for a direct link failure to the root bridge. B - PortFast is used to speed up the transition of access ports to the forwarding state, not for link failure convergence. C - BackboneFast improves convergence for indirect link failures but is not as fast as UplinkFast for direct failures. D - Loop Guard prevents loops by placing a port in a loop-inconsistent state, but it does not accelerate convergence."}, {"role": "user", "content": "If I keep RSTP for fast convergence but need to support many VLANs across the same topology, how should I scale the design so I don't lose that speed or create instability?"}, {"role": "assistant", "content": "RSTP gives per-port rapid convergence, so its speed does not come from running one instance per VLAN; you can keep the physical topology lean and still get sub-second failover. For many VLANs, map them to a small number of RSTP instances by distribution-block or service group—often via MSTP (IEEE 802.1s), which is compatible with RSTP’s fast mechanisms—so a failure only reconverges the affected instance rather than all VLANs. Keep the Layer 2 domain bounded so RSTP/MSTP timers and topology changes stay manageable, and use Layer 3 redundancy such as FHRP plus routing reconvergence for cross-boundary failures. Avoid creating many parallel Layer 2 paths, because that increases the chance of TCN storms and unstable root placement. Also standardize bridge priorities so the intended root and backup root are deterministic, which lets the fast RSTP/MSTP proposal-agreement process do its job without manual tuning."}], "meta": {"exam": "C", "qnum": 13, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What QoS mechanism should be used to ensure that an application gets guaranteed bandwidth and meets its delay requirements?"}, {"role": "assistant", "content": "To ensure an application receives guaranteed bandwidth and meets its delay requirements, the engineer must use a QoS mechanism that provides end-to-end resource reservation. The exhibit shows a hierarchical network with a focus on reliable connectivity between offices, which is suitable for a controlled environment where such guarantees are critical. IntServ with RSVP is the appropriate choice because it allows applications to request specific services and reserves network resources along the entire path, ensuring the required bandwidth and low latency. This approach contrasts with Diffserv, which classifies traffic but does not offer the same level of guaranteed service."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Diffserv with RSVP is incorrect because Diffserv is a per-hop behavior model that does not reserve resources end-to-end; RSVP is typically used with IntServ. B - Diffserv with DSCP is incorrect because Diffserv uses DSCP for traffic classification and marking but does not provide the guaranteed bandwidth and delay support needed. C - IntServ with DSCP is incorrect because IntServ relies on RSVP for resource reservation, not DSCP, which is used in Diffserv."}, {"role": "user", "content": "If the network uses IPv6 for these delay-sensitive applications, how does the QoS design change compared to IPv4, and do the same mechanisms still guarantee bandwidth and delay?"}, {"role": "assistant", "content": "The QoS design logic stays the same in IPv6, but the classification and marking fields differ: instead of the IPv4 ToS byte, you use the IPv6 Traffic Class field, which still carries DSCP in the upper 6 bits and ECN in the lower 2 bits, so DSCP-based per-hop behaviors and priority queuing continue to work identically. Bandwidth guarantees via mechanisms like LLQ/CBWFQ and delay control via prioritization and shaping are Layer 3 protocol-agnostic, so they apply unchanged as long as devices support IPv6 QoS. The main practical differences are that you must verify IPv6 is enabled in the QoS policy maps (some platforms handle v4 and v6 class-maps separately), and you should account for the larger 40-byte IPv6 header plus extension headers in your bandwidth calculations. For coexistence, you can run parallel IPv4 and IPv6 policies or a unified policy that matches both, ensuring consistent DSCP treatment across the dual stack. If a device lacks full IPv6 QoS support, prioritize upgrading that node, because inconsistent per-hop behavior will break the end-to-end delay guarantee."}], "meta": {"exam": "C", "qnum": 21, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "On a PIM-SM router, when a multicast packet passes the RPF check, how does the router determine which interfaces should receive a copy?"}, {"role": "assistant", "content": "Forward the packet only on the interfaces in the multicast route’s OIL. In PIM"}, {"role": "user", "content": "In a PIM-SM deployment where the RPF check passes for a multicast packet, how does the forwarding decision differ if the topology is using IPv6 and MLD instead of IPv4 and IGMP?"}, {"role": "assistant", "content": "The core PIM-SM RPF logic is unchanged with IPv6: the router still checks whether the packet arrived on the interface that is the reverse-path next hop toward the multicast source, or toward the Rendezvous Point for shared-tree traffic, using the IPv6 unicast routing table. What changes is the group-membership and signaling side: MLD replaces IGMP, so the router builds Layer 2 and interface receiver state from MLD reports rather than IGMP reports. After a successful RPF check, the router still uses the outgoing interface list derived from the multicast route entry to decide where to replicate the packet, and that OIL is populated based on PIM joins plus MLD-learned receiver interest on downstream links. In IPv6, PIM-SM is typically PIM-SMv2 for IPv6, and the RPF neighbor is still resolved through the MRIB, which is fed by the IPv6 routing table. So the packet is forwarded out the interfaces in the OIL, pruned toward the source or RP as needed, and not flooded out the RPF interface, regardless of whether the control-plane membership protocol is IGMP or MLD."}], "meta": {"exam": "C", "qnum": 31, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access design, which plane should I use to automate fabric device onboarding and configuration?"}, {"role": "assistant", "content": "Use the fabric management plane, typically implemented by Cisco DNA Center, for automated device deployment and configuration. It provides PnP onboarding, configuration templates, fabric provisioning, and assurance workflows. LISP EID-to-RLOC mapping belongs to the control plane, while IS-IS underlay routing and VXLAN forwarding belong to the underlay/data planes."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - LISP-based endpoint identifiers are part of the SD-Access control plane, not the management plane.\nC - EID-to-RLOC mapping is handled by the LISP control plane, not by a BGP-based management function.\nD - An IS-IS underlay is forwarding infrastructure that may be automated by the management plane, not the management plane itself."}, {"role": "user", "content": "If the fabric management plane is what handles device onboarding and configuration automation, what happens to that workflow when the underlay is migrated to IPv6, and does the fabric management plane itself need to be dual-stack or can it stay IPv4-only?"}, {"role": "assistant", "content": "The fabric management plane in SD-Access is anchored on Cisco DNA Center (now Catalyst Center) plus the underlay routing and management protocols that stitch fabric nodes back to it, and it’s logically separate from the data and control planes. In practice, the underlay can absolutely be migrated to IPv6 (for example, IS-IS or OSPFv3 for underlay reachability, and IPv6 for the LISP/BGP handoff at the border), but the management plane’s transport to Catalyst Center and the fabric’s northbound automation channel typically remain IPv4 unless you deliberately reconfigure them. There is no requirement that the management plane be dual-stack for the fabric to function — fabric nodes just need IP reachability to Catalyst Center, PnP/DHCP services, and the border/control plane nodes, and that reachability can be IPv4 even while the underlay forwarding is IPv6. That said, many designs do run dual-stack on the management interfaces so that onboarding, telemetry, and software image distribution aren’t tied to a single address family and so IPv6-only branches can still be onboarded cleanly. The key design point is to keep the management plane addressing stable and reachable throughout the migration, because if Catalyst Center loses reachability to a node mid-migration, onboarding and config push fail even though the data plane keeps forwarding. So the safe answer is: the underlay can go IPv6 independently, the management plane can stay IPv4, but dual-stack management is strongly recommen"}], "meta": {"exam": "C", "qnum": 39, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "What is the main purpose of the E-LMI protocol in this Metro Ethernet setup?"}, {"role": "assistant", "content": "The E-LMI protocol, as shown in the diagram connecting the CE and PE, operates under the MEF 16 specification to facilitate communication between the customer's edge device and the provider's edge device. The key function of E-LMI is not to handle data forwarding or route distribution but to manage the connection state. It allows the PE to send updates to the CE about the health and availability of the EVC. For example, if an EVC fails, the PE uses E-LMI to notify the CE that the service is no longer available. This ensures the CE has accurate information about its service status without requiring complex configuration. The correct answer is B because it directly states that E-LMI notifies the CE of the availability state of a configured EVC."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - broadcasts multicast network routes from the CE to the PE; C - communicates ENI and EVC attributes to the CE; D - broadcasts to all subnets from the CE when an EVC is added"}, {"role": "user", "content": "If this Metro Ethernet design scales to hundreds of EVCs across multiple UNIs and the provider also runs MPLS in the core, how does E-LMI coexist with the MPLS control plane, and what happens to E-LMI status signaling if the service becomes MPLS-based rather than pure Ethernet?"}, {"role": "assistant", "content": "E-LMI is defined by MEF 16 to operate between the CE and the PE over the UNI, so it stays a local access-side signaling and status protocol regardless of what transport runs inside the provider core. When the provider uses MPLS, the PE still maps each EVC to an MPLS pseudowire or VPLS instance, and the CE-facing E-LMI process continues to report EVC availability, configuration, and status based on that mapping. The MPLS control plane handles label distribution and pseudowire signaling internally, while E-LMI remains the subscriber-facing mechanism that tells the CE which EVCs are active and what their UNI attributes are. At scale, the PE must maintain E-LMI state per UNI and per EVC, so the design should consider scaling limits on the PE and the use of status polling or asynchronous updates defined by MEF 16. If the service is delivered as an MPLS-based Layer 2 VPN, E-LMI still functions as long as the PE supports the MEF UNI type and maps EVC status correctly; otherwise the CE loses standardized EVC status visibility. A failure in the MPLS core, such as a pseudowire or remote PE failure, should be reflected by the PE into E-LMI status changes so the CE can react, but if that mapping is not implemented, the CE may see the UNI as up while the EVC is actually down."}], "meta": {"exam": "C", "qnum": 53, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "Given this highly available network design, what is the best method to achieve sub-second convergence for link failures in the DWDN Network?"}, {"role": "assistant", "content": "To achieve sub-second convergence as required, we need a fault detection mechanism that operates faster than the standard OSPF protocol's timers. The key requirement is to switch traffic without waiting for the OSPF dead interval, which is inherently slow. While options A and B involve tuning OSPF timers, these changes only affect the speed of the routing protocol's processing after a failure has been detected, not the detection itself. IP SLA tracking (D) can be used for path monitoring but is often more complex to configure and may not provide the same level of integration and speed as BFD. BFD, however, is specifically designed for rapid fault detection. It runs as an independent protocol over the data link layer and can detect a loss of connectivity in tens of milliseconds. Therefore, the correct solution is to utilize BFD and tune its timers to 100 ms."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "- A. Decreasing SPF timers will reduce the time it takes for the router to recalculate routes, but it does not address the initial problem of detecting the failure.\n- B. Tuning the SPF delay and LSA interval timers speeds up the internal OSPF process, but the entire process is still dependent on the slower OSPF dead timer to detect the failure.\n- D. Enabling IP SLA tracking provides proactive monitoring, but it is generally less efficient and slower than BFD for immediate fault detection in this context."}, {"role": "user", "content": "Would BFD still be the right choice if Area-1 were migrated to OSPFv3 for IPv6, and does it matter whether we run BFD per-interface versus per-neighbor in that dual-stack coexistence scenario?"}, {"role": "assistant", "content": "Yes—BFD remains the correct fault-detection mechanism for OSPFv3, since BFD is a media- and protocol-agnostic hello mechanism that operates below OSPF and can be enabled independently for IPv4 and IPv6 sessions. In a dual-stack coexistence design, you would typically run separate BFD sessions per address family (one for the IPv4 OSPFv2 adjacency and one for the IPv6 OSPFv3 adjacency), each tracking its own neighbor and interface state. BFD is inherently per-session between two neighbors over a specific path, so \"per-interface\" really just describes where the session is anchored, while the failure detection is still tied to the neighbor relationship and its liveness. For OSPFv3, the relevant commands are `bfd interval` under the interface plus `ipv6 ospf bfd` (or `bfd all-interfaces`) under the routing process, and the same millisecond timers (for example, 50 ms interval with a multiplier of 3) give you sub-second, dead-interval-independent detection. The key design consideration is that both address families must have BFD enabled and tuned consistently; otherwise a failure detected only by one family could leave the other adjacency waiting on the OSPF dead interval."}], "meta": {"exam": "C", "qnum": 63, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "I'm troubleshooting an EIGRP network where a DUAL-3-SIA error appears on the hub router. The network uses a hub-and-spoke topology with low-bandwidth connections, and all branch routers have limited resources. What should I do to fix this?"}, {"role": "assistant", "content": "Based on the scenario, the DUAL-3-SIA error suggests that a router is stuck waiting for a response to a query about a lost route. In a hub-and-spoke network, if split horizon is enabled on the hub router (R1), it will not advertise routes learned from one spoke back out to another spoke. If a spoke router needs to reach a destination via the hub but the direct path is down, it queries the hub. The hub then queries its other spokes, but because of split horizon, those spokes don't reply back to the hub. This creates a deadlock, leading to the SIA error. To resolve this, you must disable split horizon on the hub router (R1) so that it can accept and forward route advertisements from its spokes, allowing them to communicate and resolve the query."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "A - Configuring a STUB area on R4 would reduce the amount of routing information exchanged but does not address the root cause of the SIA error, which is a communication breakdown between routers. B - Poison reverse is used to prevent routing loops by advertising a route with an infinite metric, but it doesn't solve the problem of a router being unable to respond to a query. D - Creating a summary route on R2 might reduce the size of the routing table but won't resolve the active query that is causing the SIA error."}, {"role": "user", "content": "If I later add IPv6 to this same EIGRP hub-and-spoke design, can the low-bandwidth 10 Mbps links and limited-resource spokes still trigger a DUAL-3-SIA, and what would I change to keep the design stable for IPv6?"}, {"role": "assistant", "content": "Yes — DUAL-3-SIA is a transport/topology symptom, not an IPv4-specific one, so the same 10 Mbps hub-and-spoke EIGRP design can produce it under EIGRPv6 on the same links if hellos, ACKs, or query/reply traffic are delayed or dropped. In EIGRP for IPv6, you would typically run a separate EIGRPv6 process (or named-mode EIGRP address-family ipv6) and may see the same stuck-in-active condition on the hub because the hub has many spokes and its queries fan out over slow or congested WAN links. The most effective design fix is to constrain query scope with EIGRP stub routing on the spokes (especially stub connected/redistributed/summary as appropriate) so they do not receive or propagate unnecessary queries, and to use summarization on the hub toward the spokes where possible. You should also verify hello/hold timers are consistent and not too aggressive for the 10 Mbps path, ensure the links are not saturated by other traffic, and consider named EIGRP mode with address-family configuration to keep IPv4 and IPv6 policies clean and consistent. If resource limits on the spokes are severe, reducing neighbor count and query domain size is more important than tuning timers alone."}], "meta": {"exam": "C", "qnum": 8, "topic": "", "has_exhibit": true, "desc_verified": false, "quiz_user_source": "generated", "variant": "multi_turn", "refined": true}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco SD-Access fabric, which fabric role should I deploy to route traffic between fabric endpoints and an external data center or legacy WAN?"}, {"role": "assistant", "content": "Use border nodes. They are the fabric boundary devices that connect SD-Access to external Layer 3 networks, perform VXLAN-to-VLAN/VRF handoff, and exchange routes with external routers via protocols such as BGP or OSPF. Control plane nodes provide LISP mapping services, edge nodes connect endpoints, and intermediate nodes carry underlay traffic, but external communication is a border-node function."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "B - Control plane nodes provide LISP map-server/map-resolver functions and do not peer with external networks for fabric external connectivity.\nC - Intermediate nodes are under"}, {"role": "user", "content": "If the external connection is dual-homed to two border nodes for redundancy, how do I design the handoff so traffic from external networks can still reach fabric endpoints if one border node fails, and does this change if the outside network uses OSPF instead of BGP?"}, {"role": "assistant", "content": "In an SD-Access fabric, you typically deploy two border nodes as a redundant pair, and the external network should be connected so both border nodes are reachable through a Layer 3 handoff or a shared Layer 2 segment, depending on the design. For high availability, the external routers or data center switches should peer with both border nodes, and the fabric should advertise the fabric endpoint subnets into the external domain from each border node. If the outside network uses OSPF, each border node can run OSPF with the external routers and advertise the fabric prefixes, but you must carefully control metrics and area design to avoid suboptimal routing or asymmetric paths. With BGP, the border nodes commonly use eBGP to the external network, and you can influence path selection using local preference, MED, or AS-path attributes; if one border node fails, the external routers reconverge to the remaining border node. The key design constant is that the border nodes provide the fabric-to-external reachability, while the control plane node handles fabric internal endpoint registration and the edge nodes encapsulate endpoint traffic; that role separation stays the same regardless of whether the external routing protocol is OSPF, BGP, or static routing."}], "meta": {"exam": "C", "qnum": 89, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
| {"messages": [{"role": "system", "content": "You are a precise Cisco network-design assistant at CCNP Enterprise level. Answer accurately and concisely."}, {"role": "user", "content": "In a Cisco ISE deployment, what are the main functions it provides for endpoint visibility and enforcing security policy?"}, {"role": "assistant", "content": "The two primary functions are enforcing endpoint compliance and providing information about every device that touches the network. ISE identifies and profiles endpoints using RADIUS, 802.1X, MAB, and posture, then applies authorization policies to enforce compliance and network access rules."}, {"role": "user", "content": "Why are the other options wrong in this scenario?"}, {"role": "assistant", "content": "B - Enabling WAN deployment over any type of connection is a function of Cisco SD-WAN, not Cisco ISE.\nC - Automatically enabling, disabling, or reducing power to devices is Power over Ethernet negotiation, not a primary ISE function.\nE - Providing encryption for mobile devices is typically handled by VPN, IPsec, or SSL, not Cisco ISE.\nF - Allocating cloud resources is a cloud orchestration/management function, not Cisco ISE."}, {"role": "user", "content": "In a large Cisco ISE deployment spanning multiple sites with high-availability and failover requirements, how does ISE handle endpoint visibility and policy enforcement when a node or the primary PAN becomes unavailable, and what design considerations should we account for?"}, {"role": "assistant", "content": "In a distributed ISE deployment, the Policy Administration Node (PAN) is the single source of truth for configuration, while Policy Service Nodes (PSNs) handle the actual authentication, authorization, and endpoint profiling, so PSNs continue enforcing policy locally even if the primary PAN fails because they cache the last-known-good policy and profiling data. High availability is achieved by deploying a secondary PAN in a hot-standby role and pairing PSNs into node groups with session failover, allowing endpoints to be reauthenticated or have sessions replicated to a backup PSN if a primary PSN goes down. During a primary PAN outage, the secondary PAN can be manually promoted, but administrative changes and some distributed operations (like certain logging or replication tasks) may be temporarily limited until failover completes. For scalability across multiple sites, you should distribute PSNs geographically close to the endpoints to reduce latency for RADIUS and TACACS+ transactions, and size each PSN based on expected authentication load, latency, and failover capacity. Design considerations also include deploying the PAN and PSN roles on separate nodes, ensuring database replication and certificate trust are correctly configured, and validating that failover behavior meets your RADIUS and posture requirements, since endpoint visibility and enforcement depend on continuous, resilient PSN availability."}], "meta": {"exam": "C", "qnum": 98, "topic": "", "has_exhibit": false, "variant": "multi_turn"}} | |
Xet Storage Details
- Size:
- 418 kB
- Xet hash:
- 1e07e44a3b1bcb1ada800916c24c3c7bef22e8d3863e48406215592c3d381793
·
Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.