Which underlying technology does Workspace ONE Access use to collect Workspace ONE UEM device compliance information?

Question

Options

• AREST API
• BAirWatch Cloud Connector (ACC)
• CSOAP API
• DSecurity Assertion Markup Language (SAML)

• A
  87% (47)
• B
  7% (4)
• C
  2% (1)
• D
  4% (2)

Explanation

Workspace ONE Access uses a REST API to query Workspace ONE UEM and retrieve device compliance status, enabling it to enforce conditional access policies based on whether a device is compliant. REST APIs are the standard integration mechanism between modern VMware/Broadcom Workspace ONE components, providing lightweight, stateless communication that is well-suited for real-time compliance checks.

Why the distractors are wrong:

• B (AirWatch Cloud Connector): ACC is used to bridge on-premises directory services (like Active Directory) to cloud environments - it handles authentication proxying, not compliance data collection.
• C (SOAP API): SOAP is an older, heavier protocol not used in this Workspace ONE integration; VMware/Broadcom moved to REST-based architecture for inter-component communication.
• D (SAML): SAML is an authentication/federation protocol used to assert identity between an Identity Provider and Service Provider - it carries user authentication tokens, not device compliance data.

Memory tip: Think "Real-time Enforcement Starts with Trust" - REST API is how Workspace ONE Access trusts but verifies a device's compliance posture before granting access.

No community discussion yet for this question.