Question 1 of 20: Overview of Android Enterprise

Mika, a new marketing intern, has enrolled her personally owned device into her employer's EMM solution, known as the BYOD (Bring Your Own Device) use case. What can Mika's IT manager do on her device in this case?

• Fully erase the device at any time completely wiping the device of all data without the ability to only erase company data.
• Read personal text messages, view personal photos and capture all data on the device regardless it being personal or work data.
• Provide Mika with fully compliant access to company IT resources and apps completely separated by the work profile with no access to her personal profile and data.
• Use the device processors to mine crypto currency when their device is charging at night while they sleep to earn bonuses.

---

Question 2 of 20: Overview of Android Enterprise

When deploying managed devices, there will be a few different organizations involved with different roles and responsibilities. Which of the following parties is required to supply and distribute devices?

• Service Providers
• Device resellers
• Google
• OEM Manufacturers

---

Question 3 of 20: Overview of Android Enterprise

You are talking to the procurement officer of Bank Corp. He asks about the Android Enterprise Recommended program and the device types that are listed. What are some of the device types that part of the Android Enterprise Recommended OEM program?

• Premium Devices, Budget Devices, Rugged Devices and Purpose Built Devices
• Only Premium devices
• Only Google Pixel devices
• Only devices that have screens larger than 5.5 inches

---

Question 4 of 20: Overview of Android Enterprise

One of the use cases that Android Enterprise offers is to allow the use of both personal and work in one device using work profile. What is the benefit of work profile?

• A work profile is only helpful seperating network traffic.
• A work profile comes with a new mobile number offered by Google.
• Work profile applications delete after every user session and install the next time automatically.
• A work profile can be set up on an Android device to separate work and personal apps/data. With a work profile you can securely and privately use the same device for work and personal purposes.

---

Question 5 of 20: Overview of Android Enterprise

What is the key benefit of the Google-built Android Enterprise Recommended program for Enterprise users?

• This program helps Enterprise users to choose device model, EMM solutions and/or Service Providers that meet a higher enterprise requirement and are recommended by Google.
• Only devices and services on the list work with Android Enterprise.
• All Android Enterprise Recommended devices come with pre-installed enterprise applications by Google.
• Because OEM's and services pay to be part of the service, you can be confident that these services meet the high bar.

---

Question 6 of 20: Enterprise Mobility

Device management is widely used by organizations around the world. Which of the following is NOT an Enterprise Mobility use case that you probably often see in your daily life?

• Using an E-Menu tablet in a restaurant to place an order faster directly to the kitchen without calling the waiter.
• An employee using a managed Android device owned by the company that has been customized into a barcode scanner to perform a job faster anywhere.
• None of these - they are all Enterprise mobility use-cases.
• An employee uses his mobile device to send a personal text message to his colleague to invite him to a friendly afterwork.

---

Question 7 of 20: Enterprise Mobility

Bank Corp, with a variety of use cases in their organization, have selected Android for their company-owned devices. What are the management modes available to use with their devices? (Select 2 options)

• Company-owned Personally Enabled Device
• Productivity
• Bring Your Own Device (BYOD)
• Company-owned Dedicated device

---

Question 8 of 20: Enterprise Mobility

What are the main benefits of using Android for business?

• 1. Productivity Apps 2. Security 3. Deployment 4. Flexibility
• 1. Ease of use 2. Deployment 3. Budget 4. Security
• 1. Security 2. High Cost 3. Scalability 4. Productivity Apps
• 1. Flexibility 2. Personal 3. Affordable 4. Reliable

---

Question 9 of 20: Basics of Android Security

Which of the following protects Android devices against security vulnerabilities? (Select 3 options)

• Encryption
• Regular and controlled updates
• Verified Boot
• Social engineering

---

Question 10 of 20: Basics of Android Security

How often does Google issue Android security patches?

• Once a year
• Every 7 days
• Every 90 days
• Every 30 days

---

Question 11 of 20: Basics of Android Security

Jana from Sales Ltd is worried about custom operating systems or malicious code being installed on her fleet of managed devices. You remember the concept of verified boot from your Android Enterprise training. How would you explain Verified Boot to Jana?

