VCP550 · Question #55
As part of a multisite Single Sign-On (SSO) deployment what two steps are required to ensure that a change to one Single Sign-On instance is propagated to the other instances? (Choose two.)
The correct answer is A. Schedule a Replication Task on the primary instance C. During the installation of each instance choose Linked-Mode. A multisite vSphere SSO deployment requires scheduling a replication task on the primary instance and selecting Linked-Mode during installation of each subsequent instance.
Question
As part of a multisite Single Sign-On (SSO) deployment what two steps are required to ensure that a change to one Single Sign-On instance is propagated to the other instances? (Choose two.)
Options
- ASchedule a Replication Task on the primary instance
- BSelect the first instance during the installation of subsequent instances
- CDuring the installation of each instance choose Linked-Mode
- DEnable Synchronize to Active Directory on each instance
How the community answered
(56 responses)- A77% (43)
- B7% (4)
- D16% (9)
Why each option
A multisite vSphere SSO deployment requires scheduling a replication task on the primary instance and selecting Linked-Mode during installation of each subsequent instance.
A replication task must be scheduled on the primary SSO instance to actively push configuration and identity changes to other SSO nodes in the multisite topology.
Selecting the first instance during installation is not a valid standalone step; without also choosing Linked-Mode, replication between instances will not be established.
During installation of each additional SSO instance, the Linked-Mode option must be selected to join the existing SSO infrastructure, which enables cross-instance replication and unified authentication.
'Synchronize to Active Directory' is not a valid configuration option for SSO inter-instance replication in a multisite deployment.
Concept tested: vSphere SSO multisite deployment and replication setup
Source: https://docs.vmware.com/en/VMware-vSphere/5.5/com.vmware.vsphere.security.doc/GUID-7C16A9DF-FA79-4EEB-8F64-B5C9C9F4C9ED.html
Topics
Community Discussion
No community discussion yet for this question.