The answer is D. A third party identity provider is NOT a directory (like Active Directory). You are attaching through SAML to a provider. V provided a link that says the sysadmin can “configure tenant identity stores”. In a similar document it says a Tenant Admin can “manage tenant identity stores”. But that isn’t what is being asked here. To find the answer, go here: https://docs.vmware.com/en/vRealize-Automation/7.3/com.vmware.vra.prepare.use.doc/GUID-93F7569C-D228-4386-8B8D-324E110AFAF6.html
Under Prerequisites, third bullet “Log in to the vRealize Automation console as tenant administrator.”
I´d say it is A
https://docs.vmware.com/en/vRealize-Automation/7.3/com.vmware.vra.prepare.use.doc/GUID-8A19697C-AECA-4E19-9E46-765898C0D153.html
0
0
The answer is D. A third party identity provider is NOT a directory (like Active Directory). You are attaching through SAML to a provider. V provided a link that says the sysadmin can “configure tenant identity stores”. In a similar document it says a Tenant Admin can “manage tenant identity stores”. But that isn’t what is being asked here. To find the answer, go here: https://docs.vmware.com/en/vRealize-Automation/7.3/com.vmware.vra.prepare.use.doc/GUID-93F7569C-D228-4386-8B8D-324E110AFAF6.html
Under Prerequisites, third bullet “Log in to the vRealize Automation console as tenant administrator.”
4
0