10 free sample questions from a bank of 55, with the correct answers and explanations. No signup required — start practising right now.
Verdict: D and E — OAUTH, and Certificate Based Authentication
The Workspace ONE UEM console itself can be protected in two ways that authenticate the administrator
to the console: an OAuth 2.0 flow (federated sign-in through an identity provider such as Azure AD
or Okta) and Certificate Based Authentication, where the console is reached with a client
certificate instead of a password. SAML and Azure AD are Access-side concepts; CAPTCHAs are a
bot-mitigation control, never an authentication method.
through an external identity provider.
certificate issued to the admin device or smart card.
the two above.
is an Access identity-provider configuration item, not a UEM console authentication method.
Option D, OAuth, is how a SaaS console delegates authentication to a cloud identity provider: the
admin is redirected to the IdP, returns with an access token, and never types a console password.
Option E, certificate based authentication, is the other passwordless path the console supports, where
the presented client certificate is validated against the console's trusted CA store. Those are the two
methods that authenticate an administrator into the console, which is what the stem asks for.
SSO in the catalog. The UEM console administrator sign-in is not configured with SAML metadata.
OAuth (or SAML in Access); there is no "Azure AD" authentication method tile in the console.
and appears nowhere in the console's authentication configuration.
Sort every authentication question into three buckets: who holds the credential (user vs
administrator), what protocol carries it (OAuth, SAML, certificate, Kerberos), and what product
consumes it (UEM console vs Access vs Secure Email Gateway). This row fails the moment Azure AD is
mistaken for a method instead of a provider.
Verdict: D — AirWatch Cloud Connector
Of the four auxiliary components, only the AirWatch Cloud Connector (ACC) updates itself after a
console upgrade in its default configuration. It polls the SaaS service outbound over AirWatch Cloud
Messaging and pulls down the matching build without administrator intervention. The UAG appliance
(including its Secure Email Gateway add-on) and the Workspace ONE Access connector are both upgraded
deliberately, by hand, by an administrator.
brokers SaaS-to-on-premises traffic (directory sync, PKI, syslog, PowerShell, email relay) in
outbound-only mode. Documented as being configurable for automatic updates.
what makes unattended ACC self-update possible.
by an admin with APPLY PATCH / the upgrade bundle, never self-updating.
UAG appliance itself is upgraded.
installer/appliance package by hand.
The stem asks about a default configuration and about self-updating after an upgrade. The ACC is
version-coupled to the console: when the SaaS console moves to a new release, the console flags the
connected ACC as out of date and the connector updates itself. The reference architecture spells this
out — the ACC "is hosted in your internal network in outbound-only mode and **can be configured for
automatic updates**" — and administrators confirm the behaviour in practice ("ACC is supposed to be
updated automatically after each console version upgrade", with the Auto Update toggle under
Groups & Settings > All Settings > System > Enterprise Integration > Cloud Connector). Everything else
in the option list requires a scheduled maintenance window.
customer-managed VM and upgrade deliberately. There is no self-update behaviour; a new console
release does not silently patch it, and an admin must run the upgrade package.
patch/update through the admin console. It is deliberately in the operator's hands because the
change can break perimeter-dependent services (Tunnel, SEG, Content Gateway).
that runs inside the UAG appliance, so it inherits whatever version the UAG is running and can
never update ahead of or independently of it.
"Which component self-updates?" is really "which component is slaved to the console version?" — the
AirWatch Cloud Connector. Everything that runs inside an appliance the customer administers (UAG,
SEGv2, Access connector) needs a human; the connector that only ever makes outbound calls to AWCM
is the one VMware lets look after itself.
Verdict: C — Autodiscovery Enrollment
The error is the Intelligent Hub trying to auto-discover a Workspace ONE server from an email
address it cannot map. Turning on Autodiscovery Enrollment is what changes the first screen from
"enter your Server URL" to "enter your email address" — the hub then resolves the domain to your
tenant through the registered auto-discovery service. An Enrollment Token does nothing for this: it
only gates who is allowed to enrol, and only when open enrolment is already restricted.
"Enter an Email Address to Sign in") that lets the Intelligent Hub accept an email address instead
of the full tenant URL, e.g. [email protected] rather than myco.workspaceoneidentity.com.
for auto discovery, or the UEM/access side cannot complete the lookup.
activated with the emailed token) before a typed email address resolves.
registered devices"; it is an authorisation control layered on top of enrolment, not a discovery
control.
Auto discovery is exactly the feature that removes the need for users to know the Server URL. The
Access administration guide describes it as letting end users "enter their email address instead of
the organization's URL", and only once the domain is registered for auto discovery does the hub turn
that address into the right tenant. Enabling Autodiscovery Enrollment in the UEM console is the
switch the question is asking for: the hub stops expecting a Server URL and starts expecting an email
address. The vendor reference for this row is the Autodiscovery Enrollment page, which is the
console feature named in option C.
directory. It does not change the discovery field on the hub's first screen; a known user typing an
email address into a Server-URL-only hub gets the same discovery error.
it can be assigned to an organisation group. It is about provisioning ownership, not about how the
user identifies the tenant.
exactly why it is tied to registered device enrolment. A user holding a valid token still has to
reach the right tenant first; with auto discovery off, the typed email address cannot be resolved
and the token is never even requested.
Split the vocabulary: discovery answers "which server/tenant is this?", token answers "is this
person allowed to enrol?". An error that appears in the very first field of the hub, before any
credentials, is always a discovery problem.
Verdict: A — AirWatch Cloud Connector
Discovery/Directory Services integration means the SaaS console has to reach something inside your
network — Active Directory, an LDAP directory, a CA. In a SaaS deployment that hop is provided by the
AirWatch Cloud Connector (ACC) you install in the internal network; it makes outbound-only calls
back to the console and returns the results. AirWatch Cloud Messaging is not something you install
at all — it is the SaaS transport the connector uses.
directory/discovery services integration in SaaS; performs directory sync and authentication against
AD/LDAP and runs outbound-only.
assigns them to organisation groups.
talk to each other. Nothing to install on premises.
connector can live behind a restrictive firewall.
The reference architecture is explicit about the SaaS topology: "To synchronize Workspace ONE with
internal resources such as Active Directory or a Certificate Authority, you use a separate cloud
connector, which can be implemented using an Omnissa AirWatch Cloud Connector", and it runs in your
internal network outbound-only. That connector is the component that performs directory sync and
authentication against the on-premises resource — i.e. the piece that makes discovery services
integration work in a SaaS environment. The vendor prose attached to this question names the same
component.
which component is "highly recommended to be installed", and nothing is installed for AWCM; the
connector is configured with it.
DEX telemetry, used to pull device health and user-experience data, not directory services.
programs; it is not an installable on-premises component and it does not perform directory sync.
For SaaS-plus-on-premises questions, ask what the customer actually installs. Directory Services
integration, PKI and syslog integration in SaaS all point at the AirWatch Cloud Connector; AWCM is
the SaaS channel it speaks over, never the thing on your network.
Verdict: D — The user is redirected to the default Workspace ONE Access login page
Single Logout (sign-out propagation) is what tells the upstream identity provider that the Workspace
ONE session has ended. Turn SLO off and nothing is propagated, so signing out of Access simply
drops the local session and lands the user back on the Access login page. SLO is the only mechanism
that produces the other redirects listed here.
happens on sign-out and whether the session is terminated at the IdP.
Access. SLO is the reverse direction.
directions.
is honoured through the IdP sign-out call, which is exactly what disabling SLO removes.
With SLO disabled for that third-party IdP, Workspace ONE Access has no channel to tell the IdP the
session ended. Sign-out therefore terminates only the Access session and re-renders the default Access
login page — the user is not returned to the IdP, not sent to the catalog (which is where they start),
and not sent to a custom URL.
nothing in the SLO-disabled path bounces an unauthenticated user back into it.
request, which is precisely what SLO enables. With SLO off, Access never calls the IdP.
Access performs the federated sign-out; disabling SLO suppresses that call and the custom URL.
Read SLO questions as "who gets told?". SLO enabled = the IdP is told and can take the user back to
its own login or a custom URL. SLO disabled = Access ends the session locally and the default Access
login page is all the user ever sees.
Verdict: B — Deliver Launcher profile to the end-user
Check In/Check Out (CICO) on Android is built on Workspace ONE Boxer, and Boxer only behaves as a
kiosk-style application when its Launcher experience is deployed to the device. Delivering the Boxer
Launcher profile is what turns the device into a managed, shared, check-out-able workstation; the
other options have nothing to do with the CICO flow.
it back in when they are done, so a shared Android device can be handed around safely.
user can see and launch.
Boxer documents Check In/Check Out as a capability of the Boxer application itself, and Boxer on Android
delivers its CICO behaviour through the Launcher profile. Once the Launcher profile is on the device,
Boxer owns the screen and the mailbox; checking out a user grants that user their assigned Boxer
content and checking in wipes and re-claims it. Without the Launcher profile, Boxer is just another
managed app and there is no kiosk shell for CICO to run inside.
remediation. It has no bearing on whether Boxer can check content in and out of a session.
enrolment; the user performing CICO is an interactive, checked-out user, not the staging identity.
who may enrol. It says nothing about the runtime Boxer experience the user gets afterwards.
For any "which is required to deliver X" question, find the component that actually implements X and
choose the deliverable that installs it. Here Boxer implements CICO, and on Android the Launcher
profile is what installs the Boxer shell.
Verdict: C — AirWatch Cloud Connector (ACC)
Workspace ONE Access does not query the Workspace ONE UEM SaaS API endpoints directly from the
internet; the customer's AirWatch Cloud Connector, sitting in the internal network, brokers the
exchange and hands device information back to Access. SAML has nothing to do with it and SOAP is not
the integration path.
directory sync and the UEM-facing integration calls on behalf of the SaaS services.
Services and the console.
"underlying technology" being asked about.
posture that Access evaluates in access policies.
Access obtains device state by asking the customer's own on-premises integration component, which is
the AirWatch Cloud Connector. The ACC authenticates to the SaaS service with its AWCM certificate,
reads the device/compliance data through the UEM interfaces, and returns it to Access so that access
policies can evaluate conditions. This keeps all on-premises contact inside the customer's firewall and
keeps the ACC outbound-only.
is a legacy interface and not the integration contract here.
component that sits between Access and the UEM data is the ACC. Choosing REST names the wire
protocol, not the technology that collects the data.
the mechanism for collecting endpoint device state.
Whenever a question asks what technology "collects" or "fetches" data from UEM in a SaaS
architecture, the answer is the AirWatch Cloud Connector. Protocol words (SOAP, REST, SAML) are
distractors unless the question asks specifically for the interface.
Verdict: B, C and F — conditional access, Per-App VPN, and Mobile SSO
Conditional access, Per-App VPN (Per-App Tunnel) and Mobile SSO are all Workspace ONE Access
services. The unified application catalog is delivered by Workspace ONE Hub Services / the Intelligent
Hub catalog that Access consumes, "network segmentation" is a network-architecture concept rather than
an Access service, and generic "encryption" is not an Access feature name.
Connector) against an access policy before granting an app, and can block or remediate.
access to internal resources without a device-wide VPN.
including certificate/ biometric-based SSO, using Access policies.
federates resources into.
These three are the security services Access itself delivers to applications: it decides whether a
request is allowed (conditional access), it brokers app-level connectivity into internal networks
(Per-App VPN / Per-App Tunnel), and it brokers the user's authenticated session into the target app
(Mobile SSO). All three are configured in the Access console and enforced through the Intelligent Hub.
Services with the Intelligent Hub app; Access consumes and federates that catalog rather than being
the catalog feature itself, which is why it is not counted as an Access-supported option here.
Workspace ONE product segments the physical network for you.
encryption), but it is not a discrete Access service you enable; naming it as a "supported option"
is a category error.
For "which of these are supported by product X" questions, only count features that appear in that
product's own console. Access console pages = conditional access, Per-App Tunnel, Mobile SSO,
application access policies. Catalog = Hub Services. Network design = your own switching.
Verdict: B — Syslog Integration
Workspace ONE UEM has a built-in Syslog Integration page that forwards console and device events to
an external SIEM/syslog collector on a schedule you control. It works in both SaaS and on-premises
deployments and can carry console events, device events, or both.
UDP/TCP, typically RFC 3164/5424.
deployments, not for event forwarding to a SIEM.
The console's Syslog Integration configuration is exactly the feature for "get event logs into my
SIEM". You point it at the collector, choose console events, device events or both, and events
generated by the UEM console are then delivered according to the scheduler settings — and it works for
SaaS tenants as well as on-premises installs, which matters because the SIEM lives inside the customer
network and the connection is outbound.
Services in very large installs; it is not an event-forwarding integration and has no SIEM settings.
share; logs to a file share would not be SIEM ingestion anyway.
Symantec MPKI) distributes device certificates; it carries no event payload to a SIEM.
"Assist in sending event log information to a SIEM" always means syslog. If the option list offers
syslog, relay, file storage or CA integration, syslog is the only one whose purpose is event
forwarding — relay moves device traffic, CA moves certificates.
Verdict: C and E — Obtain an Apple ID, and Obtain an APNS certificate
To manage iOS devices you need an Apple ID (to enrol and to own the account relationship with
Apple) and an APNs certificate (so the console can talk to Apple's push notification service and
send commands and app pushes to devices). An iCloud account and an Apple Server Certificate are not part
of the iOS management set-up.
the identity end users authenticate with.
without it no command, query result, app install or compliance update can reach the device.
Apple's own push infrastructure, not something an administrator generates for UEM.
Enrolling an iOS device into Workspace ONE UEM means registering it with an Apple ID so that the device
management profile can be downloaded and trusted, and it means giving the console a valid APNs
certificate so that push notifications — the channel every console-to-device action travels over — are
accepted by Apple. With either missing you cannot manage iOS at scale: no APNs certificate means silent,
stuck devices.
policy delivery or command execution.
applications; iOS device management needs no Developer ID from the administrator.
it is not issued or uploaded by a UEM administrator, whereas the APNs certificate is.
For iOS set-up questions, the two answers are always the identity you enrol with (Apple ID) and the
push channel the console needs (APNs certificate). Everything Apple-branded that is neither — iCloud,
Developer ID, Apple Server Certificate — is a distractor.
Want the full bank of 55 questions for VMware Workspace ONE Professional (2V0-61.20)? See all practice exams.