1Y0-204 CCA-V Citrix Virtual Apps and Desktops 7 Administration exam Questions and Answers

 According to the Citrix documentation2, the SDX platform is a multi-tenant appliance that supports multiple Citrix ADC instances. Each instance is fully isolated and has its own dedicated resources. The SDX platform allows administrators to create, manage, and monitor multiple instances from a single management interface.

The PowerShell command Get-Service -DisplayName *citrix* is used to display all the Citrix services installed on the Delivery Controller. This command filters services by their display name to only show those related to Citrix, which typically include various components of the Citrix Virtual Apps and Desktops 7 Deployment and Administration.

The Machine Utilization report in the Machine Details page shows the CPU, memory, disk, and network usage of the selected machine over time1. This can help the Citrix Administrator identify any resource bottlenecks or spikes that may affect the performance of the applications launched from the published desktop session. The other reports do not provide information about the machine’s resource utilization, but rather about the user’s connection, session, and application launch failures2.

1: Machine utilization | Director - Citrix Product Documentation 2: Troubleshoot user issues | Director - Citrix Product Documentation

 The administrator should negate the expression of the Responder policy to avoid the HTTP callout recursion issue. According to the Citrix documentation, “If you configure an HTTP callout policy that is bound globally, you must ensure that the policy expression does not match the callout request. Otherwise, the callout request will trigger the policy, resulting in a callout recursion.” The expression in option B ensures that the policy does not match the callout request by adding the NOT operator at the end.

https://docs.citrix.com/en-us/citrix-adc/13/appexpert/http-callout/http-callout-policy.html

Citrix documentation explains that to secure traffic between internal components (StoreFront ↔ Delivery Controllers), the administrator should enable HTTPS communication using internal domain-issued SSL certificates.

Why Domain SSL Certificates are correct:

Domain-issued certificates are trusted automatically by all domain-joined machines.

They cost nothing because they are issued by the company’s internal Certificate Authority (CA).

They secure communication between:

StoreFront servers

Delivery Controllers

They protect internal usernames, passwords, STA tickets, and XML communication without requiring public certification.

Thus, deploying:

✔ A domain SSL certificate on StoreFront

✔ A domain SSL certificate on Delivery Controllers

provides full internal encryption at minimal cost and minimal administrative effort.

Why the other options are incorrect:

Third-party SSL certificates (A and B) cost money, require external verification, and provide no additional benefit for internal-only communication.

Citrix documentation recommends third-party certificates only when externally exposed components (e.g., Citrix Gateway) must be trusted on unmanaged devices.

Documentation References

StoreFront Security Configuration → HTTPS and Certificate Requirements

Delivery Controller XML/HTTPS Configuration Guide

Citrix Virtual Apps and Desktops Security Hardening Guide

According to the policy priority and filtering, the Accounting users will match the policy “Accounting”, which has ‘Client Network Drives’ enabled and ‘Client Fixed Drives’ not configured. The policy “Baseline” will not apply because it has a lower priority. Therefore, the Accounting users will be able to access only the client network drives, and not the client fixed drives. This is confirmed by the Citrix documentation on policy filtering and precedence.

Option B is correct because spillover policies are applied on the GSLB virtual server level, not on the individual GSLB service level. Therefore, the user cannot have a backup for a subset of GSLB services1.

Option C is correct because the selection of a GSLB service is based on the load balancing method configured on the GSLB virtual server, which applies to all the GSLB services bound to it. The user cannot restrict the selection of a GSLB service from a subset of GSLB services for the given domain1.

Option A is incorrect because an administrator can define a backup for a backup Vserver in an active standby GSLB setup for a given GSLB domain by using the backup domain option2.

Option D is incorrect because a GSLB Vserver can load-balance multiple FQDNs by using the domain list option

According to the Citrix documentation1, when connection proxy is used as the site persistence method, the Subnet IP (SNIP) address of the appliance is used to source the traffic when the connection is proxied. This ensures that the response from the server goes back to the same appliance that proxied the request.

1: Connection Proxy

