1Y0-205 · Question #9
Which command must a Citrix Administrator run on the Citrix Director machine to integrate the NetScaler Console appliance with Citrix Director?
The correct answer is A. DirectorConfig.exe /confignetscaler. To integrate the NetScaler (Citrix ADC) Console with Citrix Director, the administrator must run the command DirectorConfig.exe /confignetscaler on the Director machine. This enables Director to display NetScaler Gateway and HDX Insight data.
Question
Which command must a Citrix Administrator run on the Citrix Director machine to integrate the NetScaler Console appliance with Citrix Director?
Options
- ADirectorConfig.exe /confignetscaler
- BSet-MonitorConfiguration
- CDirectorConfig.exe /configscom
- DSet-LogSite
How the community answered
(55 responses)- A95% (52)
- B2% (1)
- D4% (2)
Explanation
To integrate the NetScaler (Citrix ADC) Console with Citrix Director, the administrator must run the command DirectorConfig.exe /confignetscaler on the Director machine. This enables Director to display NetScaler Gateway and HDX Insight data.
Topics
Community Discussion
6
Imani T.Mar 3, 2026The correct answer is A, DirectorConfig.exe /confignetscaler. That executable is the dedicated configuration tool on the Director machine, and the /confignetscaler switch is specifically what tells it to set up the integration with NetScaler (now NetScaler Console or NetScaler MAS depending on your version of this exam). Options C is a trap because /configscom is for System Center Operations Manager integration, not NetScaler, and B and D are PowerShell cmdlets that deal with monitoring configuration and logging respectively, not appliance integration. Whenever you see a question about wiring Director to NetScaler, remember it always starts at the Director machine with that exe and the right switch.
Wesley A.Mar 14, 2026I kept second-guessing myself toward C since SCOM always muddies the waters, but "confignetscaler" literally names the thing you're wiring up.
Ingrid P.Mar 28, 2026DirectorConfig.exe /confignetscaler is the right call here, and this one is worth a dedicated card because the syntax trips people up constantly. The executable lives on the Director machine itself, not on the NetScaler Console, which is the first thing to burn into memory. The /configscom switch in option C is a distractor targeting SCOM integration, a completely separate workflow, so if you see both on a practice test back to back, keep them in separate decks with explicit context. I tag this card with "runs on Director machine" and "NetScaler Console integration only" so the recall cue is precise enough to survive interference from the SCOM variant.
Nina C.Apr 6, 2026Yes, A is right, that exe runs on the Director machine itself.
Giselle K.Apr 7, 2026Right, and worth remembering for the exam that it still needs a line of sight to the Delivery Controller and the site database, so "runs on Director" does not mean it operates in isolation.
Giselle K.Mar 31, 2026DirectorConfig.exe /confignetscaler is the one you run locally on the Director server to point it at the NetScaler Console (formerly MAS) so that the HDX Insight and network analysis panels actually populate in Director, which is why the other options don't fit here since Set-MonitorConfiguration and Set-LogSite are PowerShell cmdlets for the Monitor and Logging services respectively. Quick question for you though, do you know whether you run this on every Director server in a multi-Director deployment or just a designated primary, and what info you need to have ready before you execute it?