1Y0-371 · Question #106
Scenario: A customer would like to configure a single NetScaler Gateway that facilitates access to XenMobile and XenApp/XenDesktop resources from iOS and Android mobile devices. The customer also…
The correct answer is B. Policy 1; StoreFront. See the full explanation below for the reasoning.
Question
Scenario: A customer would like to configure a single NetScaler Gateway that facilitates access to XenMobile and XenApp/XenDesktop resources from iOS and Android mobile devices. The customer also plans for users to access XenApp and XenDesktop resources by using a web browser from other endpoints. The following Session Policies and expressions have been configured on NetScaler:
- Policy 1: REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver &&
REQ.HTTP.HEADER Referer EXISTS
- Policy 2: REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver &&
REQ.HTTP.HEADER X-Citrix-Gateway EXISTS A Citrix Engineer is asked to create a new Session Profile for users accessing resources through web browsers on their endpoint devices. The profile should be bound to __________ and direct users to __________. (Choose the correct set of options to complete the sentence.)
Options
- APolicy 1; the XenMobile Server
- BPolicy 1; StoreFront
- CPolicy 2; the XenMobile Server
- DPolicy 2; StoreFront
How the community answered
(29 responses)- A3% (1)
- B69% (20)
- C10% (3)
- D17% (5)
Community Discussion
5
Luis F.Dec 12, 2025The answer is B, Policy 1 bound to StoreFront. Policy 1 matches requests where the User-Agent does NOT contain CitrixReceiver and a Referer header exists, which is exactly the fingerprint of a web browser hitting the gateway, and web browser sessions for XenApp and XenDesktop get routed to StoreFront, not XenMobile Server.
Orla P.Dec 13, 2025Good call on the User-Agent logic, though it is worth flagging that the Referer check can trip people up on direct-type bookmarks and certain kiosk browsers that strip that header, so test that edge case in your lab before you count on it in production.
Prof. SaraDec 12, 2025Policy 2 tempts you since Receiver traffic feels "mobile," but web browsers hit Policy 1, bound to StoreFront. Answer B.
Orla P.Dec 13, 2025Right call, and the trap is that candidates read "Receiver" and assume native client when the question stem quietly says the user opened a browser, which puts them squarely under the StoreFront-bound policy before Receiver even enters the picture.
Orla P.Dec 21, 2025Thought Policy 2 at first, but the browser User-Agent and Referer header combo nails Policy 1 pointing to StoreFront.