Chrome-Enterprise-Administrator Exam Dumps - Google Professional Chrome Enterprise Questions and Answers

Given that the MV2 extensions are not critical, and the requirement is to either block or upgrade, the most direct and efficient approach is to configure the "Manifest V2 availability" policy. This policy allows administrators to control the usage of Manifest V2 extensions, including blocking them entirely or allowing them until a specified date. Option A involves manually collecting and blocking each extension, which is less efficient. Option C ("removed") is not a standard installation mode policy. Option D is not a policy that an administrator can directly configure; the upgrade to MV3 is a developer-driven process.

===========

For macOS devices without MDM, the enrollment token can be embedded in the base image. The correct path for placing the cloud management enrollment token on macOS is `/Library/Google/Chrome/CloudManagementEnrollmentToken`. The other paths listed are for Windows Registry (A), a non-standard Linux path (C), and a potentially incorrect macOS path (D).

===========

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.

===========

Chrome checks for extension updates periodically when the browser is running. This check typically happens within the first few minutes of launching Chrome and then again every few hours. While updates are triggered by developers publishing to the Chrome Web Store, the actual update on the user's browser happens when Chrome is active and performs these periodic checks. Option A is incorrect as extensions generally don't update when Chrome is not running. Option C describes a manual update process, which is not the default behavior. Option D is incorrect because the update on the user's end is dependent on Chrome being active and checking for updates.

===========

If a browser becomes inactive due to policy, the device management token likely needs to be refreshed or re-established. Deleting the token and then reopening Chrome will typically trigger the browser to attempt re-enrollment and obtain a new token, bringing it back under management. Wiping the browser or deleting it from the CEC might be necessary in more severe cases but is not the minimum action. Simply closing and reopening Chrome might not be sufficient if the token has expired or been invalidated.

===========