• Verified Boot ensures the device will boot up within 30 seconds to prevent end users from becoming inpatient and attempting to root their devices.
• Verified Boot confirms all executed code has passed the code review by the companies IT department and they have authorized the device to access corporate IT resources such as email and apps.
• Verified Boot asks the user every single time what good version of the operating system they would like to boot up in.
• Verified Boot ensures all executed code comes from a trusted source (usually device manufacturers), and has not been modified by an attacker or corrupted. By verifying the OS it ensures a device will be running a safe version of Android.

---

Question 12 of 20: Basics of Android Security

You are talking to Bina, the CIO of Sales LTD. They are concerned that apps on Android share data by default. You realize they could benefit from understanding Application Sandboxing a little better. How would explain this concept to Bina?

• Application Sandboxing ensures apps and data are able to share from others (like at a playground sandbox), meaning that data can be accessed by apps that do not have the authority. It also helps harmful app accessing any data from the OS or any other apps by throwing sand in the bad apps containers.
• Application Sandboxing is a technology that allows each app to create its own virtual sandbox and limit the end user from being able to copy and paste data from the app into another app.
• Application Sandboxing encloses apps and data in their own virtual sandcastles, meaning that data can only be accessed by entering the end users passcode. It also protects against harmful users by crumbling the sandbox in the event a new user is discovered.
• Application Sandboxing ensures apps and data are isolated from others, meaning that data cannot be accessed by apps that do not have the authority. It also protects against a harmful app accessing any data from the OS or any other apps.

---

Question 13 of 20: Basics of Android Security

Android Enterprise creates "defense in depth" by using four layers of protection. Identify the two layers from the given list. (Select 2 options)

• Emojis: Android supports Emojis which are pictograms, smileys and other graphics used in electronic messages and web pages. The emoji's primary function is to fill the end user with positive emotions to position them in happier and more secure place while using their device.
• Google Play Protect: provides 24/7 mobile security that scans apps and devices. Using machine learning, it detects and blocks malware, constantly learning so it’s always up to date to protect users from the latest threats.
• Dynamic Wallpaper: Android Devices support animated background images that can be used as the devices wall paper that will confuse a would be hacker and discorage them from attempting to exploit the device.
• Hardware: Android devices have tamper-resistant hardware to ensure the OS hasn’t been compromised. Dedicated components handle critical tasks like encryption or screen lock.

---

Question 14 of 20: Basics of Android Security

The App Defense Alliance was created to ensure the safety of Google Play. What appropriate action can be taken to protect users?

• Partners of the App Defense Alliance can send a request to the Google Play Protect scanner service to have an app analyzed.
• New app risk intelligence can be generated as apps are being queued to publish and partners will analyze that dataset before the availablity of an app on Google Play to protect users.
• Scan results can be sent back to the partner and Google Play Protect receives analysis from the partner's scanning engines to protect the users.
• All of these

---

Question 15 of 20: Zero-touch

Liz, a customer, wants to turn on her zero-touch device for the first time. What does she need to do?

• Plug it in and let it charge for 24 hours prior to doing anything else and do not touch it.
• Literally nothing. Liz just needs to turn it on and not touch it.
• Go through the standard Android device set up, then add their company email account to begin the zero-touch enrollment process.
• Simply power on the device, connect to a wifi or cellular data network and touch through the set up screens to automatically enroll the device on the company's EMM solution and receive all the required configurations, apps and security policies.

---

Question 16 of 20: Zero-touch

Bank Corp is looking to deploy 3000 Android devices using zero-touch. What are some of the benefits of this type of deployment?

• Increase productivity for users
• Enforced management and security for organizations
• All of these
• Simplicity and flexibility for IT

---

Question 17 of 20: Zero-touch

When can a customer get access to the zero-touch customer portal?

• The device manufacturer creates one for the customer.
• The EMM provider enrolls their devices.
• The customer signs up and creates it.
• After the reseller creates an account for the customer.

---

Question 18 of 20: Zero-touch

Which Android Enterprise device enrollment method requires little to no interaction with an end user's device from IT?

• Zero-touch
• QR Code
• NFC
• DPC

---

Question 19 of 20: Zero-touch

When deploying wifi only devices with zero-touch, what information is needed from the devices?

• Manufacturer, Model, Serial Number
• IMEI, Screen size, Serial Number
• Model, Manufacturer, IMEI
• Manufacturer, Serial Number, MAC Address

---

Question 20 of 20: Zero-touch

Who can add devices to a customer’s zero-touch account?

• The EMM provider
• The device manufacturer only
• The customer IT Admin
• The device reseller and/or their vendors (if enabled)

