1Y0-241 practice question 4 of 25

Scenario: A Citrix Administrator configured Citrix ADC load balancing to send requests to one of three identical backend servers. Each server handles…

Full set: 112 questions
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 vServer 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?
Answer options
A: Disable the backend service entity targeted for change.
B: Disable the backend server entity targeted for change. Correct answer
C: Disable the load-balancing vServer.
D: Unbind the correct server entity from the load-balancing vServer.
Correct Answer:
B. Disable the backend server entity targeted for change.
Explanation

The most efficient method is to disable the backend server entity. In a Citrix ADC configuration, a server entity represents the physical or virtual machine. Multiple service entities, each representing a specific protocol or port, can be associated with a single server entity. By disabling the server entity, the administrator performs a single action that causes the Citrix ADC to mark all associated services as DOWN. This effectively and immediately removes the entire server from the load-balancing rotation for all protocols. This approach is more efficient than disabling each service individually, especially when a server handles multiple protocols as stated in the scenario.

Why Incorrect

A. Disabling each service individually is less efficient. The scenario implies multiple protocols, which would require disabling multiple service entities for a single server.
C. Disabling the load-balancing vServer would take the entire service offline, impacting all three backend servers and violating the requirement to not affect other resources.
D. Server entities are not bound directly to a load-balancing vServer; service or service group entities are. Therefore, this action is technically invalid.

References

1. Citrix ADC Documentation - Enable or disable entities: In the section "Enable or disable a server

" the documentation states

"When you disable a server

the ADC stops monitoring its health and does not forward requests to any of the services that are configured on that server." This confirms that disabling the server entity is a single

comprehensive action that affects all its associated services.

Source: Citrix Product Documentation

"Citrix ADC 13.1"

Load Balancing > Managing your setup > Enable or disable entities.

2. Citrix ADC Command Reference - disable server: The command disable server [-graceful ( YES | NO )] is used to take a server out of service. The documentation for this command confirms its function is to disable a specific server. The -graceful YES option ensures existing connections are handled before the server is marked as DOWN

which aligns with the scenario's requirement to not impede responses.

Source: Citrix Developer Documentation

"Citrix ADC 13.1 Command Reference"

Basic Commands > server > disable server.

3. Citrix ADC Documentation - Load Balancing Entities: The documentation on load balancing entities clarifies the hierarchy. A virtual server receives traffic

which it distributes to services. A service represents an application running on a server. A server is the object representing the backend machine's IP address. Disabling the parent 'server' object is the most efficient way to affect all child 'service' objects associated with it.

Source: Citrix Product Documentation

"Citrix ADC 13.1"

Load Balancing > Load balancing entities

concepts

and terminology.

Scroll to Top