5V0-35.21 · Question #136
An administrator is importing an Active Directory group with a role, and group members can login into vRealize Operations successfully. After a while, the administrator adds some new users into…
The correct answer is C. Synchronize the User Groups. D. Check if Automatically synchronize user membership for configured groups is selected. When new users are added to an Active Directory group in vRealize Operations, the platform doesn't automatically reflect those changes unless group synchronization is triggered - Synchronize the User Groups (C) forces an immediate sync to pull in new members, and checking the…
Question
An administrator is importing an Active Directory group with a role, and group members can login into vRealize Operations successfully. After a while, the administrator adds some new users into Active Directory group and discovers that newly added group members are not seen under User Accounts section and cannot login into vRealize Operations. Everything is working as expected for the old group members. The administrator needs to take further steps to allow the newly added group members to login quickly into vRealize Operations. Which two steps should the administrator take? (Choose two.)
Options
- ARe-add the Authentication Source.
- BAdd a SAML IdP as Authentication Source, and select source type as SSO SAML.
- CSynchronize the User Groups.
- DCheck if Automatically synchronize user membership for configured groups is selected.
- EDelete the existing Authentication Source.
How the community answered
(28 responses)- A4% (1)
- B4% (1)
- C79% (22)
- E14% (4)
Explanation
When new users are added to an Active Directory group in vRealize Operations, the platform doesn't automatically reflect those changes unless group synchronization is triggered - Synchronize the User Groups (C) forces an immediate sync to pull in new members, and checking the "Automatically synchronize user membership" setting (D) ensures this happens on a schedule going forward, preventing the issue from recurring.
Why the distractors are wrong:
- A (Re-add Authentication Source) is destructive overkill - it would disrupt all existing users and is not needed for a membership sync issue.
- B (Add SAML IdP) introduces a completely different authentication mechanism; the scenario already has a working AD source.
- E (Delete Authentication Source) would break authentication for all users, including the ones currently working - exactly the opposite of what's needed.
Memory tip: Think "sync before you sink" - when AD group members go missing in vROps, always check the sync options first (manual sync + auto-sync checkbox) before touching the authentication source itself. The source is working fine; only the membership refresh is stale.
Topics
Community Discussion
No community discussion yet for this question.