According to the Citrix Virtual Apps and Desktops 7 Advanced Administration guide1, the administrator can use custom access in Citrix Cloud to grant the contractor access to specific services and features, such as the Citrix Virtual Apps and Desktops Service. The administrator can also use the Delivery Group Administrator role in the Citrix Virtual Apps and Desktops Service to allow the contractor to deliver applications, desktops, and machines, and manage the associated sessions. This role has the minimum permissions required to administer the inventory application. The other roles are either too broad or too restrictive for the scenario.

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration course, Citrix Provisioning can reduce the total number of writes on the storage by using a single shared image that is streamed to multiple target devices. This eliminates the need to store multiple copies of the same image on the storage. The course also states that Citrix Provisioning can reduce the storage requirements by up to 90% compared to traditional methods1

1: CWS-215: Citrix Virtual Apps and Desktops 7 Deployment and Administration, Module 9: Implementing Citrix Provisioning, Lesson: Introduction to Citrix Provisioning, Slide 6.

Citrix Studio provides a feature called Limit Visibility, which allows administrators to hide specific published resources (apps or desktops) from chosen users or groups. This is the correct method to selectively exclude users from seeing or launching certain apps without removing them from the Delivery Group.

Correct Approach:

To prevent HR10 from seeing or accessing APP_A, the administrator should configure Limit Visibility so that only HR1–HR9 are allowed visibility for APP_A.

This ensures:

The entire HR group still receives all published apps

Only HR10 is restricted from APP_A

The Delivery Group configuration remains intact

Why the other options are incorrect:

A. Remove HR10 from the Delivery Group:This would remove HR10’s access to all Delivery Group applications, not just APP_A.

C. Remove APP_A from the Delivery Group:This removes the app for everyone, not just HR10.

D. Limit visibility on APP_A to HR10:This would assign visibility only to HR10, the opposite of what is needed.

Documentation References

Citrix Virtual Apps and Desktops → Application Publishing and Visibility

Citrix Studio → App Properties → “Limit Visibility” Feature

Citrix App Assignment Best Practices

The ns_allow expression always evaluates to true, which means it allows all users access through the vServer. The ns_disallow and ns_false expressions always evaluate to false, which means they deny all users access. The ns_true expression is not a valid policy expression1

1: Citrix ADC 13.0 - Policy Expressions

 Process Explorer is a tool that can be used to get further details on orphaned processes in the session. According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration course, Process Explorer can be used to “identify processes that are preventing a session from logging off” (Module 6: Troubleshooting User Connection Issues, Lesson: Troubleshooting Session Logon and Logoff Issues, Slide 8). Additionally, according to the Citrix Virtual Apps and Desktops 7 Administration Exam Guide, one of the objectives is to “use Process Explorer to identify orphaned processes” (Objective 6.3: Troubleshoot Session Logon and Logoff Issues). Therefore, Process Explorer is the correct answer.

Citrix Profile Management includes two key filtering policies that determine which users CPM will apply to:

Processed Groups — Only users in these groups will have their profiles managed by CPM.

Excluded Groups — Users in these groups will never be processed by CPM, even if they appear in Processed Groups.

Citrix documentation states:

If Processed Groups is enabled, only the groups listed are processed.

If a user belongs to an Excluded Group, CPM is disabled for that user regardless of other group memberships.

Users not listed in either policy will not be processed by CPM when Processed Groups is enabled.

Given the policy configuration:

✔ Product Marketing Team (Processed Group)

Members are processed.

✔ Human Resources Team (Not listed anywhere)

Since Processed Groups is enabled, HR members are not processed.→ Matches Answer C

✔ IT Team (Excluded Group)

Explicitly excluded.→ Not processed.

✔ Professional Sales Team (Excluded Group)

Explicitly excluded.→ Matches Answer D

Other options incorrectly contradict Citrix Profile Management logic.

Documentation References (no URLs)

Citrix Profile Management Administrator's Guide → “Processed Groups”

Citrix Profile Management Policy Reference → “Excluded Groups”

Citrix Profile Management GPO-Based Configuration Overview

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration course, team members who have access to their own admin partitions do NOT have Shell access by design. Shell access is only available for the default partition. Therefore, the team member cannot use aaad.debug or any other Shell commands from the CLI1

1: Manage | Citrix Virtual Apps and Desktops 7 2308

Citrix Profile Management includes two key filtering policies that determine which users CPM will apply to:

Processed Groups — Only users in these groups will have their profiles managed by CPM.

Excluded Groups — Users in these groups will never be processed by CPM, even if they appear in Processed Groups.

Citrix documentation states:

