Cisco 350-501 Exam With Confidence Using Practice Dumps

The disruption in IS-IS connectivity between R1 and R2, despite the interfaces being up, suggests an issue with packet handling or MTU configuration. Action A, disabling padding for hello packets under the serial interface on R2, is necessary because excessive padding can lead to issues in processing hello packets effectively. Action C, changing the MTU to 1500 bytes on R2, addresses potential MTU mismatch issues. MTU mismatches are common problems that can interrupt connectivity in networks using routing protocols like IS-IS; ensuring both routers operate at the same MTU can resolve this issue.

References := The explanation is derived from the principles outlined in Cisco’s Implementing and Operating Cisco Service Provider Network Core Technologies, which emphasizes the importance of proper packet handling and MTU configuration for maintaining IS-IS connectivity.

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.