When designing an OU hierarchy for a company that has multiple departments and regional offices, which approach best aligns with Google's recommended practices?

Create a flat hierarchy with only a few OUs, grouping users by department or function, and avoid unnecessary depth.

Create a hierarchy based solely on geographic regions, ignoring departmental structure, to simplify policy application.

Create a deep hierarchy that mirrors every level of the company's management structure to ensure granular policy control.

Create a hierarchy that assigns each user to a unique OU to maximize individual policy control.

A company has an OU for 'Contractors' and an OU for 'Employees'. A contractor is promoted to a full-time employee. What is the correct way to update the user's OU assignment?

Move the user from the 'Contractors' OU to the 'Employees' OU.

Change the user's group membership to an employee group.

Delete the user and recreate them in the 'Employees' OU.

Rename the 'Contractors' OU to 'Employees'.

If a setting is overridden at a child OU, what happens to the settings of objects in that child OU?

The setting is applied to the child OU and all its parent OUs.

The parent's setting still applies, and the override is ignored.

The child OU's setting takes precedence over the parent's setting for objects in that child OU.

The setting is disabled for all objects in the child OU until the override is removed.

Which of the following is a Google-recommended practice for OU design?

Create OUs for each individual user to allow for maximum customization.

Limit the depth of the OU hierarchy to avoid unnecessary complexity.

Group users by their job title to ensure precise policy application.

Place all users in the top-level OU and use groups to manage policies.

An administrator needs to delete an OU that contains users and child OUs. What is the correct procedure?

Move all users and child OUs to another OU, then delete the empty OU.

Rename the OU and then delete it; users and child OUs will be preserved.

Delete the OU directly; users and child OUs will be deleted automatically.

Delete the child OUs first, then delete the parent OU; users will be moved to the top-level OU.

Google CloudAssociate Google Workspace Administrator

Domain 1Objective 2

1.2 Designing and Creating Organizational Units (OUs) ASSOCIATE-GOOGLE-WORKSPACE-ADMINISTRATOR Practice Questions (Page 1)

Part of the Managing user accounts, domains, and Directory domain, which accounts for ~20% of the ASSOCIATE-GOOGLE-WORKSPACE-ADMINISTRATOR exam.

15questions here

3free pages

6concepts

~20%of the exam

Questions 1–5

1foundation · easy
When designing an OU hierarchy for a company that has multiple departments and regional offices, which approach best aligns with Google's recommended practices?
Select an answer first
2application · easy
A company has an OU for 'Contractors' and an OU for 'Employees'. A contractor is promoted to a full-time employee. What is the correct way to update the user's OU assignment?
Select an answer first
3foundation · easy
If a setting is overridden at a child OU, what happens to the settings of objects in that child OU?
Select an answer first
4foundation · easy
Which of the following is a Google-recommended practice for OU design?
Select an answer first
5application · medium
An administrator needs to delete an OU that contains users and child OUs. What is the correct procedure?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to ASSOCIATE-GOOGLE-WORKSPACE-ADMINISTRATOR

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Google Cloud. “ASSOCIATE-GOOGLE-WORKSPACE-ADMINISTRATOR” is a trademark of its owner, used for identification only.