New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Associate Google Workspace Administrator Exam - Topic 1 Question 8 Discussion

Actual exam question for Google's Associate Google Workspace Administrator exam
Question #: 8
Topic #: 1
[All Associate Google Workspace Administrator Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Leoma
2 months ago
Sharing instructions alone won't cut it, we need enforcement!
upvoted 0 times
...
Gilma
2 months ago
I think D makes more sense since it syncs with AD.
upvoted 0 times
...
Stevie
2 months ago
Option B is the way to go! Strong password enforcement is key.
upvoted 0 times
...
Portia
3 months ago
I agree with B, but I wonder if users will actually remember those passwords.
upvoted 0 times
...
Kiera
3 months ago
Wait, 20 characters? That’s a bit excessive, isn’t it?
upvoted 0 times
...
Lashawna
3 months ago
I recall that we talked about syncing passwords from Active Directory, so option D might be relevant, but I’m not entirely sure if that’s the best choice here.
upvoted 0 times
...
Fanny
3 months ago
I’m a bit confused about whether we should manage everything in Active Directory or if Google Workspace can handle the password policy on its own.
upvoted 0 times
...
Louvenia
4 months ago
I think option B sounds familiar because we practiced a similar question about setting password requirements in organizational units. It seems like the right approach.
upvoted 0 times
...
Leonora
4 months ago
I remember we discussed the importance of enforcing password policies in Google Workspace, but I'm not sure if we should do it directly in Google or through Active Directory.
upvoted 0 times
...
Margery
4 months ago
I'm a little unsure about the difference between Option C and Option D. I'll need to double-check the details on password synchronization and how that interacts with the Active Directory policy.
upvoted 0 times
...
Mary
4 months ago
I'm feeling pretty confident about this one. The question is clearly asking us to leverage the Google Admin console to set the password requirements, so I'm going to go with Option B.
upvoted 0 times
...
Goldie
4 months ago
Okay, I think I've got this. The key is to enable the strong password enforcement in Google Workspace and sync that with the Active Directory policy. Option B seems like the way to go.
upvoted 0 times
...
Wilburn
5 months ago
Hmm, I'm a bit confused about the relationship between Active Directory and Google Workspace. I'll need to make sure I understand how the directory sync works.
upvoted 0 times
...
Adelle
5 months ago
This looks like a tricky one. I'll need to carefully read through the options and think about the steps involved in enforcing the password policy.
upvoted 0 times
...
Quinn
9 months ago
I'd better start thinking of some really wacky passwords to meet these new requirements. Maybe I'll use emojis!
upvoted 0 times
Luther
8 months ago
B) Enable strong password enforcement and require a minimum length of 20 characters at the top-level organizational unit.
upvoted 1 times
...
Glory
8 months ago
A) Share the instructions for changing a Google account password with your users. Monitor password strength in the Google Admin console as users change their passwords.
upvoted 0 times
...
...
Herschel
9 months ago
That could work too, but I think monitoring password strength in the Google Admin console is important for ensuring compliance.
upvoted 0 times
...
Lindsay
9 months ago
I'm with Antoniois on this one. Option B is the easiest way to implement the new password requirements across the board.
upvoted 0 times
Naomi
8 months ago
D) Create a password policy in Active Directory. Enable password synchronization in GCDS.
upvoted 0 times
...
Laurel
8 months ago
A) Share the instructions for changing a Google account password with your users. Monitor password strength in the Google Admin console as users change their passwords.
upvoted 0 times
...
Camellia
9 months ago
B) Enable strong password enforcement and require a minimum length of 20 characters at the top-level organizational unit.
upvoted 0 times
...
...
Antonio
9 months ago
Haha, 20 characters? That's longer than my entire password used to be! This new policy is insane.
upvoted 0 times
Yan
8 months ago
C) Create a password policy in Active Directory. Install Password Sync on the global catalog servers for Active Directory and require a password change for your users.
upvoted 0 times
...
Lauran
8 months ago
B) Enable strong password enforcement and require a minimum length of 20 characters at the top-level organizational unit.
upvoted 0 times
...
Ronald
8 months ago
A) Share the instructions for changing a Google account password with your users. Monitor password strength in the Google Admin console as users change their passwords.
upvoted 0 times
...
...
Doyle
9 months ago
But wouldn't it be better to create a password policy in Active Directory and enable password synchronization in GCDS?
upvoted 0 times
...
Fabiola
9 months ago
D is the correct answer. We need to sync the AD password policy with Google Workspace using GCDS. Simple and straightforward.
upvoted 0 times
Micah
8 months ago
I agree. It's good that we have a tool like GCDS to help with the synchronization process.
upvoted 0 times
...
Junita
9 months ago
That makes sense. It's important to have a secure password policy in place for our accounts.
upvoted 0 times
...
Eulah
9 months ago
D is the correct answer. We need to sync the AD password policy with Google Workspace using GCDS. Simple and straightforward.
upvoted 0 times
...
...
Brett
10 months ago
I agree with Herschel. Enabling strong password enforcement at the top-level organizational unit seems like the best approach.
upvoted 0 times
...
Herschel
10 months ago
I think we should go with option B.
upvoted 0 times
...
Alexis
10 months ago
Option B seems like the way to go. Enforcing the password policy directly in Google Workspace makes the most sense for our transition.
upvoted 0 times
Alison
8 months ago
B) That's a good point. It will be easier to manage and enforce the new password policy directly in Google Workspace.
upvoted 0 times
...
Julie
8 months ago
A) Share the instructions for changing a Google account password with your users. Monitor password strength in the Google Admin console as users change their passwords.
upvoted 0 times
...
Corinne
8 months ago
B) Enable strong password enforcement and require a minimum length of 20 characters at the top-level organizational unit.
upvoted 0 times
...
...

Save Cancel