A server certificate is required for StoreFront to use HTTPS connections. A server certificate identifies the server and establishes trust between the server and the client. A client certificate is used to authenticate the client to the server, which is not necessary for StoreFront. An intermediate certificate is issued by a trusted root authority to another certificate authority, and is not used for server identification. A root certificate is the top-most certificate of the tree, and is used to validate the trustworthiness of the certificate authorities below it, but it is not used for server identification.

For more information, see  How to Generate and Install an SSL Certificate on a StoreFront Server for HTTPS connections  and  Securing StoreFront with HTTPS .

 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

To enable Citrix XML Service trust for user access within a Citrix Virtual Apps and Desktops infrastructure, the administrator must run the  Set-BrokerSite -TrustRequestsSentToTheXMLServicePort $true  PowerShell command from within a Controller.  This configures the site to trust requests sent to the XML Service port 1 .

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 methods 1

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

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration course description 1 2 , one of the objectives is to “Configure Citrix ADC to monitor and report on the health of your environment”. The course also covers how to use Citrix Application Delivery Management to monitor and manage multiple Citrix ADC instances.  According to the Citrix documentation 3 , Network Reporting on Citrix Application Delivery Management allows you to generate reports based on various metrics and events collected from the Citrix ADC instances. You can also configure thresholds and alerts for the reports, and specify the email addresses to receive the notifications. Therefore, the correct answer is D.

When StoreFront must integrate with a third-party portal , the portal typically acts as the external system that captures user credentials, handles primary authentication, and then passes those credentials (usually via HTTP headers or basic authentication mechanisms) to StoreFront.

Citrix documentation notes that HTTP Basic authentication is the method suited for integrations where StoreFront must accept credentials from an external portal or non-Citrix authentication framework. This method allows StoreFront to validate credentials passed programmatically from the third-party system.

Why not the other options?

Unauthenticated: This provides anonymous access and does not support integration with authenticated external portals.

Domain pass-through: Requires a Windows-integrated authentication flow, not compatible with third-party portals.

Pass-through from NetScaler Gateway: This applies only when authentication is performed via Citrix Gateway, not an external custom portal.

Therefore, HTTP Basic is the appropriate authentication method for third-party portal integration.

Documentation References:

StoreFront Authentication Methods Overview

StoreFront Third-Party Integration Scenarios (Authentication Requirements)

When deploying a Citrix Virtual Apps and Desktops Site with SQL database mirroring , Citrix requires that the collation setting used by the Site database must be explicitly set and must match the required Citrix standard. Citrix documentation states that the database collation must be case-insensitive and consistent between the principal and mirror SQL servers.

This collation is not automatically assigned by SQL Server when you create an empty database for mirroring. Therefore, administrators must manually configure the correct collation during initial creation. If the collation does not match Citrix requirements, the Site creation or Controller functionality may fail.

Other listed options (SQL version, database type, mirroring version) do not require manual configuration at database-creation time for Citrix Sites.

Documentation References:

Citrix Virtual Apps and Desktops Database Requirements → SQL Collation Requirements

Citrix Delivery Controller Installation Requirements → Database Mirroring Configuration