GOOGLE-WORKSPACE-ADMINISTRATOR practice question 11 of 25
The credentials of several individuals within your organization have recently been stolen. Using the Google Workspace login logs, you have determined that in several cases, the stolen credentials have been used in countries other than the ones your organization works in. What else can you do to increase your organization's defense-in-depth strategy?
Full set: 199 questionsDomain Business initiatives
Context-Aware Access (CAA) is a Google Workspace feature that enables a defense-in-depth security posture by enforcing granular access controls based on a user's identity and the context of their request. By creating an access level policy that restricts access to specific geographic locations, you can proactively block authentication attempts from unauthorized countries. This directly addresses the observed threat of stolen credentials being used from malicious locations and is a scalable, policy-driven solution that enhances security beyond just a password.
A. Implementing an IP block is a reactive measure. Attackers can easily circumvent this by using different IP addresses, proxies, or VPNs, making it an ineffective long-term solution.
C. Enforcing higher complexity passwords does not help when credentials have already been stolen. It is a good preventative measure for the future but does not address the immediate threat.
D. Mobile device management geo-fencing only applies to managed mobile devices. It would not prevent malicious actors from using stolen credentials on unmanaged devices, such as a desktop browser. ---
1. Google Workspace Admin Help, "Context-Aware Access overview." This document states, "With Context-Aware Access (CAA), you can create granular access control policies for apps, based on attributes such as user identity, location, device security status, and IP address." This directly supports using CAA for location-based access control.
2. Google Workspace Admin Help, "Create Context-Aware access levels," Section: "Create an access level," Step 5: "Add one or more conditions to the access level." The documentation lists "IP subnetworks" as a condition attribute. Administrators can define IP ranges corresponding to approved countries to enforce geo-location policies. This confirms the technical implementation described in the correct answer.
3. Google Workspace Admin Help, "Control which third-party & internal apps access Google Workspace data," Section: "Manage access to Google services: Context-Aware Access." This page reinforces that CAA is the designated tool for controlling access to Google services based on network location (IP address), which is the method for implementing geo-restrictions.
4. Google Workspace Admin Help, "Enforce password policies for your users." This documentation details password management but does not position it as a solution for compromised credentials being actively used, confirming that option C is an inappropriate response to the immediate threat.
Keep practicing
Take the free GOOGLE-WORKSPACE-ADMINISTRATOR practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other GOOGLE-WORKSPACE-ADMINISTRATOR practice questions
- Question 1You work for an international organization and your CEO frequently travels to other count…
- Question 2In your organization, users have been provisioned with either Google Workspace Enterprise…
- Question 3Your organization has just appointed a new CISO. They have signed up to receive admin ale…
- Question 4In the years prior to your organization moving to Google Workspace, it was relatively com…
- Question 5All Human Resources employees at your company are members of the “HR Department” Team Dri…
- Question 6Your Accounts Payable department is auditing software license contracts companywide and h…
