Scenario: A Citrix Administrator is enabling TLS Secure connections between the Cloud Connectors and on-premises StoreFront. After configuring the TLS certificate on all Cloud Connectors and…

Question

Options

• AConfigure Internet Information Services (IIS) on the StoreFront server to use HTTPS.
• BChange transport type to HTTPS in the StoreFront store DDC list.
• CConfigure Cloud Connectors to allow unsecured connections.
• DInstall Internet Information Services (IIS) on the Cloud Connector.

• A
  3% (1)
• B
  3% (1)
• C
  83% (24)
• D
  10% (3)

Explanation

Option C is correct because the Cloud Connectors were configured to enforce HTTPS-only, but on-premises StoreFront communicates with Cloud Connectors via HTTP by default for XML-based resource enumeration - disabling HTTP broke that internal communication path, and the fix is to re-enable unsecured connections on the Cloud Connectors so StoreFront can enumerate resources again. Option A is wrong because configuring IIS on StoreFront for HTTPS affects how end users access the StoreFront web interface, not how StoreFront's backend communicates with Cloud Connectors as DDC proxies. Option B is a plausible distractor, but changing the DDC transport to HTTPS in StoreFront would require additional certificate trust configuration and misaligns with Citrix's intended architecture where StoreFront-to-Cloud Connector XML traffic stays on HTTP within the internal network. Option D is wrong because Cloud Connectors use built-in services for XML communication - IIS is not a prerequisite on Cloud Connectors.

Memory tip: Picture two separate "tunnels" - one tunnel runs outside (Cloud Connector → Citrix Cloud) and must be encrypted with TLS, while the other runs inside (StoreFront → Cloud Connector) and defaults to plain HTTP. Locking down HTTP entirely closes the internal tunnel; you need to re-open it by allowing unsecured connections on the Cloud Connector side.

No community discussion yet for this question.