vmartinez

A WiFi configuration was pushed out via the EMM instance that would automatically connect users to the recently upgraded office network. Is this behavior: Select 1 answer, then submit.

 

• (A) Observed

 

• (B) Expected

 

Since the policy is not supported by the minimum OS on the device, would you resolve the issue or escalate to a partner? Select 1 answer, then submit.

 

• (A) Escalate to carrier/reseller
• (B) Resolve issue
• (C) Escalate to OEM
• (D) Escalate to EMM

 

Taking our answers from the previous activity, why would the Bluetooth policy not be applied to a number of the devices? Select 1 answer, then submit.

 

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

 

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

 

Answer the questions using the bug report snippets above as a resource. Select each box and make a selection, then submit.

 

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

 

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