Refer to the exhibit. A network engineer checks connectivity between two routers. The engineer can ping the remote endpoint but cannot see an ARP entry. Why is there no ARP entry?

The ping command can be executed successfully within a VRF context; the issue is with the visibility of the ARP entry in the global table, not the command's execution itself.

Virtual Routing and Forwarding (VRF) instances create isolated routing and forwarding tables on a single router. If FastEthernet0/0 is configured within VRF CUST-A, all network operations, including the Address Resolution Protocol (ARP) table, are logically separated and belong exclusively to that VRF, hence the ARP entry would only be discoverable within the CUST-A VRF context.

ARP protocol is a fundamental aspect of IP communication on a local segment and functions automatically within each VRF without requiring explicit enabling per VRF.

The ARP protocol is not disabled in the global routing table when VRFs are used; it continues to operate normally for interfaces assigned to the global routing table.