5V0-62.22 VMware Workspace ONE 21.X UEM Troubleshooting Specialist Free Practice Exam Questions (2025 Updated)

The strategy that accurately describes the solution for this problem is running the keytool import targeting the new certificate. The AWCM keystore is a Java keystore file that contains the SSL certificates used by AWCM to establish secure connections with devices and other components. If the SSL certificates are rotated on IIS and the load balancer, but not on the AWCM keystore, then AWCM will not be able to communicate with devices using push notifications. To resolve this issue, the administrator must import the new SSL certificates into the AWCM keystore using the keytool command2.

The component that should be focused on when troubleshooting this device connectivity issue to VMware Workspace ONE UEM is Device Services. Device Services is a component of Workspace ONE UEM that handles device enrollment, management, and communication. Device Services also hosts the AWCM service, which is responsible for delivering push notifications to devices. If Device Services is not working properly, devices may not be able to check in with Workspace ONE UEM or receive profiles, commands, or policies3.

The misconfiguration that would be causing this behavior is AWCM Persistence is not correctly configured. AWCM Persistence is a setting that ensures that devices maintain a consistent connection with the same AWCM server in a load-balanced environment. If AWCM Persistence is not correctly configured, devices may be bounced between different AWCM servers and cause enrollment failures or communication errors. The administrator should check and configure AWCM Persistence properly.

The most likely cause of this issue is that the organization’s Apple Push Notification certificate expired. The Apple Push Notification certificate is required for iOS devices to communicate with Workspace ONE UEM and receive commands, profiles, and applications2. If the certificate expires, the iOS devices will not be able to receive any updates from Workspace ONE UEM, including the application catalog. The organization should renew the certificate as soon as possible to restore the functionality of the iOS devices3. The other options are not likely causes of this issue because:

A misconfigured application assignment via a smart group would affect all devices in the smart group, not just iOS devices.

A misconfigured application assignment via the enrollment type would affect all devices with the same enrollment type, not just iOS devices.

An expired Apple sToken would prevent the organization from purchasing or distributing new applications from Apple Business Manager or Apple School Manager, but it would not affect the existing applications in the Workspace ONE Catalog.

 The reason that this problem is occurring is that the Workspace ONE UEM Console stopped communicating with VMware AirWatch Cloud Messaging (AWCM). AWCM is a service that delivers push notifications to devices and enables device-based commands from the Workspace ONE UEM Console3. If the Workspace ONE UEM Console cannot communicate with AWCM, it will not be able to send commands to devices, such as “Lock Device”. The administrator should check and resolve any issues with AWCM connectivity.

 The two root causes that could possibly cause this problem are that the device has not checked in with the Workspace ONE UEM tenant, and that the Policy Engine Service is not running. The device check-in is a process that updates the device status and information in the Workspace ONE UEM console3. If the device has not checked in with the Workspace ONE UEM tenant, it will not receive the latest compliance policy or report its compliance status. The Policy Engine Service is a service that evaluates and enforces compliance policies on devices. If the Policy Engine Service is not running, it will not be able to detect or remediate non-compliant devices. The administrator should check and resolve any issues with device check-in and Policy Engine Service.

The logging level for AirWatch Cloud Connector should be changed in the CloudConnector.exe.config file. This file contains various settings for ACC (AirWatch Cloud Connector), such as logging level, proxy settings, service URLs, and so on. The administrator can edit this file to change the logging level for ACC from default to verbose or debug, which can provide more detailed information for troubleshooting purposes.

 The three actions that can be enabled for users to self-manage devices through the Self-Service Portal are generate targeted log, upload SMIME certificate, and sync device. The Self-Service Portal is a web-based application that allows users to perform various actions on their enrolled devices, such as lock, unlock, wipe, or unenroll. Users can also generate targeted log to collect device logs for troubleshooting purposes, upload SMIME certificate to enable secure email communication, and sync device to update device information and settings in the Workspace ONE UEM console.

 The component that the administrator should enable verbose logging on is UAG (Unified Access Gateway) Edge service. UAG is a component that provides secure edge services for Workspace ONE UEM, such as VMware Tunnel, Content Gateway, or Secure Email Gateway2. If users are receiving a timeout error when accessing files using the Workspace ONE Content application, it could indicate that there is a problem with UAG configuration, connectivity, or performance. Enabling verbose logging for UAG can help identify and troubleshoot the issue.

Flushing the cache via the Workspace ONE UEM console. Memcached is a service that caches data in memory for faster access and performance. If a configuration value is updated in Workspace ONE UEM, it may take some time for Memcached to refresh the cached data and reflect the new value. Flushing the cache via the Workspace ONE UEM console can force Memcached to clear the cached data and update it with the latest value.

The option that is available for Unified Access Gateway to export a collection of all logs is using the UAG-log-archive.zip download button from the Support Settings section in the UAG Admin UI. This ZIP file contains all logs from the Unified Access Gateway appliance, such as system information, network configuration, edge service logs, and so on4. This option can help troubleshoot any issues or errors related to Unified Access Gateway deployment and operation.

The service that can help meet this goal is the Self-Service Portal. The Self-Service Portal is a web-based application that allows users to perform various actions on their enrolled devices, such as lock, unlock, wipe, or unenroll1. Users can also reset their device passcode through the Self-Service Portal, which can reduce the number of help desk tickets and improve user satisfaction2.

The root cause of this issue is that Workspace ONE Assist agent failed to connect to the Workspace ONE Assist server. The request timeout error indicates that the Workspace ONE Assist agent did not receive a response from the Workspace ONE Assist server within the specified time limit3. This could be due to network issues, firewall settings, or authentication problems. The administrator should check and resolve these issues to enable remote sessions using Workspace ONE Assist.

The two log files that would be used to troubleshoot issues related to this Directory synchronizations are DirectorySyncServiceLogFile.log and CloudConnector.log. DirectorySyncServiceLogFile.log is a log file that records the directory synchronization process between Workspace ONE UEM and Active Directory or LDAP. CloudConnector.log is a log file that records the communication and synchronization between Workspace ONE UEM and ACC (AirWatch Cloud Connector), which is a service that integrates Workspace ONE UEM with internal enterprise systems, such as Active Directory or Certificate Authority. These log files can help identify and troubleshoot any errors or issues related to directory synchronization.

 The most likely cause of this issue is that the application installation file is corrupted. A corrupted file may cause the application installation to fail or abort on the devices4. The administrator should verify the integrity of the application installation file and upload a new file if needed.

The reason that this certificate authority integration test connection failed is that fetching the root certificate from CA failed. The root certificate from CA is a certificate that validates the identity and trustworthiness of the certificate authority (CA) that issues certificates for devices. Workspace ONE UEM needs to fetch the root certificate from CA to verify and manage certificates for devices. If fetching the root certificate from CA failed, it could indicate that there is a problem with CA configuration, connectivity, or availability. Workspace ONE UEM will not be able to connect to CA or issue certificates for devices, and the certificate authority integration test connection will fail.

The console page that would confirm a potential configuration change is Monitor > Reports & Analytics > Events > Console Events. This page allows the administrator to view and filter the events that occurred in the Workspace ONE UEM console, such as configuration changes, user actions, system errors, and so on. The administrator can use this page to find out if a configuration was enabled by mistake that caused the error.