You are adding a new EX4300 member switch to your existing EX4300 Virtual Chassis. However, the new
member is not running the same Junos version as the other members.
By default, what is the expected behavior?
A.
The new switch is not recognized by the Virtual Chassis.
B.
The Virtual Chassis will transition into a split brain situation between the existing master Routing Engine and
the switch running the different version.
C.
The new switch will be assigned a member ID and then placed in an inactive state.
D.
The new switch will automatically pull the correct version from the master Routing Engine and perform the
necessary upgrade.
I think the answer is C.
I believe automatic sw update is not enabled by default
https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/virtual-chassis-ex4200-software-automatic-update-ex-series-cli.html
You are correct:
For a standalone switch to join an existing Virtual Chassis, it must be running the same version of Junos OS that is running on the Virtual Chassis master. When the master in a Virtual Chassis detects that a new switch has been added to the configuration, it checks the software version on the new switch. If the software version on the new switch is not the same as the version running on the master, the master keeps the new switch in the inactive state. If you have not enabled the automatic software update feature, you have to manually install the correct software version on each prospective member switch as it is added to the Virtual Chassis.
https://www.juniper.net/documentation/en_US/junos/topics/concept/virtual-chassis-ex4200-software-automatic-update.html
Answer correct is C
from new junos releases, auto-image upgrade is enabled by “default” on standalone switches.
this is to make sure that new ex switches that are being added to the VC will have less intervention.
D is the answer.
Of course D…