Free Citrix Certified Professional - Virtualization (CCP-V): Citrix Virtual Apps and Desktops 7 Advanced Administration practice test: 30 questions with answers

The Local Host Cache on a Delivery Controller keeps a cached copy of site configuration so brokering can continue during a database outage, although some operations are limited. Profile streaming handles user profile files, the Session Recording Agent captures sessions, and pass-through authentication handles sign-on, so none of them keeps brokering running.

A SQL Server Always On availability group and an active-passive Citrix Gateway pair both provide a standby that takes over when the primary fails. A lone gateway and a database sharing a disk with a VDA image leave a single point of failure in place.

Global server load balancing on Citrix ADC resolves one name to whichever site is available, so clients fail over without changing their settings. Local Host Cache only keeps a controller brokering during a database outage, and profile exclusions and recording storage do not steer users between sites.

The site database on SQL Server stores machine catalogs, delivery groups and related site configuration, so it is central to recovery. Director is a monitoring console, the Local Host Cache sits on Delivery Controllers rather than VDAs, and the Workspace app stores only client-side preferences.

VDAs register with the Delivery Controllers listed in their configuration, so the site keeps brokering when one controller is patched or fails. Director is a monitoring console rather than a registration point, a single delivery group adds no controller redundancy, and moving the site database onto Director does not remove the controllers' role.

SmartAccess lets Citrix Gateway pass access tags, based on endpoint analysis, to the Delivery Controller, which then filters what each session can launch. A second store or a shared password does not evaluate device trust, and multimedia redirection concerns media playback rather than access control.

The STA issues session tickets that authorize a gateway-brokered ICA connection to a specific VDA, keeping internal addresses hidden from the client. The other options describe profile storage, Director monitoring and endpoint caching, none of which are STA functions.

StoreFront uses its internal and external beacons to decide whether a client is on the internal network, so a wrong beacon setting sends internal users through the gateway. The store count, VDA timeouts and legacy Web Interface mode do not control that routing decision.

Delegated Administration in Citrix Studio uses administrators, roles and scopes, so helpdesk staff can manage only the delivery groups in their scope. A shared account removes accountability, the Full Administrator role grants unnecessary rights, and local rights on controllers are broader than the task needs.

Domain pass-through reuses the Windows sign-in credentials on domain-joined devices so users are not prompted again. Anonymous access does not authenticate users to private resources, per-application passwords defeat single sign-on, and Director is a monitoring console rather than a store sign-in method.

In Citrix policies, priority 1 is the highest, so the allow setting from Policy A takes effect over the lower-priority prohibition. Citrix does not average conflicting values, does not treat a higher number as overriding, and does not block sessions because of policy conflicts.

Profile streaming retrieves profile files from the user store on demand, which shortens logon for large profiles. Keeping the profile only on the endpoint, caching it in the site database and deleting files at logoff are not what streaming does.

Profile Management exclusion lists keep named folders out of the synchronized user store, which fixes slow logoff and wasted storage. A different user store path does not change what is synced, mandatory profiles remove personal settings entirely, and a StoreFront store only changes the app catalog.

The adaptive transport setting uses Enlightened Data Transport (EDT), a UDP-based protocol, where supported and falls back to TCP otherwise. Profile streaming affects profile file retrieval, multimedia redirection decodes video on the endpoint rather than the server, and browser content redirection moves web rendering, so none of them is the transport choice.

WEM agents keep a local cache of the last configuration they received, so they can still apply settings when the Infrastructure service is unavailable. Blocking logons and fetching settings from Director or the Delivery Controller do not match how WEM delivers its configuration.

CPU spike protection in WEM limits processes that consume excessive CPU, protecting interactive users without changing the image. Folder redirection, printer actions and session pre-launch deal with data locations, printing and session start-up rather than CPU use.

Process optimization in WEM sets CPU priority for named processes, which keeps interactive sessions responsive. Profile streaming, multimedia redirection and session recording handle profile retrieval, media playback and session capture rather than process scheduling.

WEM registry entry actions write registry values for assigned users at logon, so the same setting follows them across VDAs without changing the image. Director dashboards report on performance, the Local Host Cache keeps brokering running during database outages, and Session Recording policies decide which sessions are captured.

Disabling SSL 3.0 and TLS 1.0 and requiring TLS 1.2 or later are standard hardening steps. SSL 2.0 is a broken protocol, and a certificate whose name does not match the host breaks identity checks, so neither belongs in a hardened gateway.

App protection policies, such as anti-keylogging and screen capture protection, block endpoint software from capturing input and screen content during the session. Session recording only keeps a record of activity, while profile exclusions and SmartAccess tags do not stop capture.

The Session Recording Agent is installed on the VDA, where it captures the session and sends it to the Session Recording server. The Player is used to review recordings, Director's HDX Insight is a monitoring feature, and a Gateway session policy controls connection behavior rather than recording.

Recording policies can target specific user groups, so only contractor sessions are captured and the rule stays central. Recording everything and deleting later still records employees, recording on controllers captures nothing because the agent lives on VDAs, and notifications inform users without choosing who is recorded.

Director's logon breakdown, Citrix Scout diagnostics and event logs gather evidence without altering the environment. Recreating the site database and changing every policy at once would alter state and hide the real cause.

Changing several variables at once leaves the real cause unknown, so good methodology changes one variable at a time and verifies each result. The other options invent requirements that are not part of standard troubleshooting practice.

Defining the symptom and its scope first narrows the search to the components involved. Replacing images, restarting every controller or escalating without data skip evidence gathering and can destroy the state needed to find the cause.

The Citrix Broker PowerShell SDK exposes site configuration and machine state through cmdlets, so scripts can query delivery groups and catalogs. The certificate binding page, the StoreFront wizard and the firewall editor manage other components and do not report brokered site data.

Cloud Connectors make outbound connections to Citrix Cloud, so no inbound internet rule is needed. Inbound sessions to VDAs, public inbound exposure of the connectors and a VPN ending on Director do not describe how Cloud Connectors connect.

Citrix Cloud runs the management control plane while VDAs and other workloads stay in the resource location, and Citrix recommends at least two Cloud Connectors per location for redundancy. Cloud Connectors run on Windows servers rather than Linux hosts in a DMZ, and Citrix Cloud does not require local accounts on each VDA.

Citrix Cloud can federate administrator sign-in with Azure AD (Microsoft Entra ID), so the company directory stays the identity source. Shared local accounts, StoreFront as an identity source and VDA local accounts do not provide directory-based sign-in for Citrix Cloud.

A resource location is the customer-side location that holds VDAs, hypervisor connections and related resources, reached through Cloud Connectors. The control plane is hosted by Citrix, an identity provider authenticates users, and an access policy decides who receives which resources.