When using the Gateway Direct secure access method in the Web interface, the XenApp administrator must provide the __________of the Access Gateway server. (Choose the correct option to complete the…

Thekla S.Jun 21, 2026

The answer is D, the Fully Qualified Domain Name (FQDN). Gateway Direct requires the Web Interface to resolve and present the Access Gateway server by its FQDN because SSL certificates are bound to that hostname, and any mismatch between what the client connects to and what the certificate asserts will break the secure handshake before the session ever opens.

Dervla O.Jun 27, 2026

The trap here is A, because you might think "network address, just use the IP," but Gateway Direct is SSL-based and the certificate is bound to a name, not a number, so entering an IP breaks the trust chain immediately. You land on D, the FQDN, because that is what the certificate resolves against and what the secure tunnel actually validates on both ends.

Viktor S.Jun 27, 2026

The exam nails you on D here because the Gateway Direct method routes your session through HTTPS, and HTTPS requires SSL/TLS to validate the server identity against a certificate. That certificate is issued to a name, not an IP address, so when XenApp Web Interface needs to hand off the connection to the Access Gateway, it has to know the FQDN that matches what's on that cert. Putting in an IP address would either break name resolution or, worse, cause a certificate mismatch error that kills the session before it starts. NetBIOS is a non-starter since this is all happening over an internet-routable path where NetBIOS has no business. What I want to know from anyone studying this, do you actually understand why an SSL cert can't just be tied to an IP in most enterprise setups here, or are you just memorizing "FQDN goes with SSL"? Because the underlying reason is what you'll actually run into when a cert renewal breaks Web Interface config in a real deployment.

Wesley A.Jun 27, 2026

The answer is D, FQDN, and the reason it trips people up is that A looks so reasonable on the surface. You think, well the admin needs to point to a server, and IP addresses work for servers all the time, so why not here. The catch is that Gateway Direct goes over SSL, and SSL certificates are issued to a hostname, specifically a fully qualified domain name, not a raw IP. When the Web Interface hands off the connection to the Access Gateway, it passes along that FQDN, and if what you entered does not match the CN on the cert, the handshake breaks. NetBIOS is a flat name with no dot notation and is not valid for SSL either, and the SSL cert itself is something you install on the appliance, not something you provide to configure the connection. I saw a version of this question on my first attempt and bubbled IP address because I was thinking about network reachability instead of thinking about what makes a secure SSL handshake valid. Second time around I had drilled this enough that FQDN was obvious the moment I read "secure access method" and "Gateway Direct" in the same sentence. If the question mentions Access Gateway and anything about the Web Interface configuration, your first thought should be FQDN because that is what ties the SSL trust chain together. Lock that in and do not second-guess yourself.

Orla P.Jun 27, 2026

Gateway Direct is SSL-based, so the cert is what ties it all together.