Multiple VLAN Registration Protocol (MVRP) dynamically propagates VLAN information between switches. For MVRP to function correctly across a network, it must be enabled on all trunk interfaces that are part of the desired Layer 2 path. The provided configuration for Core-1 only enables MVRP on interface ge-0/0/15.0, which connects to Access-1. To allow VLANs to be propagated to and from Access-2, MVRP must also be enabled on the trunk interface on Core-1 that connects to Access-2, which is ge-0/0/16.0. This ensures that VLAN registration messages can be exchanged across the entire path.

A. The choice of spanning tree protocol (RSTP vs. VSTP) is unrelated to the VLAN propagation failure caused by the incomplete MVRP configuration.

B. MVRP is designed for inter-switch trunk links to manage VLAN propagation, not for host-facing access interfaces. Configuring it on access ports is incorrect.

D. Similar to option B, enabling MVRP on access interfaces is an improper configuration and would not solve the trunk link propagation issue.

1. Juniper Networks. (2023). Understanding Multiple VLAN Registration Protocol (MVRP) for VLANs. TechLibrary. In the "MVRP Operation" section, it states, "To enable MVRP, you must configure it on all trunk interfaces on all switches that you want to participate in MVRP." This confirms that MVRP must be enabled on all relevant trunk ports. Retrieved from https://www.juniper.net/documentation/us/en/software/junos/vlan-l2/topics/concept/mvrp-understanding.html

2. Juniper Networks. (2023). Configuring MVRP (CLI Procedure). TechLibrary. Step 2 of the "Step-by-Step Procedure" shows the command set protocols mvrp interface interface-name and includes the instruction, "Repeat this step for all trunk interfaces that will participate in MVRP." This directly supports the need to configure the interface to the second access switch. Retrieved from https://www.juniper.net/documentation/us/en/software/junos/vlan-l2/topics/task/mvrp-configuring.html