Free Google-Workspace-Administrator Actual Exam Questions - Question 14 Discussion
Workspace licensing. A third of your employees are located in the United States, another third in
Europe, and the other third geographically dispersed around the world. European employees are
required to have their data stored in Europe. The current OU structure for your organization is
organized by business unit, with no attention to user location. How do you configure Workspace for
the fastest end user experience while also ensuring that European user data is contained in Europe?
D seems solid since config groups can be applied without restructuring OUs, keeping things simple and still ensuring European data stays local. Less hassle than changing OU setups.
B tbh. Adding location-based OUs seems like a clean way to segment data region controls without messing with existing business unit structures too much. It directly ties data storage rules to user location, which matches the requirement well. Plus, it avoids potential confusion from overlapping config groups or needing complex rules. Seems more straightforward for compliance and performance.
D. Configuration groups let you target users by location without changing OUs, keeping the current structure intact. This way, European data stays in Europe and users get the best experience.
C, because config groups let you target European users without changing the OU structure.
This one’s tricky, but I think D makes more sense here. Instead of juggling OUs, configuration groups let you assign data regions based on location without restructuring the existing OU setup. That way, European users get their data stored in Europe, and others get the best experience without mixing up the business unit OUs. Adds flexibility without disrupting the current structure, which seems safer given the question doesn’t say we can reorganize OUs easily. So, I’d go with D.
It’s B. The current OU is based only on business units, so you’re not segmenting by location yet. Adding new OU structures for location lets you assign data regions correctly for each group. This way European users get their data in Europe, and others can be optimized too. Options A or C don’t fix the problem fully since they’re either setting region at the top of an OU that includes non-European users or just a config group, which might be less consistent. D is close but splitting into config groups instead of OUs might not manage policies as cleanly at scale.