If Processed Groups is enabled, only the groups listed are processed.

If a user belongs to an Excluded Group, CPM is disabled for that user regardless of other group memberships.

Users not listed in either policy will not be processed by CPM when Processed Groups is enabled.

Given the policy configuration:

✔ Product Marketing Team (Processed Group)

Members are processed.

✔ Human Resources Team (Not listed anywhere)

Since Processed Groups is enabled, HR members are not processed.→ Matches Answer C

✔ IT Team (Excluded Group)

Explicitly excluded.→ Not processed.

✔ Professional Sales Team (Excluded Group)

Explicitly excluded.→ Matches Answer D

Other options incorrectly contradict Citrix Profile Management logic.

Documentation References (no URLs)

Citrix Profile Management Administrator's Guide → “Processed Groups”

Citrix Profile Management Policy Reference → “Excluded Groups”

Citrix Profile Management GPO-Based Configuration Overview

Option B is the correct answer because it uses the DROP action to block access to the URLs that match the BAD_URL pattern set. The other options use the RESET action, which only resets the connection but does not prevent access. Also, option C has a typo in the bind responder global command, which would cause an error. Option D has an invalid type argument for the bind responder global command, which should be DNS_REQ_OVERRIDE instead of DNS_REQ. For more information, see the following resources:

Manage | Citrix Virtual Apps and Desktops 7 2308

Applications | Citrix Virtual Apps and Desktops 7 2308

