1Y0-231 · Question #106
Scenario: Users are unable to establish RDP sessions through the Citrix Gateway RDP proxy. The configuration below is present on the Citrix ADC: Which command can a Citrix Administrator use to…
The correct answer is A. add dns addrec rdpserverinfo 10.102.147.134. Option A is correct because the Citrix Gateway RDP proxy requires a DNS address record (rdpserverinfo) to resolve the internal RDP server's IP address - without this record, the ADC cannot forward the client's RDP connection to the backend server, making session establishment…
Question
Scenario: Users are unable to establish RDP sessions through the Citrix Gateway RDP proxy. The configuration below is present on the Citrix ADC:
Which command can a Citrix Administrator use to establish these RDP sessions?
Exhibit
Options
- Aadd dns addrec rdpserverinfo 10.102.147.134
- Bset rdp clientprofile p1 -psk citrix -redirectClipboard DISABLED
- Cset vpn parameter -clientlessVpnMode ON -defaultAuthorizationAction ALLOW -
- Dadd vpn parameter -clientlessVpnMode OFF -redirectClipboard DISABLED
How the community answered
(50 responses)- A92% (46)
- B2% (1)
- C4% (2)
- D2% (1)
Explanation
Option A is correct because the Citrix Gateway RDP proxy requires a DNS address record (rdpserverinfo) to resolve the internal RDP server's IP address - without this record, the ADC cannot forward the client's RDP connection to the backend server, making session establishment impossible.
Option B is a distractor because set rdp clientprofile only modifies an existing profile's settings (like clipboard redirection and PSK), it does not resolve the underlying connectivity gap caused by a missing DNS entry. Option C is wrong because enabling clientlessVpnMode ON applies to browser-based SSL VPN access, not the RDP proxy feature, and would not fix RDP sessions. Option D is invalid both syntactically (add vpn parameter is not a real command - VPN global parameters use set vpn parameter) and logically, since disabling clientless mode and clipboard redirection does nothing to enable RDP proxy routing.
Memory tip: Think "RDP proxy = DNS-dependent plumbing." Before traffic can flow, the ADC needs a map (dns addrec) to find the destination - no map, no session.
Topics
Community Discussion
6
Mei-Ling H.Nov 9, 2025The answer is A, and here is why it matters. The Citrix Gateway RDP proxy feature depends on a DNS resolution for the server name configured in the RDP server profile, in this case "rdpserverinfo," and without that address record mapping the name to an actual IP, the gateway simply cannot complete the proxy connection to the backend RDP server. Option B is a distractor because it modifies an existing client profile setting like clipboard redirection, which does not fix a broken DNS lookup. Options C and D both deal with clientless VPN mode parameters, which is a completely separate feature from the RDP proxy path and will not restore RDP sessions no matter how you set them.
Anjali D.Oct 24, 2025Went with B first, then saw the missing DNS record breaks everything.
Nina C.Oct 25, 2025Same thing happened to me on that practice set, and now "check DNS first" is basically my new rule before I touch anything else in those troubleshooting scenarios.
Kemal J.Dec 5, 2025Took me a second on this one because I kept second-guessing myself thinking it had to be something more complicated, but A is dead obvious once you remember that the RDP proxy on the Gateway needs the server name to resolve, and without that DNS address record mapped to the RDP server IP the whole thing just sits there doing nothing. Seen TAC cases where a guy swore the profile config was wrong and spent two days tweaking psk values when the real problem was the ADC had no idea where to send the session because nobody added the record.
Mei-Ling H.Dec 5, 2025Good point, and worth flagging for the exam that some question stems say "host record" instead of "A record," which is the same thing, so do not let that wording swap trip you up when you scan the answer choices.
Nina C.Nov 18, 2025Yeah, A is right, the RDP proxy on the ADC uses a hostname like "rdpserverinfo" internally and if there is no DNS A record pointing that name to the actual server IP, the proxy has nothing to connect to. Adding that address record is what gives the ADC the resolution it needs to broker the session.