To isolate management traffic in a non-default routing-instance on Junos-based devices, you can use the set system management-instance and set routing-instances mgmt_junos commands. set system management-instance: This command associates the management interface (usually named fxp0 or em0 for Junos OS, or re0:mgmt-* or re1:mgmt-* for Junos OS Evolved) with the non- default virtual routing and forwarding (VRF) instance. After you configure the non-default management VRF instance, management traffic no longer has to share a routing table with other control traffic or protocol traffic.
set routing-instances mgmt_junos: This command creates a new routing instance named mgmt_junos. The name of the dedicated management VRF instance is reserved and hardcoded as mgmt_junos; you cannot configure any other routing instance by the name mgmt_junos.
Therefore, options C and D are correct. Options A and B are not correct because they attempt to assign an interface to the mgmt_junos routing instance, which is not necessary for isolating management traffic.

The default hold-time is 90 seconds, meaning that the default frequency for keepalive messages is 30 seconds.
https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/ref/statement/precision- timers-edit-protocols- bgp.html#:~:text=BGP%20on%20the%20local%20routing,keepalive%20messages%20is%2030
%20seconds