In preparation for a maintenance task, an LTM Specialist performs a "Force to Standby" on LTM device Unit 1. LTM device Unit 2 becomes active as expected. The maintenance task requires the reboot of Unit 1. Shortly after the reboot is complete, the LTM Specialist discovers that Unit 1 has become active and Unit 2 has returned to standby.
What would cause this behavior?
Suggested Answer: C
Get Premium 303 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
LA
Latrice
10 months ago
I agree, D seems like the right answer here.
FE
Felix
10 months ago
I thought Auto Failback only applied to traffic groups?
EM
Emiko
11 months ago
Definitely, it's probably the redundancy state preference.
MA
Matthew
11 months ago
Wait, so Unit 1 just takes over after a reboot? That's surprising!
JA
Jacquelyne
11 months ago
Sounds like Unit 1 has a higher priority set.
IL
Iluminada
11 months ago
I think I read that if a device group is set to Auto Failback, it could cause this behavior. But I'm not confident if it's the device group or traffic group that's relevant here.
LO
Loreta
12 months ago
I feel like the answer might be related to the default device settings. Wasn't there something about how the default device impacts failover?
VI
Vincenza
12 months ago
This scenario seems similar to a practice question about failover behavior. I think Auto Failback could be involved here, but I can't recall the specifics.
YU
Yuriko
12 months ago
I remember studying redundancy preferences, but I'm not entirely sure if it's the device group or high availability settings that take precedence.
TO
Torie
1 year ago
I'm pretty confident I know the answer to this one. It's got to be option C - the traffic group is set to Auto Failback with Unit 1 as the default device.
JU
Jules
1 year ago
Okay, I think I know what's going on here. The key is to look at the redundancy state preferences and any auto failback settings that might be configured.
BA
Barbra
1 year ago
Hmm, I'm a bit confused by the question. I'll need to review my notes on LTM device failover and redundancy to try to determine the right answer.
QU
Quiana
1 year ago
This seems like a tricky one. I'll need to think through the high availability and redundancy settings to figure out what could be causing the behavior.
KA
Kaycee
1 year ago
That's a good point, maybe C is the correct answer after all.
JE
Jerlene
1 year ago
But wouldn't Auto Failback in a traffic group make more sense?
OL
Ollie
1 year ago
I'm leaning towards B actually.
KA
Kaycee
1 year ago
I disagree, I believe it's D.
LE
Leandro
1 year ago
I'm going with C. It makes the most sense given the scenario. Though I wonder if the LTM Specialist has a history of accidentally pressing the 'Activate Me' button on Unit 1.
MI
Mitsue
1 year ago
Yeah, it's important to double check before making any changes to avoid unexpected behavior.
DA
Dana
1 year ago
Maybe the LTM Specialist needs to be more careful with that 'Activate Me' button on Unit 1.
DA
Dalene
1 year ago
I think it's C too. Auto Failback would explain why Unit 1 became active again.
GL
Glenn
1 year ago
Wait, isn't this just a case of Murphy's Law in action? Unit 1 was supposed to be the standby, but it just had to go and become the active one.
CH
Chantell
1 year ago
C) A traffic group is configured with Auto Failback, and Unit 1 is the default device.
BA
Barrett
1 year ago
A) Unit 1 is set with the redundancy state preference of active in devices groups.
DU
Dusti
1 year ago
Definitely D. The auto failback on the device group is the culprit here, not the traffic group.
HA
Halina
1 year ago
Hmm, I think it's C. The auto failback setting on the traffic group would make Unit 1 the active device after the reboot.
ET
Ettie
1 year ago
Yeah, that makes sense. Auto Failback would switch Unit 1 back to active after the reboot.
LA
Larue
1 year ago
I agree, C seems like the most likely option.
JE
Jerlene
1 year ago
I think the answer is C.