350-501 VCE Exam Download

The configuration shown in the exhibit enables IP flow information collection on the interface gigabitethernet0/1. This setup is used for network traffic analysis, and when applied, it provides data that includes the source interface of the traffic for traceback analysis. This is useful for identifying the origin of traffic, which can be critical in situations such as security incidents or network troubleshooting.

The configuration in Option A is correct for enabling dial-out telemetry streams using gRPC on devices with TLS disabled.

It uses model-driven telemetry (MDT), which is a new method of monitoring network devices. Unlike traditional methods that pull data from the device, MDT pushes data from the device to the collector.

In this configuration:

Telemetry is model-driven.

It specifies a destination group with an IP address and port number where the telemetry data will be sent.

The encoding is self-describing-gpb (Google Protocol Buffers).

The protocol used is TCP.

This setup ensures that telemetry data is sent to the specified collector without requiring TLS encryption.

 MPLS LDP (Label Distribution Protocol) is used for label distribution in MPLS networks. When making changes to the LDP configuration, it’s essential to ensure that the changes do not disrupt existing LDP sessions. In this scenario, the network administrator implemented MPLS LDP changes on the PE-A LSR (Label Switching Router) device, and the goal is to prevent any disruption to LDP peers.

The MPLS LDP Non-Stop Routing (NSR) feature allows LDP sessions to survive control-plane switchover events without interruption. When NSR is enabled, the LDP session state information is synchronized between the active and standby control planes. If the active control plane fails, the standby control plane takes over seamlessly, and LDP sessions continue without interruption.

 To align with customer contract SLAs and allow 10% of interface capacity on router R3 for traffic from CE1 towards the FTP server, the network engineer must apply a policy map to R1 to reserve the remaining 10% of interface bandwidth (Option C). Additionally, applying a policy map to R3 to reserve 10% of interface bandwidth (Option D) ensures adherence to the customer’s contract SLAs while utilizing the allocated bandwidth capacity. References: Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) - Quality of Service section.