Are You Being Watched Over by Your Company Using WorkspaceONE Intelligent Hub?

In the age of smartphones and digital connectivity, the lines between our personal and professional lives have blurred. Many companies now encourage or even require their employees to use their personal mobile devices for work-related tasks. It's convenient, cost-effective, and promotes flexibility in today's fast-paced business world. However, the rise of bring-your-own-device (BYOD) policies and mobile working has given rise to concerns about privacy and security. One solution that businesses turn to for managing this mobile workforce is Workspace ONE Unified Endpoint Management (UEM), often accessed through the Intelligent Hub app. But what exactly can Workspace ONE UEM see on your mobile device, and should you be concerned about your personal data when using it for work-related tasks?

Workspace ONE UEM and the Intelligent Hub

WorkspaceONE UEM, formerly known as AirWatch, is an enterprise mobility management (EMM) platform developed by VMware. It's designed to help businesses manage and secure mobile devices, applications, and data. The Intelligent Hub is the user-facing app that allows employees to access company resources and manage work-related tasks on their mobile devices. It can be installed on various platforms, including Android and iOS.

Workspace ONE offers a range of features that benefit both businesses and employees. These features include secure application management, mobile device management, and data protection. However, with such power comes a natural concern about how much visibility and control a company has over the personal devices of its employees.

The Balancing Act: Security vs. Privacy

When you enroll your personal device in your company's Workspace ONE UEM program, you're essentially granting the organization certain rights to manage and secure the device. The level of control and visibility a company has over your device varies based on the policies and configurations set by your organization. This is where the balancing act between security and privacy comes into play.

Here are some key aspects to consider:

1. Compliance Policies:

Workspace ONE UEM allows organizations to set compliance policies for enrolled devices. These policies may include requirements for encryption, passcode complexity, and security updates. The company can ensure that your device complies with these policies, which is essential for protecting sensitive company data.

2. Application Management:

Employers can deploy, manage, and update enterprise apps on your device. They may also have the ability to whitelist or blacklist certain apps. This helps ensure that only approved apps are used for work-related tasks.

3. Remote Management:

In the event that your device is lost or stolen, Workspace ONE UEM allows your company's IT department to remotely lock or wipe the device to protect sensitive data. This feature is crucial for data security.

4. Device Information:

Your company can access device details, such as the model, operating system, serial number, and hardware specifications. This information helps with device inventory and management.

5. Content Distribution:

Employers can distribute and manage documents, files, or resources to your device, making it easier to access important work-related materials.

6. VPN Configuration:

Your company can configure and manage VPN connections on your device, ensuring secure access to the organization's network.

7. Network and Connectivity:

IT administrators can manage Wi-Fi profiles and network settings on your device, which is essential for ensuring secure connections.

8. Reporting and Analytics:

Workspace ONE UEM provides the ability to generate reports on device usage, security compliance, and other relevant metrics, which can help organizations track and improve their mobile management strategies.

Privacy Concerns and User Awareness

With this array of capabilities, it's natural to have concerns about privacy when enrolling your personal device in Workspace ONE UEM. However, it's essential to understand that organizations typically operate within the boundaries set by their mobile device management (MDM) policies and relevant regulations. They are also often committed to respecting your privacy while ensuring the security of company data.

To address these concerns and maintain a balance between security and privacy, here are some best practices and points to consider:

1. Clear Policies:

Employers should have clear BYOD policies in place. These policies should outline the extent of monitoring and control over personal devices and should be communicated to employees.

2. Consent:

Employees should be asked to give their explicit consent before enrolling their personal devices. This ensures that employees are aware of what is being monitored and controlled.

3. Separation of Work and Personal Data:

Workspace ONE UEM can often separate work-related data and applications from personal data on the device, preserving your privacy.

4. Remote Wipe Procedures:

Employers should establish clear procedures for remote device wipe and ensure they are only used when necessary, such as in the case of a lost or stolen device.

5. Limited Data Access:

Workspace ONE UEM can be configured to restrict access to specific device data, such as personal photos, contacts, or messages, depending on company policies.

6. Regular Auditing:

Companies should regularly audit and review their MDM policies to ensure they are in compliance with privacy regulations and respect user privacy.

7. Employee Education:

Employers should educate employees about the capabilities of Workspace ONE UEM and the importance of following security policies.

Conclusion

