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.

To view license information in Studio, an administrator must have at least the Read Licensing delegated administration permission. The built-in Full Administrator and Read-Only Administrator roles have that permission1.

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 using Machine Creation Services, the Delivery Controller must communicate with the configured hosting connection (such as VMware, Hyper-V, Citrix Hypervisor, Nutanix AHV). This communication enables provisioning, power management, and information retrieval from the hypervisor.
Citrix documentation defines the Citrix Host Service as the Delivery Controller service responsible for:
* Managing hypervisor connections
* Sending provisioning and power-action commands
* Communicating with hosting infrastructure APIs
* Initiating VM creation and updates for MCS catalogs
The Citrix Broker Service manages session brokering, not hypervisor communication.
The Citrix Environment Test Service focuses on diagnostics.
"Citrix Hypervisor Service" is not a Citrix Delivery Controller service.
Therefore, the correct service enabling Controller-to-hypervisor communication is the Citrix Host Service.
Documentation References:
Citrix Virtual Apps and Desktops # Delivery Controller Services Overview Citrix Host Service Description within Hosting Connections

According to the Citrix documentation1, the correct syntax for adding a simple ACL rule is:
add simpleacl <aclname> <ALLOW | DENY> -srcIP <IPAddress> [-destIP <IPAddress>] [-TTL
<timeInSeconds>]
The correct syntax for adding an extended ACL rule is:
add ns acl <aclname> <ALLOW | DENY> -srcIP <IPAddress> [-destIP <IPAddress>] [-TTL
<timeInSeconds>]
Therefore, the correct answer is B, because it uses the extended ACL rule format and specifies the destination IP address of the load balancing virtual server (192.168.100.25) and the TTL value of 10 minutes (600 seconds).
1: https://docs.citrix.com/en-us/citrix-adc/13/networking/acl.html