1Y0-250 · Question #51
Which configuration option should an administrator select to pass users' credentials to a file share in a NetScaler Gateway environment?
The correct answer is C. Single sign-on with Windows. See the full explanation below for the reasoning.
Question
Which configuration option should an administrator select to pass users' credentials to a file share in a NetScaler Gateway environment?
Options
- ALocal LAN-Access
- BSingle sign-on to a domain
- CSingle sign-on with Windows
- DSingle sign-on to Web applications
How the community answered
(19 responses)- B11% (2)
- C84% (16)
- D5% (1)
Community Discussion
8The answer is C, Single sign-on with Windows, and the reason should be obvious once you think about what a file share actually is. File shares run over SMB and authenticate with Windows credentials, meaning Kerberos or NTLM, not HTTP forms or some web app handshake. Single sign-on with Windows is the setting that tells NetScaler Gateway to forward the user's Windows credentials down to those SMB resources so users do not get a second login prompt when they hit a network share. The other options are for completely different purposes, web app SSO handles HTTP-based authentication, domain SSO is about the initial logon process, and LAN access is a network routing mode, none of which have anything to do with authenticating to a file share.
Worth adding that the Citrix documentation places this setting in the session profile under the Published Applications tab, so the exam may test the exact configuration path, not just the concept.
C is the one you want here, though I have seen people burn time on D because "web applications" sounds plausible when file shares are in play. Single sign-on with Windows is specifically what passes credentials through to a file share in a NetScaler Gateway setup, so lock that in.
Bao nailed it, and if you want a quick anchor for the real thing, the phrase "file share" in the stem is your signal to stop entertaining web application options entirely, since that SSO with Windows is doing the credential handoff that makes the share accessible without a second login prompt.
Took me a second on this one because I kept second-guessing myself between B and C, but once I remembered that Windows file shares use NTLM or Kerberos and you need the Gateway to hand off those Windows credentials natively, C clicked right into place. I had actually seen this exact scenario at a job years back where users kept getting prompted twice for credentials on a mapped drive, and the fix was enabling Single sign-on with Windows, so seeing it on the exam felt like free points by the time I sat down.
Going with A on this one and I feel pretty solid about it. The Local LAN-Access setting in the NetScaler Gateway client is specifically what controls whether the client can route traffic to resources on the local network, and a file share sitting on the internal LAN is exactly that kind of resource. Without that option enabled, the tunnel intercepts everything and you never get the credential passthrough to the share in the first place, so the networking layer has to be right before any auth conversation even starts. The Citrix documentation for the Access Gateway 5.x and NetScaler Gateway 10.x client configuration sections both describe Local LAN-Access as the toggle that lets the client reach adjacent network resources, and a CIFS share fits squarely in that bucket. The other options talk about web app SSO or domain auth flows, which are downstream concerns and not the mechanism that gets credentials to a file share specifically.
Hiroshi, Local LAN-Access is a split-tunneling toggle for reaching your own adjacent subnet, not a credential-delivery mechanism, so enabling it just means the traffic can flow, it does not actually pass your Windows credentials to the share. Option C, Single Sign-On to Windows, is the feature that takes your authenticated session token and hands it to the CIFS challenge, which is the whole point of the question.
Honestly, I keep coming back to A on this one, and here is my thinking. Local LAN-Access is what actually controls whether the client can reach resources sitting on the internal network segment, and a file share is exactly that kind of resource. Without enabling that access mode, the gateway just will not route the credential flow down to the share at all, so the other options become kind of moot. The way I see it, the question is really asking what opens the door for credentials to travel to a file share specifically, and Local LAN-Access is the setting that puts the client on the same logical path as those internal resources.