ASSOCIATE-GOOGLE-WORKSPACE-ADMINISTRATOR · Question #21
Your company is transitioning to Google Workspace from legacy communication and collaboration applications. User accounts are managed in Active Directory and synced to Google Workspace by using…
The correct answer is D. Create a password policy in Active Directory. Enable password synchronization in GCDS. Since user accounts are managed in Active Directory (AD) and synced to Google Workspace via GCDS, Active Directory is the authoritative source of truth for user credentials. Password policies must be enforced at the source - AD - to be meaningful. Option D correctly identifies…
Question
Your company is transitioning to Google Workspace from legacy communication and collaboration applications. User accounts are managed in Active Directory and synced to Google Workspace by using Google Cloud Directory Sync (GCDS). Your company is implementing a new security policy for all accounts that requires complex passwords. Passwords must be at least 20 characters long, contain 3 symbols, 4 numbers, and 2 capital letters. You need to enforce the new password policy in Google Workspace. What should you do?
Options
- AShare the instructions for changing a Google account password with your users. Monitor password
- BEnable strong password enforcement and require a minimum length of 20 characters at the top-
- CCreate a password policy in Active Directory. Install Password Sync on the global catalog servers
- DCreate a password policy in Active Directory. Enable password synchronization in GCDS.
How the community answered
(19 responses)- A11% (2)
- B5% (1)
- C5% (1)
- D79% (15)
Explanation
Since user accounts are managed in Active Directory (AD) and synced to Google Workspace via GCDS, Active Directory is the authoritative source of truth for user credentials. Password policies must be enforced at the source - AD - to be meaningful. Option D correctly identifies this: create the complex password policy in AD (where it will be enforced at login), then enable password synchronization in GCDS so that password changes in AD propagate to Google Workspace. Option A is not enforcement - it's just instruction. Option B attempts to set policy in Google Workspace directly, but because credentials originate in AD, Google Workspace password settings are bypassed during SSO/sync flows. Option C uses Password Sync (a separate tool from GCDS) which syncs raw password hashes - this is unnecessary and introduces additional complexity when GCDS's built-in synchronization handles the requirement.
Topics
Community Discussion
No community discussion yet for this question.