Android Enterprise Support Engineer Answers
Android Enterprise Experts Certification Exam Answers
Indice del contenido
Module 1 Lesson 2 Answers
Q.1 – Match the question to its corresponding watchpoint. Drag each question to a box, then submit.
Select OS version/device – Are the critical apps, policies and configurations supported by the OS?
Set device policies – Are there multiple, conflicting policies set?
Upload apps – Did you target your private apps to your managed Google Play Accounts enterprise?
Provision device – Does the device have network connectivity in order to update and enroll successfully?
Module 1 Lesson 3 Answers
Customer reports that whitelisted apps aren’t showing up in managed Google Play. Which tool would you use to ensure that managed Google Play can assign and make apps available to users? – Android Management Experience
Customer reports that a policy to disable the camera is only working on some devices. Which tool would you use to test policy problems? – TestDPC
Customer reports that configured apps are crashing and policies aren’t being applied, how would you test that the EMM console is configured correctly? – Android Management API colab
Module 1 Lesson 5 Review Answers
(A) Watchpoints
(B) Problem solving framework
- (A) Carrier/reseller
- (B) OEM
- (C) EMM
- (D) Google
- (A) True
- (B) False
Compare the observed behavior against the expected behavior. – Describe behavior
Ask for screen captures, bug reports, and all other relevant information. – Gather data
Eliminate conflated issues or general confusion that misdiagnose root causes. – Trust but verify
Review common troubleshooting steps which may not apply to the issue or were skipped. – Review watchpoints
Consider the most common causes identified to narrow the scope of the issue. – Process of elimination
Identify systemic problems versus localized issues. – Reproduce issue
Module 2 Lesson 2 Answers
NFC – Transfer configurations to a new device using NFC hardware.
QR Code – Scan a code to enroll a device using the device camera.
DPC Identifier – Users enter a code to install a specific EMM agent.
Zero-touch enrollment – Enroll devices in bulk with full management and no manual setup.
Q.2 – Select each box and enter the missing word, then submit.
What is the minimum OS that supports provisioning using a QR code? – 7.0
How many different methods could you use to provision a dedicated device running Android 7.0? – 3
- (A) True
- (B) False
- (A) There’s no need for IT to physically handle the managed devices.
- (B) Device deployments are streamlined.
- (C) Configurations are automatically applied to devices on first boot.
- (D) Users can’t remove device management by simply factory resetting.
Module 2 Lesson 4 Answers
- (A) Observed
- (B) Expected
- (A) Expected
- (B) Observed
- (A) Android Management Experience
- (B) TestDPC
Q.4 – Select the watchpoints that apply to provisioning troubleshooting. Select 5 answers, then submit.
The five answers are:
- Select/bind EMM
- Provision device
- Select OS version/device
- Create/sync users or groups
- Configure provisioning
Q.5 – Which watchpoints can be ruled out?
Select and bind your EMM – Does the EMM you use support QR Code provisioning?
Select OS version/device – Does the device support QR code enrollment?
Create/sync users or groups – Is the user set up to be able to enroll devices?
Configure provisioning – Are the DPC extras specified in the QR code valid?
Provision device – Does the device have network connectivity in order to download the DPC?
- (A) Try regenerating the code
- (B) Test to see if NFC will work instead
- (C) Try on a different WiFi network, or using mobile data
- (D) Reach out to a carrier/reseller for additional support
- (A) Carrier/reseller
- (B) OEM
- (C) EMM
Q.8 – What information should you include when you escalate? Select all answers that apply, then submit.
- (A) Screenshot of error
- (B) Bug report
- (C) QR code
- (A) Expected
- (B) Observed
- (A) Observed
- (B) Expected
- (A) Screenshot
- (B) Zero-touch CSV export file
- (C) EMM configuration
- (D) Enrollment method
- (E) Bug report
- (A) Android Management Experience
- (B) Zero-touch portal
- (C) TestDPC
- (D) AM API Quickstart Colab
Q.13 – Select the watchpoints that apply to provisioning troubleshooting. Select 5 answers, then submit.
The five answers are:
- Create/sync users or groups
- Configure provisioning
- Provision device
- Select OS version/device
- Select/bind EMM
Select and bind your EMM – Does the EMM support zero-touch provisioning?
Select OS version/device – Is the device zero-touch compatible?
Create/sync users or groups – Are the correct IMEIs uploaded to the zero-touch portal? Is the user set up
Configure provisioning – Are the CSV values (e.g. IMEI, device model) entered correctly?
Provision device – Does the device have connectivity?
- (A) Ask the customer to verify the device is showing in the zero-touch portal
- (B) Verify that the device supports zero-touch
- (C) Verify that EMM configuration is correct and applied
- (D) All of the above
- (A) Applied
- (B) Not applied
- (A) Issue is unrelated
- (B) Zero-touch portal showing incorrect IMEI
- (A) Device model does not support zero-touch
- (B) The Kernel version does not match the OS version
- (C) Baseband version does not support WiFi
- (D) OS version does not support zero-touch
- (A) The serial number of the device is not present
- (B) The model type is not present
- (C) The zero-touch CSV lists the incorrect manufacturer
- (D) Issue is unrelated
- (A) Carrier/reseller
- (B) EMM
- (C) OEM
Module 2 Lesson 5 Review Answers
- (A) DPC Identifier
- (B) Zero-touch
- (C) NFC
- (D) QR Code
- (A) If the OS supports the method
- (B) If the device supports the method
- (C) If the carrier/reseller supports the method
- (D) If the EMM supports the method
Module 3 Lesson 2 Answers
Developer – When a developer builds an app for Google Play, they must meet certain requirements.
App + Schema – An app schema is a set of policies an app is willing to accept. This is included when the app is uploaded to Google Play.
Schema – The EMM console can read an app’s schema and display it in their UI. This allows IT admins to set the app configurations like server, name, server config, or security policy.
Config – Once the app is properly configured, the EMM will save the configurations and send it back to Google Play.
Configured app – At the time of installation, Google Play will deliver the app and its saved configurations to the device, providing a seamless end-user experience.
Module 3 Lesson 4 Answers
- (A) Observed
- (B) Expected
- (A) Expected
- (B) Observed
The four answers are:
- Bug report
- Package Names/IDs
- Play EMM API calls
- Enterprise, User, and Device IDs
- (A) Android Management Experience
- (B) TestDPC
- (C) AM API Quickstart Colab
Q.5 – Select the watchpoints that apply to application troubleshooting. Select 7 answers, then submit.
The seven answers are:
- Select OS version/device
- Select/bind EMM
- Create/sync users or groups
- Upload apps
- Set managed config
- Update apps/device
- Approve/assign apps
Q.6 – How could you rule out the following watchpoints? Select each box and make a selection, then submit.
Select/bind EMM – Is the enterprise still bound?
Select OS version/device – Is the application supported by the OS / device?
Create/sync users or groups – Is the application assigned to the correct users and/or groups?
Upload apps – Is the private app published and targeting your enterprise?
Approve/assign apps – Is the user able to find and install from the Play store?
Set managed config – Is the app configured correctly?
Update apps/device – Did the developer update the app and ask for additional permissions?
- (A) Check if users have connectivity
- (B) Verify that there are no conflicting policies
- (C) Confirm the app is approved in the EMM console
- (D) All of the above
Q.8 – From the customer, you’ve managed to collect the following screenshots:
1. The customer’s managed Google Play console
2. Device’s Play Store
3. The list of organization IDs in the Developer Google Play Console
4. Package ID
With this information, we can determine that… Select 1 answer, then submit.
(A) The Play Console isn’t listing the package ID
(B) The DPC has not been properly downloaded to the device
(C) The target organization has not been added to the list of approved organizations
(D) The package ID is incorrect
Q.9 – If this issue requires escalation, where should you escalate first? Select 1 answer, then submit.
- (A) Carrier/reseller
- (B) OEM
- (C) EMM
Q.10 – Which of the following is the best way to describe the behavior? Select 1 answer, then submit.
- (A) Customer is using Android 7.0 devices that should support G Suite apps, but they keep crashing.
- (B) Each time users open G Suite applications (Docs, Sheets, Slides, etc.) the apps prompt users to log into a personal Gmail account. Customer expects them to work only in an “offline” mode.
- (C) G Suite apps are crashing.
- (D) Customer wants G Suite apps to work on their devices.
- (A) Bug report
- (B) Logcat
- (A) AM API Quickstart Colab
- (B)TestDPC
- (C) Android Management Experience
The six answers are:
- Select/bind EMM
- Create/sync users or groups
- Update apps/device
- Set managed config
- Approve/assign apps
- Select OS version/device
Select/bind EMM – Is there a Google account on the device?
Select OS version/device – Does the app support the OS on the device?
Create/sync users or groups – Is the app approved for the user?
Approve/assign apps – Has the app being whitelisted in the managed Play Store?
Set managed config – Does the app require a specific configuration to function?
Update apps/device – Have app permissions recently changed?
- (A) Verify the user login credentials to the app are correct
- (B) Check the app’s managed configuration to see if it supports an “offline” mode and if it’s set correctly
- (C) Verify the app permissions have been set up correctly
- (D) Confirm that the app is approved in the EMM console
- (A) First Image
- (B) Second Image
- (C) Third Image
The four answers are:
- Screenshot or text of error encountered
- Bug report
- Reproduction steps taken
- App policy set on EMM console
Module 3 Lesson 5 Review Answers
- (A) Set device policies
- (B) Set managed config
- (C) Select/bind EMM
- (D) Provision device
Q.2 – Which tools will help to identify the source of an application issue? Select 2 answers, then submit.
- (A) TestDPC
- (B) Android Management Experience
- (C) AM API Quickstart Colab
- (A) True
- (B) False
Module 4 Lesson 4 Answers
- (A) Expected
- (B) Observed
- (A) Expected
- (B) Observed
The four answers are:
- Screenshot or text of error encountered
- Bug report
- Policy set on EMM console
- Model/Manufacturer, OS version
- (A) AM API Quickstart Colab
- (B) TestDPC
- (C) Android Management Experience
Q.5 – Select the watchpoints that apply to policy troubleshooting. Select 5 answers, then submit.
The five answers are:
- Update apps/device
- Select/bind EMM
- Select OS version/device
- Create/sync users or groups
- Set device policies
Select/bind EMM – Does the EMM support this policy?
Select OS version/device – Is the compliance policy only available on a specific OS version?
Create/sync users or groups – Does the policy target the desired user or user group?
Set device policies – Is the correct policy active and pushed to affected devices?
Update apps/device – Is there an OS update or security patch available that resolves the issue?
What is the OS running on the device where Bluetooth is disabled? – 8.1.0
What is the OS running on the device where Bluetooth is still enabled? – 7.1.2
Q.8 – What is the API level that corresponds to Android 8.0? Select 1 answer, then submit.
- (A) API level 25
- (B) API level 26
- (C) API level 27
- (D) API level 28
- (A) The no_bluetooth policy has a minimum supported OS of 8.0 so devices running 7.0 will need to be updated or replaced.
- (B) The bug reports indicate that both are dedicated devices so any Bluetooth policy is redundant.
- (C) The no_config_bluetooth policy has a minimum supported OS of 8.0 so the issue will need to be escalated to the EMM.
- (D) The no_bluetooth and no_config_bluetooth policies are conflicting and one needs to be removed.
- (A) Check the policy properly configured
- (B) Verify the policy supported by the EMM
- (C) Confirm the phone has network connectivity for the policy to be applied
- (D) All of the above
- (A) Escalate to carrier/reseller
- (B) Resolve issue
- (C) Escalate to OEM
- (D) Escalate to EMM
- (A) Observed
- (B) Expected
- (A) Observed
- (B) Expected
The four answers are:
- Policy set on EMM console
- Screenshot or text of error encountered
- Bug report
- Model/Manufacturer, OS version
- (A) DUMP OF SERVICE activity
- (B) DUMP OF SERVICE account
- (C) DUMP OF SERVICE device_policy
- (A) TestDPC
- (B) Android Management Experience
- (C) AM API Quickstart Colab
Q.17 – Select the watchpoints that apply to policy troubleshooting. Select 4 answers, then submit.
The four answers are:
- Create/sync users or groups
- Set device policies
- Select OS version/device
- Select/bind EMM
Does the EMM support this policy? – Select/bind EMM
Does the device support the network you’re trying to configure? – Select OS version/device
Does the policy target the desired user or user group? – Create/sync users or groups
Is the correct policy active and pushed to affected devices and is the SSID and password correct? – Set device policies
- (A) Is the policy properly configured in the EMM?
- (B) Check the EMM Solutions directory – is the policy supported by the EMM?
- (C) Does the device/OS support the network you’re trying to configure?
- (D) Is the correct policy set?
- (E) Is there a policy conflict (multiple policies targeting the same device)?
- (F) All of the above
Q.20 – Is the WiFi configuration correct? Select 1 answer, then submit.
- (A) Incorrect
- (B) Correct
Q.21 – If incorrect, which part of the configuration needs to be changed? Select 1 answer, then submit.
- (A) SSID
- (B) Security type
- (C) WiFi password
- (D) Nothing – the configuration is setup correctly
- (A) Escalate to OEM
- (B) Escalate to EMM
- (C) Resolve issue
- (D) Escalate to carrier/reseller
Module 4 Lesson 5 Review Answers
- (A) True
- (B) False
- (A) Set device policies
- (B) Upload apps
- (C) Select/bind EMM
- (D) Provision device
Q.3 – What’s a policy that can only be set on a work profile? Select 1 answer, then submit.
- (A) Disable screenshot
- (B) Cross profile contact sync
- (C) Verify apps enforcement
- (D) Certificate Installation
Android Enterprise Support Engineer Final Assessment Answers
Module 5 Final Review Answers
- (A) Expected
- (B) Observed
- (A) Expected
- (B) Observed
The six answers are:
- Affected devices model/OS
- Managed app configuration
- Screenshots
- Bug report
- In-app feedback
- Play EMM API calls
- (A) Check the EMM console
- (B) Ask the user
Q.5 – Which of the following tools could Tomas use to test the Gmail app? Select 2 answers, then submit.
- (A) AM API Quickstart Colab
- (B) TestDPC
- (C) Android Management Experience
Q.6 – Select the watchpoints that apply to application troubleshooting. Select 4 answers, then submit.
The four answers are:
- Select/bind EMM
- Update apps/device
- Set managed config
- Set device policies
Q.7 – What watchpoints can be ruled out? Select each box and make a selection, then submit.
Select/bind EMM – Is the enterprise still bound so that managed configurations can be pushed?
Set device policy – Are any policies interfering with connectivity? Are the correct certificate(s) on the device, if needed?
Set managed config – Is the managed app configuration correct? (e.g. server URL, sync window, etc)
Update apps/device – Did the Exchange environment, the Gmail app, or the managed app config change recently?
- (A) Check if users have connectivity
- (B) Verify that there are no conflicting policies
- (C) Check Gmails configurations and sync window settings
- (D) All of the above
- (A) The hostname is incorrect
- (B) SSL Required should be off
- (C) There’s no default email signature
- (D) The username is incorrect
- (E) The user logged into Gmail with an incorrect email address
- (F) There’s no Login Certificate Alias
- (G) Default Sync Window is too narrow
- (H) The email address in Managed Configuration is incorrect
- (A) 3
- (B) 4
- (C) 0
- (D) 2
- (E) 5
- (F) 1
- (A) Escalate to carrier/reseller
- (B) Escalate to EMM
- (C) Escalate to OEM
The 4 answers are:
- Play EMM API calls
- Bug report
- App policy set on EMM console
- Reproduction steps taken
- (A) Observed
- (B) Expected
- (A) Observed
- (B) Expected
The four answers are:
- Policy details
- Contacts / dialer app information
- Bug report
- Screenshot
- (A) EMM console
- (B) Bug report
- (C) Zero-touch CSV export file
- (D) Logcat
Q.17 – Select the watchpoints that apply to troubleshooting Amy’s problem. Select 4 answers, then submit.
The 4 answers are:
- Select OS version/device
- Set device policies
- Update apps/device
- Select/bind EMM
Does the EMM support cross profile contacts and caller ID policies? – Select/bind EMM
Does the device support contact search in work profiles? – Select OS version/device
Are cross profile caller ID and cross profile contact search policies applied? – Set device policies
Does the app cross profile caller ID and contacts search? Is there an app update pending? – Update app/device
- (A) DUMP OF SERVICE account
- (B) DUMP OF SERVICE crossprofileapps
- (C) DUMP OF SERVICE device_policy
- (D) DUMP OF SERVICE connectivity
- (A) Cross-profile data management
- (B) Cross-profile contact management
Q.21 – From the bug report snippet, has the policy been applied? Select 1 answer, then submit.
- (A) The policy has not been applied to the device
- (B) The policy has been applied to the device but isn’t working
- (A) Resolve issue
- (B) Escalate to carrier/reseller
- (C) Escalate to OEM / app developer
- (D) Escalate to EMM
- (A) Escalate to OEM / app developer
- (B) Escalate to EMM
- (C) Escalate to carrier/reseller
- (D) Resolve issue
Android Enterprise Support Engineer Answers