GOOGLE-WORKSPACE-ADMINISTRATOR practice question 20 of 25

Your organization recently implemented context-aware access policies for Google Drive to allow users to access Drive only from corporate managed desktops. Unfortunately, some users can still access Drive from non-corporate managed machines. What preliminary checks should you perform to find out why the Context-Aware Access policy is not working as intended? (Choose two.)

Full set: 199 questions

Domain Data access and security

Answer options
A: Confirm that the user has a Google Workspace Enterprise Plus license. Correct answer
B: Delete and recreate a new Context-Aware Access device policy.
C: Check whether device policy application is installed on users’ devices.
D: Confirm that the user has at least a Google Workspace Business license.
E: Check whether Endpoint Verification is installed on users’ desktops. Correct answer
Correct Answer:
A. Confirm that the user has a Google Workspace Enterprise Plus license.; E. Check whether Endpoint Verification is installed on users’ desktops.
Explanation

Context-Aware Access (CAA) functionality depends on two fundamental components: user licensing and context signals from the device. A preliminary investigation into a failing policy should verify these basics. First, CAA is a premium feature not available on all Google Workspace editions. A user must be assigned a supported license (e.g., Enterprise, Education Plus) for any CAA policy to be enforced on their account. Therefore, verifying the user's license is a critical initial step. Second, for device-based policies on desktops, CAA relies on the Endpoint Verification Chrome extension to gather and report device attributes (e.g., serial number, OS, encryption status). Without this extension installed and running, the CAA engine receives no signals to evaluate against the policy, which can lead to unintended access.

Why Incorrect

B. Deleting and recreating a policy is a last resort, not a preliminary diagnostic check. The existing configuration should be investigated first.
C. The device policy application is for managing mobile devices (Android and iOS), whereas the scenario specifies desktops, which use Endpoint Verification.
D. Google Workspace Business editions do not include the Context-Aware Access feature, so this check would be based on an incorrect premise.

References

1. Google Workspace Admin Help, "Control access to apps with Context-Aware Access." In the "Before you begin" section, under "Supported editions," the documentation lists the required licenses: "Google Workspace Enterprise Plus, Enterprise Standard, Education Plus, Education Standard; Cloud Identity Premium." This supports checking for a license like Enterprise Plus (A) and refutes the validity of a Business license (D).

2. Google Workspace Admin Help, "Overview of Endpoint Verification." This document states, "Endpoint Verification allows you to see details about the computers that access your organization's data... When you create Context-Aware access policies, you can use information from Endpoint Verification to require that devices are company-owned..." This directly confirms that Endpoint Verification is the required component for desktop device policies (E) and is distinct from the mobile device policy app (C).

3. Google Workspace Admin Help, "Troubleshoot Context-Aware Access." Under the section "Common issues and troubleshooting steps," the guide explicitly lists "Check the user's license" and "For computers, verify that Endpoint Verification is installed on the device" as primary troubleshooting actions. This validates both (A) and (E) as correct preliminary checks.

Scroll to Top