Chrome-Enterprise-Administrator Professional Chrome Enterprise Administrator Certification Exam Questions and Answers

When managing inactive device tokens, the "Renew Token" option is crucial for allowing devices to re-enroll after a period of inactivity. If the token is revoked, invalidated, or deleted, the device will likely require a manual re-enrollment process. Renewing the token provides a mechanism for the device to check back in and remain managed.

===========

The **Enrollment Token** is the key to associating a Chrome browser instance with a specific organizational unit (OU) in the Google Admin console during the enrollment process. By applying the correct enrollment token during setup, the browser will be placed in the designated OU and inherit the policies configured for that OU. Device Management Tokens are more relevant for ChromeOS devices. Browser Policy Tokens are not a standard term for OU assignment during enrollment. Cloud Management Token is a general term encompassing the enrollment process.

===========

The Chrome Versions report specifically focuses on the distribution of different Chrome browser versions across the managed fleet. A key data point in this report is the number of "Active Browsers" on each version, allowing administrators to understand their update status and identify any significant fragmentation. While "Total Browsers" might be a related metric, the core focus of the "Versions" report is on the active instances and their respective versions. Information on "Inactive Browsers" or the "Last update" time for individual browsers might be found in other reports.

===========

The Chrome Insights Report in the Google Admin console provides visibility into the managed Chrome browser environment. Key report types available here include "Browsers pending updates" to identify devices needing patching, "Browsers without activity in the past 28 days" to understand browser usage, and "Browsers that have been recently enrolled" for monitoring onboarding. The other options list reports that are either not specific to Chrome Insights or related to device hardware rather than browser status.

===========

The "Chrome Browser - > Reports - > Apps & extensions usage" section in the Google Admin console provides detailed information about installed extensions, including permissions and a risk assessment (if available through integrated security features). This report allows administrators to filter and analyze extensions based on their risk score and the number of permissions they request, enabling them to identify extensions that meet the cyber risk team's criteria.

===========

By default, when a Chrome browser on a Windows device is enrolled in Chrome Enterprise Core, cloud-based machine policies will take precedence over locally configured machine policies (Group Policy). This ensures that the centrally managed cloud policies are enforced.

===========

To pin Chrome to a specific working version and prevent upgrades beyond it while still allowing updates within that major version for security patches, the "Target version and rollback" policy is the appropriate choice. This allows administrators to specify a target version and potentially roll back if issues arise, while still receiving critical security updates within that targeted version.

===========

A "3rd Party Risk Score" provides an objective assessment of the extension's security and privacy risks, often based on automated analysis of its code, requested permissions, developer reputation, and other factors. This is a more data-driven approach to evaluating safety compared to simply counting permissions (which doesn't account for the sensitivity of each permission), the Manifest version (which indicates features but not necessarily safety), or Chrome Web Store ratings (which are subjective and can be manipulated).

===========

While not directly stating "enforce to the latest major stable version," the "Auto-update check period" policy, when configured appropriately (shorter intervals), ensures that devices check for and apply updates more frequently. This increases the likelihood of browsers reaching and staying closer to the latest stable version over time. "Rollback to target version" is for reverting updates, "Component updates" manages specific browser components, and "Relaunch notification" prompts users to restart after an update.

===========

To minimize disruption while ensuring updates are applied, an engineer can configure a "Relaunch window" in the Relaunch notification settings. This allows users to be prompted to restart within a specific timeframe that is less likely to interrupt their critical work hours, giving them more control over when the restart occurs after an update. Disabling automatic updates (option A) would compromise security. Adding a quiet period (option B) only suppresses notifications, not the forced restart. Setting the auto-update check policy to occur during core work hours (option C) affects when updates are downloaded, not when the restart occurs.

===========

Clearing the browser's cache and cookies is a common first-line troubleshooting step for issues related to website access and login problems. Outdated or corrupted cached data and cookies can often interfere with website functionality and authentication processes. The Google Admin console provides remote actions to "Clear Cache," "Clear Cookies," or both. Options B, C, and D include actions that are either more disruptive (restart browser, logout user, restart user session) or not standard remote actions available for managed Chrome browsers through the Admin console (delete temporary files, delete swap file).

===========

To prevent a child OU from inheriting a policy set at a parent OU, the administrator needs to configure the policy within the child OU itself and set its inheritance status to "Locally applied." This explicitly overrides the inherited policy from the parent with a specific setting for the child OU. Setting it to locally applied at the parent would not prevent inheritance. Turning off inheritance entirely might not be desired for other policies, and "Child > Parent" is the default precedence when inheritance is enabled.

===========