what two steps are required to ensure that a change to one Single Sign-On instance is propagated to the other instances?

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.)

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.)

A.
Schedule a Replication Task on the primary instance

B.
Select the first instance during the installation of subsequent instances

C.
During the installation of each instance choose Linked-Mode

D.
Enable Synchronize to Active Directory on each instance

Explanation:

Show Hint

Leave a Reply 10

Your email address will not be published. Required fields are marked *

Bart

Bart

If you install vCenter Server systems in multiple locations, you can install a SSO server in each location. When you install the second and subsequent instances of SSO, you can (–B->)point it to the first SSO instance during installation()Changes to one instance are propagated to the other instance(<-A–).

A. AND B. must be the answers.

Reply

RDGR

RDGR

I’m not sure that B propogates changes between instances whoever Linked Mode it required.

Reply

vmsatguru

vmsatguru

A and B might be the answers

Ref: http://www.youtube.com/watch?v=AsZEQSW2UQg (approx 8 mins)

During the ‘SSO’ installation its not asking about the linked mode but its asking the partner host name during the second site installation.

Reply

AlektroNik

AlektroNik

Correct answer “A” and “B”.

Reply

mkbell

mkbell

A is correct:Replicating Data Between Single Sign-On Sites
Automatic replication of data between Single Sign-On Sites is not supported. Whenever you make a change to one of the Single Sign-On instances, you must perform a manual data export and import operation with a command-line tool. The data to replicate includes local users and groups and the configuration of the STS server. Because this data rarely changes, you can schedule replications once a day or week, as appropriate.http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2034074

B is correct:To install vCenter Single Sign-On in a multisite deployment:
At Site A, install the primary Single Sign-On node.
In the Single Sign-On installation wizard panel vCenter Single Sign-On Deployment Type, select Create the primary node for a new vCenter Single Sign On installation.
In the panel that asks you to Select single node type, select Create the primary node for a new vCenter Single Sign On installation.
Complete the Single Sign-On installation wizard.
At Site B, install a secondary Single Sign-On node, pointing to Site A.
In the Single Sign-On installation wizard panel vCenter Single Sign-On Deployment Type, select Join an existing vCenter Single Sign On installation.
For the node type, select Multisite, and point to the Single Sign-On primary node that you created in step 1.
Enter the FQDN or IP address, Single Sign-On HTTPS port, and the password admin@System-Domain for the primary Single Sign-On node. Note: If Site A is a high-availability cluster, enter the address of the Site A load balancer.
Complete the Single Sign-On installation wizard.

Reply

HWill

HWill

For VCP550 exam, answer should be B & C – refer: http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.install.doc/GUID-C6F362AF-397C-4271-A9A1-4EEF1C718AA9.html

See also http://vtricks.com/?p=1527

A – automatic replication now in 5.5, wasn’t in 5.1
B – Correct from actual install steps and from the VM doco
C – Correct. Key word is multi-site, from the VM doco above, linked mode is a requirement for multisite SSO
D – This is a bit tricky. Whilst the doco says local accounts cannot be used, it allows either AD or OpenLDAP.

So B&C are the best

Reply

andp75

andp75

Agree with the previous poster: should be B and C.

Reply