Just completed the troubleshoot course, and its clearly documented in course material you can run on prem without a cloud connector but the DS and CN server will need to be able to access the local domain (for example in PS integration you can do it without ACC). You will not be able to run the service without a console server

In a Workspace ONE UEM (Unified Endpoint Management) on-premises environment, the two core components that are typically required for all on-premises environments are: A. Device Services: Device Services is a core component that manages the device lifecycle, profiles, and policies in Workspace ONE UEM. E. Console Services: Console Services is the component responsible for hosting the Workspace ONE UEM administrative console, which allows administrators to configure and manage the Workspace ONE UEM environment. While components like the AirWatch Cloud Connector (B), Unified Access Gateway (C), and Secure Email Gateway (D) can be important for specific use cases or configurations, they are not always required for all on-premises environments. The specific components needed may vary based on your organization's requirements and setup.

A&E, ACC is only required if you want communication with your Back-End, which is not mandatory.

Only AE is correct in this scenario

Workspace ONE UEM consists of many services that come together to provide a single cohesive application. The term "core component refers to the service or software required for the platform to function at its most basic ability: • Workspace ONE UEM console server • Workspace ONE UEM device services • Workspace ONE UEM database • AirWatch Cloud Messaging (AWCM) service The AirWatch Cloud Messaging (AWCM) service works with AirWatch Cloud Connector to integrate Workspace ONE UEM with your back-end enterprise systems. BUT it's not mandatory

Admin Console & Device Service

It seems to be: A & E https://techzone.vmware.com/resource/workspace-one-uem-architecture#on-premises-architecture Syncing with internal resources such as Active Directory or a Certificate Authority can be achieved directly from the core components (Device Services and Admin Console) or using an AirWatch Cloud Connector. The implementation is separated into the three main components: - Workspace ONE UEM Admin Console - Workspace ONE UEM Device Services - AirWatch Cloud Connector

https://techzone.vmware.com/resource/workspace-one-uem-architecture#on-premises-architecture

Cloud connector is not necessary if all accounts are local to WS1 UEM.

On-Premises Architecture: The implementation is separated into the three main components: Workspace ONE UEM Admin Console Workspace ONE UEM Device Services AirWatch Cloud Connector Reference: https://techzone.vmware.com/resource/workspace-one-uem-architecture#on-premises-architecture

AWCC is required for on-prem. The implementation is separated into the three main components: Workspace ONE UEM Admin Console Workspace ONE UEM Device Services AirWatch Cloud Connector The AirWatch Cloud Messaging Service can be installed as part of the Workspace ONE UEM Device Services server, and the API Endpoint is installed as part of the Admin Console server. Depending on the scale of the environment, these can also be deployed on separate servers. In addition to the components already described for this cloud-based architecture, there are additional components required for an on-premises deployment.

It's A&E. ACC is not required on-prem

AE is the correct answer, the rest are optional components

I would say A+E. We don't use ACC in our on-prem environment

Per reference architecture, the diagram for on-prem architecture shows that Devices Services and AirWatch Cloud Connector are required: https://techzone.vmware.com/resource/workspace-one-uem-architecture#on-premises-architecture

CC is no requirement