certslothcertsloth
AGWA/Topic 05

Google Cloud / Associate

Manage browsers and devices

2 min read5 recall promptsReviewed 2026-10-10

Memory hook: Enroll, enforce, inventory, offboard.

Must remember

  • Basic mobile management provides lighter controls; advanced management adds supported device and application controls. Choose according to ownership, platform, edition and compliance requirements.
  • Distinguish company-owned devices from BYOD. An account wipe removes managed organizational data where supported; a full device wipe has much broader impact.
  • Inventory registered devices, inspect sync/activity and respond to loss or departure through a documented offboarding process. Removing a directory account is not a substitute for all device actions.
  • Enroll Chrome browsers into management and apply policies through the intended OU/group. Separate user policy from browser/device policy when diagnosing precedence.
  • Allow, block or force-install extensions based on business need and permissions. Manage update cadence and offline capabilities without leaving browsers permanently unpatched.
  • Verify policy application on the actual endpoint. A configured policy is only useful if the device is enrolled, in scope and communicating.

Choose under exam pressure

Requirement Choice and reason
Personal phone used for work Prefer targeted work-account removal when supported and sufficient.
Mandatory approved Chrome extension Managed browser enrollment and a scoped force-install policy.

Traps

  • A full wipe can remove personal data; check ownership and supported action semantics.
  • Installing Chrome does not automatically enroll it for enterprise management.

Active recall

1. What should offboarding include?

Revoke access, preserve required data and remove or wipe managed data on devices as appropriate.

2. Why inventory devices?

To identify ownership, compliance and stale or suspicious access.

3. What makes an extension risky?

Its permissions, publisher trust, update path and access to sensitive content.

4. Where investigate a policy not applying?

Enrollment, OU/group targeting, policy precedence and device synchronization.

5. Why stage browser updates?

To test compatibility while keeping security patches timely.

Sources

CLOSE THE NOTES. EXPLAIN THE CHOICE.

How well could you recall it?

Your next review is based on this answer. Progress stays in this browser.

Search across every published topic.