Citrix Virtual Apps and Desktops 7 Deployment and Administration (CWS …

CWS-215: Citrix Virtual Apps and Desktops 7 Deployment and …

EDUCATION CWS-215: Citrix Virtual Apps and Desktops 7 Administration On …

Typically, the migration of existing profiles to a new profile management system occurs during the user’s first logon after the policy has been applied, as this is when the user’s profile is first accessed and can be migrated.

https://docs.citrix.com/en-us/workspace-environment-management/current-release/user-interface-description/policies-and-profiles/citrix-upm-settings.html

Citrix Director includes application probing and health monitoring that categorizes issues into:

Warnings

Faults

Failures

According to Citrix’s monitoring definitions:

✔ An Application Fault refers to a failure that impacts functionality or causes loss of service or data.

Specifically, a fault indicates that the application:

Has experienced a significant failure

Cannot provide expected functionality

Has recorded an event indicating a serious problem

Needs administrative attention

This differs from:

Warnings (A) — non-critical issues that might lead to problems

Application unavailable (C) — a condition caused by machine/host failure

Probe failures (D) — failures detected through scheduled application probes and classified differently

Therefore, an Application Fault directly relates to loss of functionality or data, making B correct.

Documentation References

Citrix Director Monitoring Guide → Application Health States

Citrix Application Probing Documentation → Fault vs Warning Definitions

 When creating a custom scope, the Full Administrator role is not available because custom scopes are designed to limit administrators’ permissions to specific objects or tasks within the Citrix environment.

When EDT is disabled, ICA fallback communication occurs over TCP rather than UDP.

Remote users connecting through NetScaler Gateway reach internal Citrix resources using ICA over SSL.

Citrix documentation specifies that NetScaler Gateway communicates with clients using:

TLS/SSL over port 443, regardless of whether EDT is enabled or not.

This port must be opened on the perimeter firewall to allow:

Secure ICA proxy traffic

Authentication traffic

Connection establishment

STA ticket validation via Gateway

Why the other options are incorrect:

1494 — Raw ICA (not used externally when Gateway is in front).

2598 — Session Reliability port; also not used by external clients connecting via Gateway.

80 — Unencrypted HTTP (never appropriate for secure remote access).

NetScaler Gateway always requires SSL 443 for secure ICA proxy connections.

Documentation References

Citrix Gateway Deployment Guide → Ports and Protocols

ICA/HDX Network Port Requirements

Citrix Virtual Apps and Desktops → EDT and Fallback Behavior

The administrator needs to change the product edition in Citrix Studio to match the newly installed advanced licenses. This action ensures that the Citrix Virtual Desktops Site utilizes the correct licenses and resolves the issue with the evaluation license expiration error message.

Workspace Control allows users to reconnect to their disconnected sessions automatically when they roam between devices or reconnect after a network disruption. It is designed to provide a seamless user experience by maintaining the user’s session state, allowing them to pick up where they left off without starting a new session. This feature can be managed within the Citrix Virtual Apps and Desktops management consoles and is essential for scenarios where users need to maintain continuity in their work, such as in the given scenario where users leave work and expect to reconnect to their sessions later.

According to the Prepare to install article, the First-Time wizard automatically pops up when the appliance is configured with the default IP address (192.168.100.1) or when licenses are not present on the appliance. Therefore, options C and D are correct. Options A and B are not related to the First-Time wizard.

Citrix Director provides a feature under the Trends section where administrators can configure and review application faults. This allows them to monitor and analyze applications that have crashed, helping to identify patterns or recurring issues.

According to the Citrix documentation, when you bind an interface to a VLAN, the native VLAN of the interface changes to the VLAN to which it is bound. In this scenario, the native VLAN of interface 1/1 was 40 before the command was executed, so it remains 40 after the command is executed. The command does not change the native VLAN of the interface, only the VLAN to which it is bound. Therefore, the correct answer is B.

 According to the Citrix documentation, the -denySSLReneg parameter specifies the type of SSL renegotiation that the Citrix ADC denies. The possible options are:

NONSECURE: Deny renegotiation requests from a client if the initial handshake between the Citrix ADC and the client is not secure. A secure handshake is one in which both parties prove their identities to each other by presenting valid certificates.

FRONTEND_CLIENT: Deny renegotiation requests from a client on a front-end SSL connection, regardless of whether the initial handshake is secure or not. A front-end SSL connection is one in which the Citrix ADC communicates with the client over SSL.

ALL: Deny all renegotiation requests from a client on a front-end SSL connection and from a server on a back-end SSL connection. A back-end SSL connection is one in which the Citrix ADC communicates with the server over SSL.

NO: Allow all renegotiation requests.

Therefore, the correct answer is A and C.

 The administrator can add the partition information to the SNMP traps by using the command set snmp alarm partition-name on the Citrix ADC. This command enables the Citrix ADC to include the name of the partition that generated the trap in the SNMP trap message. This way, the administrator can easily identify which partition has the load balanced virtual server that is down. The other options are not relevant or effective for this purpose. See SNMP alarms for more details.

 The Dashboard view in Citrix Director provides a real-time graphical representation of the health and usage of the site, including the database services, the license server, and any hypervisor-hosting connections12

1: Director - Citrix Product Documentation 2: Director Dashboard Explained - Citrix Blogs

According to the Citrix Cloud documentation1, a Citrix Administrator needs to supply the following information when creating a silent installation of the Cloud Connector:

The customer ID of the Citrix Cloud account for which the administrator is installing the Cloud Connector.

The client ID and secret of the secure API client the administrator wants to use to install the Cloud Connector.

The resource location ID for the resource location that the administrator wants to associate with the Cloud Connector. If the administrator does not supply this value, Citrix Cloud uses the ID of the default resource location.

Therefore, the correct answer is C, Resource Location ID.

1: Install Cloud Connectors from the command line | Citrix Cloud

In the scenario described, when network connectivity to Citrix Cloud is lost, the Local Host Cache (LHC) feature allows one of the Citrix Cloud Connectors at the resource location to become the primary broker. This enables it to broker new sessions and manage existing HDX connections using the LHC, ensuring continuity of service during outages

According to the Proxy modes | Citrix Secure Web Gateway 12.1 - NetScaler document, to configure a Content Switching virtual server for implementing the Citrix Secure Web Gateway in the transparent proxy mode, the command should be:

add cs vserver < name > PROXY < ipaddress > < port >

The document also provides an example of the command:

add cs vserver swgVS PROXY 192.168.10.1 80

Therefore, the correct answer is C, which matches the format and the example given in the document. The other options are incorrect because they either use asterisks (*) instead of an IP address, or they do not specify a port number.

 The Dashboard view in Citrix Director provides a real-time graphical representation of the health and usage of the site, including the database services, the license server, and any hypervisor-hosting connections12

1: Director - Citrix Product Documentation 2: Director Dashboard Explained - Citrix Blogs

The administrator received this error because they did not run the Add-PSSnapin Citrix* command before running the Get-BrokerSite PowerShell command. This is required to load the Citrix PowerShell snap-ins.

Typically, the migration of existing profiles to a new profile management system occurs during the user’s first logon after the policy has been applied, as this is when the user’s profile is first accessed and can be migrated.

https://docs.citrix.com/en-us/workspace-environment-management/current-release/user-interface-description/policies-and-profiles/citrix-upm-settings.html

 The New-BrokerRebootScheduleV2 cmdlet creates a new reboot schedule for a machine catalog or a delivery group. The -StartTime parameter specifies the start time of the reboot schedule in 24-hour format. The -RebootDuration parameter specifies the time interval in minutes between each machine reboot. The -Frequency parameter specifies how often the reboot schedule occurs. The -DesktopGroupName parameter specifies the name of the delivery group to apply the reboot schedule to. The -Enabled parameter specifies whether the reboot schedule is enabled or not12

The dig +trace command can be used to resolve DNS requests by tracing the path from the root name servers to the authoritative name servers. This can help identify any issues with DNS resolution or delegation. The nslookup command can also be used to query DNS records, but it does not provide the trace option. The curl command can be used to transfer data from or to a server, but it does not resolve DNS requests. The ping command can be used to test the connectivity and latency between two hosts, but it does not resolve DNS requests.

The Control layer contains the Site database in a Citrix Virtual Apps and Desktops Architecture model. The Site database stores the running site configuration, plus the current session state and connection information. The Access layer contains the components that users need to connect to their apps and desktops, such as StoreFront and Citrix Gateway. The User layer contains the user profiles, policies, and data. The Resource layer contains the machines that host the apps and desktops, such as VDAs and hypervisors

 MAC-based forwarding (MBF) can be used to avoid multiple route/ARP lookups and to avoid asymmetrical packet flows. MBF caches the MAC address of the upstream router that forwarded the client request to the appliance. When a reply is received, it is passed through to the same router that sent the client request without going through any route lookup

The Citrix Application Delivery Management appliance, when used with Citrix Director, allows administrators to monitor various aspects of the infrastructure. It provides detailed insights into latency and bandwidth effects for specific user sessions ©, average ICA round trip time for specific user sessions (D), and peak concurrent total sessions for specific applications and desktops (E), enhancing the ability to manage and optimize the Citrix environment.

The Resource Utilization view in Citrix Director accesses historical trend information of CPU, memory, and disk latency for each machine running the VDA. This view helps the administrator to monitor the resource consumption and performance of the machines1

1: Monitor historical trends across a site | Director

Machine Creation Services (MCS) is suitable for deploying a large number of virtual desktops with low impact on network infrastructure. MCS allows for user-installed applications and persistency by using differencing disks and personal vDisks.

 According to the IBM documentation1, the Corrupt qualifier is used to modify the HTTP header of an HTTP request. The Corrupt qualifier changes the current value to a different value for a request or response header. If a value exists for the header, then this value is changed equivalent to a regular expression search and replace.

The Citrix Universal Generic Printer is a special type of auto-created printer that uses the Citrix Universal Print Driver and does not require any printer drivers to be installed on the server. It can reduce the number of native drivers being used within the Site infrastructure. To use this feature, the administrator must enable the Auto-create generic universal printer policy setting

 Installing the Cloud Connector on a machine template (before cloning) is not supported. If you clone a machine with the Cloud Connector installed, the Cloud Connector services won’t run and the machine can’t connect to Citrix Cloud1. Therefore, the administrator should provision each machine from a cloned machine template and install the Cloud Connector software on them. This way, the Cloud Connectors can communicate with Citrix Cloud and register with the same resource location2.

1: Cloud Connector Installation | Citrix Cloud 2: Install Cloud Connectors from the command line | Citrix Cloud Government

According to the Citrix documentation, Citrix Director supports exporting reports in the following formats: PDF, XLS, and CSV. DOC and TXT are not supported. See Export reports and SCOM alerts for more details.

Without a bound SSL certificate, the SSL virtual server cannot establish secure connections and will be in a DOWN state.

According to the Citrix documentation, “To enable SSL offloading for a virtual server, you must bind an SSL certificate to the virtual server.”

The image you sent shows the configuration commands for setting up an SSL virtual server and services. However, there is no command to bind an SSL certificate to the virtual server.

Therefore, the correct answer is D. The SSL Certificate is NOT bound to the virtual server.

https://docs.citrix.com/en-us/citrix-adc/13/ssl/ssl-offload-howto.html

 According to the Citrix documentation, automatic HA synchronization will fail if the primary and secondary Citrix ADCs have different build versions. The build versions must be the same for the configuration to be synchronized. A manual synchronization, a configuration change to the primary Citrix ADC, or a force failover will not affect the automatic HA synchronization1

1: Citrix Virtual Apps and Desktops 7 Deployment and Administration - High Availability

According to the Citrix documentation1, an HTTP-ECV monitor can be used to check the availability of a web server by sending an HTTP request and expecting a specific keyword in the response. The keyword can be specified in the Special Parameters - Receive String field. This monitor can ensure that the web server is not only responding, but also delivering the expected content.

The Citrix Workspace Control settings can be modified in the StoreFront console to enable or disable the automatic reconnection of applications and desktops as users move between devices1. This feature is not available in Citrix Studio, Group Policy, or Citrix Workspace app.

 The minimum built-in delegated administration role required to create an Application Group is the Delivery Group Administrator. This role has the necessary permissions to manage application groups within a delivery group1.

Citrix XML Service Trust is a security setting that determines whether StoreFront trusts communication from Delivery Controllers. Citrix documentation states that this trust must be enabled when authentication relies on credentials that must be securely forwarded or delegated through StoreFront and Delivery Controllers.

The authentication features that require XML Service Trust to be enabled are:

✔ A. Pass-through Authentication

This method allows the user’s Windows credentials to be automatically passed from the endpoint to StoreFront and then to Delivery Controllers.

This process requires StoreFront to trust the Delivery Controllers for credential delegation.

✔ D. Pass-through from NetScaler Gateway

When Gateway authenticates the user and passes credentials or tokens to StoreFront, StoreFront must trust the XML service on the Delivery Controllers to validate user identity securely.

✔ E. Smart Card Authentication

Smart card credentials contain certificate-based identities that StoreFront must securely trust and forward to the Delivery Controllers. This requires XML trust between components.

Why the other options are incorrect:

B. Smart AccessSmartAccess is a Citrix Gateway feature based on SmartControl policies and does not rely on XML service trust.

C. HTTP BasicThis uses direct credential submission; it does not require XML trust.

Documentation References

StoreFront Authentication and XML Trust Requirements

Citrix Delivery Controller XML Communication Security

Citrix Virtual Apps and Desktops Authentication Methods Overview

 Featured App Groups in Citrix Virtual Apps and Desktops can be created based on Application names, Keywords, and Application categories. This allows administrators to organize and highlight applications for users based on these criteria

The issue is caused by the policy expression of the no_chunk_pol being ‘true’ and ‘NOT HTTP.REQ.IS_VALID’. This means that the policy will always be true and thus, always be invoked, preventing the other policy from being used. This is explained in the Citrix Virtual Apps and Desktops 7 Deployment and Administration (CWS-215) course, under the section “Load Balancing Virtual Server Rewrite Policy Binding”.

Application Lingering allows applications to stay open for a configurable amount of time after a user closes them, which can reduce application launch times in subsequent sessions.

 CDF Control is a tool that can be used to collect information to investigate issues with session performance. CDF Control allows the administrator to enable and disable tracing, collect trace logs, and analyze them using Citrix Scout or Citrix Insight Services

According to the Citrix Secure Web Gateway 12.1 documentation1, Citrix Secure Web Gateway (SWG) is a cloud-delivered service that provides secure access to web and SaaS applications, globally. It provides a complete stack of security capabilities, such as Secure Web Gateway, Cloud Access Security Broker, Malware Protection with Sandboxing, Intrusion Prevention and Detection Systems, and Data Loss Prevention. Citrix SWG can intercept and inspect all the traffic, including SSL/TLS, coming in and going out of the enterprise network. It can also block access to URLs identified as serving harmful or insecure content, and identify users who are accessing malicious websites. Citrix SWG can be deployed as a proxy on a Citrix ADC appliance at the edge of the network. The other options are not relevant for this scenario, as they do not provide the same level of security and visibility as Citrix SWG.

According to the Citrix documentation1, the weight option assigns a numerical weight to a service. The higher the weight, the more requests the service can handle. By default, the weight is 1, which means equal distribution of requests. To make the new servers receive twice the connections of the old servers, the administrator needs to assign a weight of 2 to the services attached to the new servers.