Chrome-Enterprise-Administrator Practice Exam Questions with Answers Professional Chrome Enterprise Administrator Certification Exam Certification

The scenario describes vulnerabilities that could allow cross-site data leakage within the browser's memory. "Site isolation for every website" is a security feature in Chrome that isolates the rendering process for each website, preventing one site from accessing the data of another, even if a vulnerability is exploited. This policy directly addresses the risk of cross-site information leakage due to memory vulnerabilities. Option A relates to TLS security, option B is a general security best practice but doesn't directly prevent cross-site memory access, and option C manages extension behavior, not core browser memory isolation.

===========

Organizational Units (OUs) in the Google Admin console allow administrators to apply different Chrome policies to different groups of devices or users based on their organizational structure. By creating separate OUs for Engineering and HR (and potentially other departments), the administrator can configure different Chrome update policies for each OU, ensuring Engineering gets rapid updates while HR stays on a more stable release. User groups primarily manage access to services, and device policies are generally applied at the device level, not necessarily tied to departmental needs for update cadences. Active Directory forests are a Microsoft concept and not directly used for managing Chrome update policies in the Google Admin console.

===========

For machines with no internet connectivity, automatic updates will not work. The only way to update Chrome in this scenario is to manually run the Chrome installer with an updated version obtained through an alternative method (e.g., downloaded on a connected machine and transferred). Auto-update requires internet access, setting a target version only dictates the desired version for automatic updates, and force relaunch requires an update to be downloaded first.

===========

When a managed browser is deleted from the Google Admin console, it needs to be re-enrolled to receive policies again. The process for re-enrollment typically involves deleting the **device management token** from the local machine. Upon relaunching Chrome, the browser will detect the absence of the token and attempt to re-enroll with the cloud management service, at which point it will receive a new token and the latest policies. Deleting the enrollment token (option B) might disrupt the initial enrollment if it still existed. Deleting Chrome policies (option C) might not trigger re-enrollment. Clearing the cache and signing back in (option D) addresses user profile data, not device enrollment.

===========

The study guide emphasizes using enrollment tokens generated in the Google Admin console for enrolling browsers. When using an MDM solution, the most efficient and recommended method is to generate a single enrollment token and then deploy it to the devices through the MDM software. This allows for automated and scalable enrollment. Bulk enrollment features in the Admin console are typically for direct enrollment, not through MDM. Individual tokens or keys would be inefficient for a large deployment.

===========

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 andapply 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 ensure timely patching, the engineering team should adjust the "Auto-update check period" policy. By shortening this period, Chrome browsers will check for updates more frequently, increasing the likelihood of applying security patches sooner and improving compliance with patching SLAs. "Chrome browser updates" is a general category, "Relaunch notification" affects when users are prompted to restart, and "Google updater policy precedence" deals with the order of policy application, not the frequency of checks.

===========

To prevent extensions from modifying the internal homepage, the administrator should add `*.acme.com` to the "Runtime blocked hosts" list. The wildcard `*` ensures that any attempt to access or modify this domain by an extension will be blocked at runtime. Additionally, to disable access to storage and history, the administrator needs to explicitly disable the "Storage" and "History" permissions within the extension management settings. Therefore, the correct combination is to block the host and disable the permissions.

===========

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 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.

===========