So, are you being watched over by your company using Workspace ONE UEM's Intelligent Hub? The answer is yes, but within certain boundaries. Employers have the ability to manage and secure devices to protect sensitive company data, but they are also committed to respecting employee privacy.

To ensure a fair and transparent balance between security and privacy, it's crucial for organizations to establish clear policies, seek employee consent, and educate their workforce about the capabilities of Workspace ONE UEM. This way, employees can enjoy the benefits of mobile working while trusting that their personal data remains private and secure.

Remember that the specifics of what an organization can see and control on your device will depend on your employer's policies and configurations. It's always a good practice to have an open dialogue with your employer about any privacy concerns you may have when enrolling your personal device in a company's mobile device management program.

Disclaimer:

The information provided in this blog is intended for general informational purposes only. It is not legal advice or a comprehensive guide to the specific features and functionalities of Workspace ONE Unified Endpoint Management (UEM) or the Intelligent Hub app.

The capabilities and policies related to WorkspaceONE UEM may vary from one organization to another. The level of control and visibility that an organization has over personal devices enrolled in their Workspace ONE UEM program depends on the specific policies and configurations set by the organization, as well as any applicable laws and regulations.

Readers should be aware that while Workspace ONE UEM is designed to help organizations manage and secure mobile devices, it should be used in accordance with applicable privacy regulations and with respect for user privacy. Employees are encouraged to consult with their employers and IT departments for detailed information about the specific policies and practices in place within their organizations.

The blog content is not a substitute for professional legal or IT advice. Any action taken based on the information provided in this blog is at the reader's own discretion and risk. As a author, I do not assume any responsibility for any consequences that may arise from the use or interpretation of this information. Readers are encouraged to seek guidance from relevant legal and IT professionals for their specific circumstances and concerns.

Understanding the Importance of the EnterpriseID in Google's EMM Program and locate EnterpriseID

As more and more organizations adopt mobile devices and cloud-based services, managing and securing these devices has become a top priority. Google's Enterprise Mobility Management (EMM) program offers a solution for managing mobile devices and apps in the enterprise. One of the key elements of this program is the EnterpriseID, which is a unique identifier assigned to each organization that enrolls in EMM.

So what exactly is an EnterpriseID, and why is it important for EMM?

An EnterpriseID is a unique identifier that is assigned to an organization when they enroll in Google's EMM program. This ID is used to identify the organization within Google's systems and is required for managing devices and deploying apps through EMM.

Why is the EnterpriseID important for EMM? There are a few reasons:

Device management: The EnterpriseID is used to manage devices in EMM. When devices are enrolled in EMM, they are associated with the organization's EnterpriseID. This allows administrators to manage these devices and apply policies and configurations to them.

App deployment: The EnterpriseID is also used to deploy apps to devices in EMM. When an app is deployed through EMM, it is associated with the organization's EnterpriseID. This allows administrators to control which apps are available to users and ensure that only authorized apps are installed on company-owned devices.

API integration: The EnterpriseID is used to set up the Google Mobile Management (GMM) API, which allows EMM administrators to manage devices and apps programmatically. This API is used to integrate EMM with other enterprise systems, such as helpdesk and inventory management tools.

Now that we understand why the EnterpriseID is important, let's take a look at how to find it. If you are the administrator of an organization that has enrolled in Google's EMM program, you can find the EnterpriseID in the Google Cloud Console or the Google Admin Console.

To find the EnterpriseID in the Google Cloud Console, follow these steps:

• Log in to the Google Cloud Console with your EMM administrator account.
• In the left-hand navigation menu, click on "IAM & Admin."
• Click on "Settings" in the submenu that appears.
• Under "Organization Settings," you should see your EnterpriseID listed.

To find the EnterpriseID in the Google Admin Console, follow these steps:

• Log in to the Google Admin Console with your EMM administrator account.
• In the left-hand navigation menu, click on "Billing."
• Under "Subscriptions," you should see your EnterpriseID listed next to your EMM subscription.
• If you do not have access to either the Google Cloud Console or the Google Admin Console, you may need to contact your EMM administrator or Google Workspace support for assistance in finding your EnterpriseID.

In conclusion, the EnterpriseID is a critical component of Google's EMM program. It is used to manage devices, deploy apps, and integrate EMM with other enterprise systems. By understanding what an EnterpriseID is and how to find it, EMM administrators can ensure that their organization's mobile devices and apps are secure and effectively managed.