In this scenario, you want the border leaf device to advertise Type 5 EVPN routes to another border leaf in a different data center. Type 5 routes in EVPN are used to advertise IP prefixes, which means that for proper route advertisement, you need to configure the correct settings within the evpn hierarchy.
Step-by-Step Analysis:
* Understanding EVPN Type 5 Routes:
* EVPN Type 5 routes are used to advertise IP prefixes across EVPN instances, which allow different data centers or networks to exchange routing information effectively.
* VRF Target Setting:
* The vrf-target configuration is crucial because it defines the export and import policies for the VRF within the EVPN instance. For EVPN Type 5 routes to be advertised to other border leaf devices, the vrf-target needs to be correctly configured under the evpn hierarchy, not just within the routing instance.
Command to solve this:
move vrf-target target:65000:1 to evpn
* Other Options:
* Option B:Adding a VLAN configuration would not address the requirement to advertise Type 5 routes.
* Option C:Adding VXLAN encapsulation may be necessary for other scenarios but does not directly address the Type 5 route advertisement.
* Option D:Changing the route-distinguisher will differentiate routes but does not impact the advertisement of Type 5 routes to other data centers.
By moving the vrf-target to the evpn hierarchy, you enable the proper route advertisement, ensuring that the Type 5 routes for local networks are shared with other data center border leaf devices. This is aligned with best practices for multi-data center EVPN implementations, which emphasize the correct placement of routing policies within the EVPN configuration.

The Junos Telemetry Interface (JTI) supports streaming real-time data from devices using modern, efficient protocols:
using UDP
JTI supports UDP-based streaming, often with Juniper's JTIs streaming protocol (for low-latency telemetry).
using gRPC
JTI supports gRPC/gNMI for structured, reliable telemetry export.

By default, Juniper switches with factory-default configurations attempt to obtain an IP address via DHCP on any connected and operational interface, not just the management interface.
The DHCP server configuration can include options to provide Junos version requirements, such as bootfile information, to DHCP clients for automated provisioning or upgrades.

* Telemetry Methods in Junos:
* Telemetry is used to collect and report data from network devices. For high-frequency statistics reporting, such as every five seconds, you need a telemetry method that supports this level of granularity and real-time monitoring.
* Junos Native Sensors:
* Option C:Native Sensors in Junos provide detailed, high-frequency telemetry data, including TX and RX traffic statistics for interfaces. They are designed to offer real-time monitoring with customizable sampling intervals, making them ideal for the five-second reporting requirement.
Conclusion:
* Option C:Correct-Native Sensors in Junos are capable of providing the required high-frequency telemetry data every five seconds.