220-1202 Practice Question: A technician is configuring a company-issued…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Set up a separate User account for work.

  Why it's wrong here

  Setting up a separate User account for work on an Android device creates a completely distinct user environment, requiring the employee to log out of their personal account and into the work account to access corporate applications and data. This process is cumbersome and inefficient for a single individual who needs to seamlessly switch between personal and work applications throughout the day, as it does not allow for simultaneous access or integrated notifications.

• ✓

  Enable the Work Profile via the device's Settings under Accounts.

  Why this is correct

  Enabling the Work Profile via the device's Settings under Accounts is the correct and most efficient method for configuring a company-issued Android phone. This feature creates a secure, managed container for all work-related applications, data, and accounts, keeping them entirely separate from personal content on the same device. IT administrators can enforce specific security policies and manage applications within this profile without intruding on the user's personal data or privacy, offering a seamless and secure experience.

• ✗

  Use Screen Pinning to lock the device to the email app.

  Why it's wrong here

  Using Screen Pinning to lock the device to the email app is an inappropriate solution for configuring a company-issued phone for general use. Screen Pinning is a temporary security feature designed to restrict a device to a single application, preventing access to other apps or device settings until unpinned. This functionality is entirely unsuitable for an employee who requires access to multiple work applications (e.g., calendar, documents, communication tools) in addition to personal apps, as it severely limits device functionality.

• ✗

  Install a third-party MDM agent only.

  Why it's wrong here

  Installing a third-party MDM (Mobile Device Management) agent only, without leveraging Android's native Work Profile feature, is less secure and offers weaker data separation. While an MDM agent can enforce policies, without the containerization provided by a Work Profile, the agent may operate with broader device administrator permissions, potentially gaining access to personal data or applying policies globally across the entire device. This approach lacks the robust, built-in segregation and privacy safeguards that a Work Profile provides for corporate data.

Go deeper

Related to this question