Exam F5CAB5 Topic 6 Question 57 Discussion
Actual exam question for F5's F5CAB5 exam
Question #: 57
Topic #: 6
Question #: 57
Topic #: 6
A traffic group includes four devices. The failover method is HA order. The failover order is:
* BIGIP-D
* BIGIP-B
* BIGIP-C
* BIGIP-A
Auto fallback is enabled. BIGIP-D has been forced to standby. BIGIP-B was active before being rebooted.
Which device is active when BIGIP-B is up after the reboot?
* BIGIP-D
* BIGIP-B
* BIGIP-C
* BIGIP-A
Auto fallback is enabled. BIGIP-D has been forced to standby. BIGIP-B was active before being rebooted.
Which device is active when BIGIP-B is up after the reboot?
Suggested Answer: C Vote an answer
To understand which device becomes active, we must look at how the BIG-IP system handles HA Order and Auto Fallback within a traffic group.
* HA Order Mechanism: When a traffic group is configured with an "HA Order" list, the system prefers to host the traffic group on the highest-ranking available device in that list (1 being the highest).
* The Impact of "Forced to Standby": BIGIP-D is the first choice in the order, but it has been "Forced to Standby." This state is persistent and manual; until an administrator releases the "Force to Standby" state, the device is ineligible to host the traffic group, effectively removing it from the top of the preference list.
* Auto Fallback: When "Auto Fallback" is enabled, the traffic group will automatically migrate back to a higher-priority device in the HA order as soon as that device becomes available and is in a healthy
"Standby" state.
* The Scenario Logic: 1. BIGIP-D is ineligible (Forced Offline/Standby).
2. BIGIP-B is the next highest device in the HA Order (Rank 2).
3. While BIGIP-B was rebooting, the traffic group would have failed over to BIGIP-C (Rank 3).
4. Once BIGIP-B finishes booting and joins the cluster in a "Standby" state, the Auto Fallback setting triggers.
5. Because BIGIP-B is higher in the HA Order than the current active device (BIGIP-C) and the only device above it (BIGIP-D) is ineligible, the traffic group fails back to BIGIP-B.
* HA Order Mechanism: When a traffic group is configured with an "HA Order" list, the system prefers to host the traffic group on the highest-ranking available device in that list (1 being the highest).
* The Impact of "Forced to Standby": BIGIP-D is the first choice in the order, but it has been "Forced to Standby." This state is persistent and manual; until an administrator releases the "Force to Standby" state, the device is ineligible to host the traffic group, effectively removing it from the top of the preference list.
* Auto Fallback: When "Auto Fallback" is enabled, the traffic group will automatically migrate back to a higher-priority device in the HA order as soon as that device becomes available and is in a healthy
"Standby" state.
* The Scenario Logic: 1. BIGIP-D is ineligible (Forced Offline/Standby).
2. BIGIP-B is the next highest device in the HA Order (Rank 2).
3. While BIGIP-B was rebooting, the traffic group would have failed over to BIGIP-C (Rank 3).
4. Once BIGIP-B finishes booting and joins the cluster in a "Standby" state, the Auto Fallback setting triggers.
5. Because BIGIP-B is higher in the HA Order than the current active device (BIGIP-C) and the only device above it (BIGIP-D) is ineligible, the traffic group fails back to BIGIP-B.
by Lynn at Aug 14, 2026, 05:00 PM
0
0
0
10
Comments
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Report Comment
Commenting
You can sign-up / login (it's free).