Question 1
When you execute a reboot command on the vMaster, how is aVCS Chassis affected?
- Reboot is performed on vMaster and reload operation on vBlades.
- All devices in the chassis are rebooted.
- Reboot is performed on vMaster.
- Reboot is performed only on vBlades.
Question 2
What information is typically submitted with every aXAPI call after the initial login is complete?
- Authorization header with signature
- The ACOS device serial number
- The programming language being used
- The AXAPI special permission XML file
- Log file location
Question 3
What is the purpose of a VRRP-A floating-IP address?
- To serve as a tie-breaker when selecting a VRRP-A owner.
- To provide a single next hop IP address for uplink and downlink devices.
- To use as source IP address for VRRP-A hellos.
- To provide a single IP to manage all VRRP-A devices in the set.
Question 4
When vBlade A issues a “vcs vmaster-take-over 200” command, which statement is true?
- The command is ignored when the current vMaster is in vMaster maintenance mode.
- Any subsequent vmaster-take-over command within the chassis with a parameter smaller than 201 is ignored.
- The 200 priority is compared to the current vmaster’s default vrid priority to determine which device controls the chassis.
- If an administrator on vBlade B were to simultaneously issue command vcs vmaster-take-over 210, vBlade B would become the vMaster.
Question 5
Which statement describes the effect this command: erase preserve-management
- The startup-config file is erased and the ACOS is immediately rebooted
- All configuration profiles, SSL certificates, aFlex polices, black/white lists, and system logs are erased the next time the system reboots
- The startup-config file is erased but the management interface ip configuration is kept
- The start-up config file is erased but the all of the admin accounts are preserved