New Year Sale ! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-425 Topic 2 Question 100 Discussion

Actual exam question for Cisco's 300-425 exam
Question #: 100
Topic #: 2
[All 300-425 Questions]

Refer to the exhibit.

A network engineer has identified that during a recent controller failure, several APs failed over to the tertiary controller instead of the secondary controller. The configuration from one of the APs is provided. Which design consideration led to the issue?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Carmen
2 months ago
Ah, the good old 'secondary controller at capacity' problem. The networking version of 'turning it off and back on again'!
upvoted 0 times
...
Malika
2 months ago
I bet the network engineer is regretting that 'set it and forget it' approach right about now. Shoulda kept a closer eye on those controllers!
upvoted 0 times
Ashlee
22 days ago
Exactly. The network engineer should have ensured proper failover configurations to prevent this issue.
upvoted 0 times
...
Edda
1 months ago
So the tertiary controller took priority because it's an HA-SKU controller, right?
upvoted 0 times
...
Isabelle
1 months ago
Definitely! Looks like the secondary controller was at capacity, causing the APs to fail over to the tertiary.
upvoted 0 times
...
Paola
2 months ago
APs failing over to the tertiary controller instead of the secondary? That's a major design flaw.
upvoted 0 times
...
...
Shonda
2 months ago
The tertiary controller being in the same subnet as the primary? That's just asking for trouble. Gotta keep those separate, people!
upvoted 0 times
Salena
1 months ago
The secondary controller being at capacity could also have caused the issue.
upvoted 0 times
...
Elizabeth
2 months ago
I agree, that's a design flaw waiting to happen.
upvoted 0 times
...
Franklyn
2 months ago
Yeah, having the tertiary controller in the same subnet as the primary is a big no-no.
upvoted 0 times
...
...
Jolene
2 months ago
I'm not convinced the tertiary controller being an HA-SKU is the issue. Wouldn't that actually provide more redundancy and stability?
upvoted 0 times
...
Arlette
3 months ago
Hmm, the secondary controller being at capacity seems like the most likely culprit here. Overloading can definitely cause failover issues.
upvoted 0 times
Timmy
1 months ago
Could be a network configuration issue then.
upvoted 0 times
...
Lili
1 months ago
D) The tertiary controller is in the same subnet as the primary controller.
upvoted 0 times
...
Trinidad
1 months ago
That makes sense, having a higher priority controller.
upvoted 0 times
...
Josphine
2 months ago
User 3: Maybe they should consider upgrading the capacity of the secondary controller.
upvoted 0 times
...
Caren
2 months ago
C) The tertiary controller is an HA-SKU controller, so it took priority.
upvoted 0 times
...
Sabra
2 months ago
Maybe the failover settings need to be adjusted.
upvoted 0 times
...
Valentin
2 months ago
B) The secondary controller is an SSO configuration.
upvoted 0 times
...
Lezlie
2 months ago
User 2: That could definitely cause the APs to failover to the tertiary controller.
upvoted 0 times
...
Osvaldo
2 months ago
I think the secondary controller was at capacity.
upvoted 0 times
...
Ruth
2 months ago
Yeah, that could definitely cause some problems.
upvoted 0 times
...
Jutta
2 months ago
A) The secondary controller was at capacity.
upvoted 0 times
...
...
Verlene
3 months ago
I think the issue was due to the tertiary controller being in the same subnet as the primary controller.
upvoted 0 times
...
Tawna
3 months ago
I disagree, I believe it was because the tertiary controller is an HA-SKU controller.
upvoted 0 times
...
Corrie
3 months ago
I think the issue was caused by the secondary controller being at capacity.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77