Scenario: A Citrix Architect needs to design a new Citrix Virtual Apps and Desktops environment.
Click the Exhibit button to view information collected by the architect during the Resource Layer discussions.
Based on the requirements, the Citrix Administrative team should use _____________ to manage Citrix policies and _____________ to manage Microsoft settings. (Choose the correct option to complete the sentence.)
To manage Citrix policies, the Citrix Administrative team should use Citrix Studio as this tool is specifically designed for managing Citrix environments and ensures that Citrix policies have priority, which is one of the requirements mentioned. For managing Microsoft settings, Active Directory Group Policy Objects should be used since they provide centralized management of policy settings, another stated requirement, without needing to install additional software components on user desktops. This setup aligns with the requirements specified in the scenario.
E is correct : https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/policies/policies-processes.html
E. Active Directory Group Policy Objects; Active Directory Group Policy Objects we can still do anything required by ADO
We have some requirements. Not to install additional software/agents (No WEM). Centralized management (open one AD GPO Console) and Citrix policies to have priority (so we can't use studio for Citrix policies - we need the ADMX files): it can only be E!
Agreed with E. But question still have not limits to install any agent on VDA, on user desktops only
the processing and the priority are opposite. Process: Local GPO Citrix policy site level GPO Dom-LEVEL GPO OU-LEVEL GPO Prio: OU-LEvel Dom-LEvel Site-LEvel Citrix-Policy local GPO Note: the policy is closer to the object, has more prio.
I would now say that E is more elegant and simple way to solve the problem because of some overhead for WEM support (and esp. to update for frequent CRs of WEM) and a lack of sound API for WEM. But question still have not limits to install any agent on VDA, on user desktops only
A is correct as "... that Citrix policies have priority". That is only the case if you configure Citrix Policies in Studio and GPOs in GPMC. See this: https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/policies/policies-processes.html However, if a conflict occurs, policy settings that are processed last can overwrite those that are processed earlier. This means that policy settings take precedence in the following order: Organizational Units Domain-level GPOs Site-level GPOs XenApp or XenDesktop Site GPO (stored in the Site database) Local GPO
A is correct
B looks logical:CTX policies by admx, all but any CTX\AD\local policies by WEM
I 'm quite sure it's C! Last requirement can be achieved with E and remember: it's a Citrix related question. We are talking about Citrix products. Everything required in the question can be done with the Citrix PRODUCTS: Studio and WEM!
Sorry! I was wrong. I misunderstood the last requirement... thought of blocking installations but it means we are not allowed to install the WEM agent. It could be E or even D (Citrix policies from Studio have precedence over local policies).
limits to install anything on user desktops only
A is correct. Based on the data, Citrix UPM is required, and Citrix policy needed as high priority. Citrix policies can only be handled via Studio. Lockdown policies are AD GPO based.
You can centrally manage Citrix policies through GPO using the Citrix ADMX template. Based on precedence hierarchy, a GPO must be used for Citrix policies. That leaves B and E as possible options. Since we can't install an agent, WEM is out. E is the answer. https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/policies.html#:~:text=Policy%20settings%20placed%20at%20the,and%20Citrix%20Local%20Policies%20levels.
do not see any word in question that we cannot install any agent on VDA or elsewere B looks logical:CTX policies by admx, all but any CTX\AD\local policies by WEM
I would now say that E is more elegant and simple way to solve the problem because of some overhead for WEM support (and esp. to update for frequent CRs of WEM) and a lack of sound API for WEM. But question still have not limits to install any agent on VDA, on user desktops only