1Y0-231 · Question #58
Scenario: A Citrix Administrator configured Citrix ADC load balancing to send requests to one of three identical backend servers. Each server handles multiple protocols, and load balancing is set up…
The correct answer is D. Unbind the correct server entity from the load-balancing virtual server. Unbinding the server entity from the specific load-balancing virtual server is the most surgical option - it removes the target server from that particular VIP's traffic distribution without touching anything else on the ADC. The other server entities remain bound and continue…
Question
Scenario: A Citrix Administrator configured Citrix ADC load balancing to send requests to one of three identical backend servers. Each server handles multiple protocols, and load balancing is set up in round-robin mode. The current load-balancing setup on the Citrix ADC is:
- One load-balancing virtual server with one externally accessible VIP One service created for
each protocol type
- One server entity for each backend resource
- During business hours, the administrator wants to make changes to one backend server without
affecting the other servers What is the most efficient way for the administrator to ensure that all traffic is routed away from the server without impeding responses from other resources?
Options
- ADisable the backend server entity targeted for change.
- BDisable the load-balancing virtual server.
- CDisable the backend service entity targeted for change.
- DUnbind the correct server entity from the load-balancing virtual server.
How the community answered
(26 responses)- A4% (1)
- B12% (3)
- C4% (1)
- D81% (21)
Explanation
Unbinding the server entity from the specific load-balancing virtual server is the most surgical option - it removes the target server from that particular VIP's traffic distribution without touching anything else on the ADC. The other server entities remain bound and continue serving requests uninterrupted.
Why the distractors are wrong:
- A (Disable the server entity): Disabling a server entity has global scope - it takes the server offline across all services and virtual servers on the ADC that reference it, not just the one being modified. This risks collateral impact on unrelated configurations.
- B (Disable the LB virtual server): This kills the entire VIP, dropping traffic to all three backend servers simultaneously - exactly the opposite of the goal.
- C (Disable the service entity): Since one service exists per protocol type (not per server), disabling it removes that protocol from all three servers at once, not just the targeted one.
Memory tip: Think of it as a hierarchy of blast radius - disable VIP > disable service > disable server > unbind. When you need to isolate one server from one VIP, always reach for the most targeted action: unbind, not disable.
Topics
Community Discussion
No community discussion yet for this question.