350-501 Cisco Implementing and Operating Cisco Service Provider Network Core Technologies (350-501 SPCOR) Free Practice Exam Questions (2025 Updated)

 The JSON script in the exhibit configures BGP with a neighbor at IP address 192.168.1.2 that resides in AS (Autonomous System) 65514. In the script,  specifies the neighbor’s IP address, and  indicates the AS number of the neighbor.

References: For more information, you can refer to the “Implementing and Operating Cisco Service Provider Network Core Technologies” training, which covers topics such as configuring, verifying, troubleshooting, and optimizing Service Provider IP network infrastructures, including BGP configurations

 In BGP, the weight attribute is the first criterion used to determine the best path. It is a Cisco-specific attribute and is not propagated in BGP updates. Weight is a numeric value, and the path with the highest weight is preferred. If weights are the same, BGP will then consider the local preference, AS path length, origin type, and other attributes in sequence.

References: Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) training material

When implementing traffic shaping on a network, the goal is to control the rate of traffic being sent into the network to avoid congestion. This is done by buffering excess packets and then scheduling them to be sent out at a steady rate.

Option A is correct because traffic shaping requires a queue with sufficient memory to buffer excess packets. When the traffic rate exceeds the configured maximum rate (shaping rate), the excess packets are temporarily stored in the queue until they can be sent out, ensuring a smooth flow of traffic without overwhelming the network1.

Option B is also correct as traffic shaping involves configuring token values in bytes. Tokens are used to represent permission to send a certain amount of data. The token bucket is filled with tokens at a steady rate, and packets can only be sent if there are enough tokens in the bucket. The token values determine the size of the bucket and the rate at which it is refilled, which in turn controls the rate of traffic1.

Option C is incorrect because packet remarking for excess traffic is not a component of traffic shaping. Packet remarking is typically used in conjunction with policing, where packets that exceed the rate limit can be remarked to a lower priority for downstream handling1.

Option D is incorrect in the context of traffic shaping. While a scheduling function is used to handle the packets that are delayed due to buffering, the scheduling itself is not part of the shaping mechanism but rather a function of the queuing system that works alongside shaping1.

Option E is incorrect as it pertains to traffic policing, not shaping. In traffic policing, packets that exceed a certain threshold are discarded or remarked, whereas shaping delays excess packets by buffering them1.

References: The information provided here is based on the Quality of Service (QoS) Configuration Guide from Cisco, which details the components and implementation of QoS, including traffic shaping1.

 Both Chef and Puppet are configuration management platforms that aim to configure and manage servers and other IT infrastructure. They operate in the same infrastructure management space and share several similarities:

Use a master-client architecture: Chef functions with a master-client architecture, where the server runs on the master machine, and the client runs as an agent on every client machine. Similarly, Puppet follows a similar setup.

Manage devices or nodes to be configured: Both Chef and Puppet manage the configuration of devices or nodes within an infrastructure.

Leverage a pull model: Both tools use a pull model, where the configuration is pulled from a central server to the managed nodes.

 To prevent packets from being forwarded beyond the service provider domain when the Label Switched Path (LSP) is down, the engineer must configure a private IP address as the destination address of the headend router of Cisco MPLS Traffic Engineering (TE). This ensures that if the LSP fails, the packets will not be routable over the public internet, thus containing them within the service provider’s network.

References := Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) documentation provides guidelines on MPLS TE configuration, including the use of private IP addresses for headend routers to maintain traffic within the service provider domain. This practice is aligned with the principles of traffic engineering and network containment for service providers.

 The control plane protocol used between Cisco SD-WAN routers and vSmart controllers is the Overlay Management Protocol (OMP). OMP is a proprietary protocol of Cisco SD-WAN that facilitates the exchange of routing, policy, and management information across the network. It operates within the secure environment provided by the Datagram Transport Layer Security (DTLS) or Transport Layer Security (TLS) control connection, ensuring that the communication between the routers and controllers is encrypted and authenticated1.

References := Cisco 300-415: Cisco SD-WAN vSmart-WAN Edge Router Control Plane Protocol

 OSPFv3 is designed to support both IPv4 and IPv6. The message “IPv6 routing not enabled” indicates that IPv6 has not been configured on the router, but this does not prevent OSPFv3 from running for IPv4. The OSPFv3 configuration for IPv4 will still function on the interface FastEthernet0/0 as intended.

The configuration shown is for the head-end router of a Cisco MPLS TE tunnel with segment routing. This setup involves commands related to segment routing and MPLS traffic engineering tunnels, such as “mpls traffic-eng tunnels”, “segment-routing mpls”, and “segment-routing prefix-sid-map advertise-local”. These commands configure the head-end router to effectively create and manage TE tunnels using segment routing. References: Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) - Cisco SPCOR Training & Certification.

https://www.cisco.com/c/en/us/solutions/service-provider/mobile-internet/5g-transport/converged-5g-xhaul-transport.html#

Router 1 is the trigger router in a Remote Triggered Black Hole (RTBH) implementation. In the configuration provided, Router 1 has a static route to null0 for network 192.168.1.0/24 with a tag of 1, which is used to drop traffic destined to this network, effectively mitigating DDoS attacks. The route-map “ddos” matches this tag and sets local preference and community accordingly. The BGP process redistributes this static route based on the “ddos” route-map, signaling other routers in the network to drop traffic destined for the attacked network. References: Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) - RTBH section1.

 To implement a PIM-SSM (Protocol Independent Multicast - Source Specific Multicast) configuration for streaming live traffic across different domains, the network operator must ensure that IGMPv3 (Internet Group Management Protocol version 3) is enabled on R1. IGMPv3 is required for SSM because it allows the receiver to specify the source IP address of the desired traffic, which is a key feature of SSM. The operator would configure IGMPv3 on the interfaces that connect to the users who will be accessing the multicast stream. Additionally, PIM-SSM must be enabled on the router, and the multicast sources and groups must be properly defined.

References: The explanation is based on the concepts outlined in the Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) course

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/cether/configuration/xe-3s/asr903/16-12-1/b-ce-xe-16-12- asr900/m_ce_802_1ad_900.html

The configuration shown indicates that R1 has been configured to support Label Distribution Protocol (LDP) graceful restart. This means that R1 will maintain the forwarding state during an LDP restart, allowing it to continue forwarding packets along known routes while it re-establishes LDP neighbors/peers. This ensures minimal disruption to traffic flow during such events. References: Implementing and Operating Cisco Service Provider Network Core Technologies source documents or study guide

 In Cisco Service Provider Network Core Technologies, an EVPN instance can be likened to a VRF (Virtual Routing and Forwarding). A VRF allows multiple instances of a routing table to co-exist within the same router at the same time. Similarly, EVPN provides separation between routing instances which aligns with how VRF operates.

OSPF adjacency is established when two OSPF routers have matching interface parameters. This includes the OSPF router ID, network address, area ID, and other OSPF-specific configurations such as MTU size and network type. For example, the configuration commands provided in the image description suggest setting the OSPF router ID, network address with a wildcard mask, and specifying the OSPF area. Additionally, the interface is set to a point-to-point network type with a specific MTU size, which is important for OSPF adjacency as mismatched MTU sizes can prevent OSPF neighbors from forming an adjacency.

References: For a comprehensive understanding, refer to the “Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR)” official Cisco documentation and study guide,