Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Citrix Exam 1Y0-241 Topic 12 Question 78 Discussion

Actual exam question for Citrix's 1Y0-241 exam
Question #: 78
Topic #: 12
[All 1Y0-241 Questions]

Scenario: A Citrix Administrator is configuring a Citrix ADC high availability (HA) pair with an existing primary Citrix ADC with all resources configured. The administrator adds the secondary Citrix ADC in HA and discovers that the configuration on the existing primary was removed and is now the secondary Citrix ADC in the HA pair.

Which two configurations could the administrator have used to prevent this from happening? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

Forcing the node to stay secondary works on both standalone and secondary nodes. On a standalone node, you must use this option before you can add a node to create an HA pair. When you add the new node, the existing node stops processing traffic and becomes the secondary node. The new node becomes the primary node.

https://docs.citrix.com/en-us/citrix-adc/current-release/system/high-availability-introduction/forcing-a-secondary-node-to-stay-secondary.html

On a standalone node, you must use this option before you can add a node to create an HA pair. When you add the new node, the existing node continues to function as the primary node, and the new node becomes the secondary node.

https://docs.citrix.com/en-us/citrix-adc/current-release/system/high-availability-introduction/forcing-the-primary-node-stay-primary.html


Contribute your Thoughts:

Arleen
5 months ago
That's a good point, it's important to have monitoring on all devices in the HA pair.
upvoted 0 times
...
Fabiola
5 months ago
I bet the admin was like, 'Wait, what? My primary Citrix ADC just pulled a Darth Vader on me!' Gotta love those unexpected plot twists.
upvoted 0 times
...
Mollie
5 months ago
Monitoring all the interfaces, as in option C and D, is also a good idea. Can't have those secondary devices slacking off, you know?
upvoted 0 times
...
Catarina
5 months ago
Hmm, I'd say both A and B are the way to go. Locking in those roles is crucial, unless you want a Citrix ADC identity crisis on your hands.
upvoted 0 times
Selma
4 months ago
Don't forget to enable HA monitoring on all primary device interfaces as well.
upvoted 0 times
...
Tamra
4 months ago
HA monitoring on all secondary device interfaces should also be enabled.
upvoted 0 times
...
Wilburn
4 months ago
Definitely, and setting the secondary Citrix ADC to stay secondary is just as crucial.
upvoted 0 times
...
Daryl
4 months ago
I agree, setting the primary Citrix ADC to stay primary is important.
upvoted 0 times
...
...
Otis
5 months ago
I also believe enabling HA monitoring on all secondary device interfaces could have helped.
upvoted 0 times
...
Dorian
5 months ago
Option A seems like the obvious choice here. You gotta keep your primary Citrix ADC in the driver's seat, am I right?
upvoted 0 times
...
Ling
5 months ago
Wait, the primary became the secondary? That's like a secret agent switching sides - unexpected and kind of hilarious!
upvoted 0 times
Thora
5 months ago
Maybe they should have enabled HA monitoring on all primary device interfaces.
upvoted 0 times
...
Erinn
5 months ago
I know right, it's like a plot twist in a movie!
upvoted 0 times
...
...
Clorinda
6 months ago
Yes, that would have prevented the configuration from being removed.
upvoted 0 times
...
Arleen
6 months ago
I think the administrator should have set the primary Citrix ADC to stay primary.
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