Refer to the exhibit. An administrator configures inter-VRF route leaking between Production:vrf- prod and Non-Production:vrf-nonprod. However, the route in the Non-Production:vrf-nonprod VRF to the…

Changing the contract scope to Global is typically for inter-tenant communication or making an L3Out globally available, but it does not directly enable the leaking of specific BD subnets between VRFs within the same or different tenants.

For inter-VRF route leaking, the specific subnet within the Bridge Domain (BD) that resides in the source or provider VRF (Production:vrf-prod in this scenario) must be explicitly configured with the "Shared between VRFs" option. This flag enables the ACI fabric to advertise and leak that subnet's route into other VRFs, such as Non-Production:vrf-nonprod, when a contract permits.

Subnets are defined at the Bridge Domain level, not directly at the EPG level, and enabling "Shared between VRFs" on an EPG subnet is not the correct mechanism for inter-VRF route leaking. The flag applies to BD subnets.

Exporting a contract from a provider to a consumer tenant is for inter-tenant contract sharing, not the specific setting required for enabling a subnet to be leaked between VRFs.