Sign in
Home/VMware/VMware Workspace ONE Professional (2V0-61.20)/Free questions

VMware Workspace ONE Professional (2V0-61.20) — Free Practice Questions

10 free sample questions from a bank of 55, with the correct answers and explanations. No signup required — start practising right now.

1Which two authentication methods are available in the Workspace ONE UEM console? (Choose two.)
  • SAML
  • Azure AD
  • CAPTCHAs
  • OAUTH
  • Certificate Based Authentication
Answer: D, E

Verdict: D and E — OAUTH, and Certificate Based Authentication

The short version

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.

Key concepts

  • OAuth 2.0 — delegated/federated authorisation used to sign administrators into the UEM console

through an external identity provider.

  • Certificate Based Authentication — passwordless console authentication using a client

certificate issued to the admin device or smart card.

  • AirWatch Cloud ID — the console's own local username/password store, the third option alongside

the two above.

  • SAML — the assertion protocol Workspace ONE Access uses to federate to a third-party IdP; it

is an Access identity-provider configuration item, not a UEM console authentication method.

  • CAPTCHA — a bot/spam challenge on public forms.

Why D and E are correct

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.

Why the others are wrong

  • A. SAML — SAML belongs to Workspace ONE Access identity-provider configuration and to per-app

SSO in the catalog. The UEM console administrator sign-in is not configured with SAML metadata.

  • B. Azure AD — Azure AD is a directory/identity provider, not a method. You consume it over

OAuth (or SAML in Access); there is no "Azure AD" authentication method tile in the console.

  • C. CAPTCHAs — a CAPTCHA challenges a human proving they are not a robot; it authenticates nobody

and appears nowhere in the console's authentication configuration.

2V0-6120 exam tip

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.

2Which auxiliary component, with a default configuration, has the ability to self-update after an upgrade?
  • Workspace ONE Access Connector
  • Unified Access Gateway
  • Secure Email Gateway on UAG
  • AirWatch Cloud Connector
Answer: D

Verdict: D — AirWatch Cloud Connector

The short version

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.

Key concepts

  • AirWatch Cloud Connector (ACC) — on-premises Windows service in your internal network that

brokers SaaS-to-on-premises traffic (directory sync, PKI, syslog, PowerShell, email relay) in

outbound-only mode. Documented as being configurable for automatic updates.

  • AirWatch Cloud Messaging (AWCM) — the SaaS channel the ACC uses to reach the console; it is

what makes unattended ACC self-update possible.

  • Unified Access Gateway (UAG) — VMware appliance for Tunnel, SEGv2 and Content Gateway. Patched

by an admin with APPLY PATCH / the upgrade bundle, never self-updating.

  • Secure Email Gateway (SEG / SEGv2) — a UAG-hosted service, so its version moves only when the

UAG appliance itself is upgraded.

  • Workspace ONE Access connector — on-prem Access service host; upgraded by running a new

installer/appliance package by hand.

Why D are correct

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.

Why the others are wrong

  • A. Workspace ONE Access Connector — the Access connector is a service you install on a

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.

  • B. Unified Access Gateway — UAG is an appliance image that must be upgraded by uploading a

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).

  • C. Secure Email Gateway on UAG — SEGv2 is not a separate installable box at all; it is a service

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.

2V0-6120 exam tip

"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.

3During an enrollment attempt, a user enters their email address in the initial field in the Intelligent Hub. The user receives an error stating, "Something went wrong with discovery". Which configuration setting can be enabled to allow end users to enter an email address instead of a Server URL?
  • Allow only known users
  • Pre-Register devices
  • Autodiscovery Enrollment
  • Enrollment Token
Answer: C

Verdict: C — Autodiscovery Enrollment

The short version

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.

Key concepts

  • Autodiscovery Enrollment — Workspace ONE UEM setting (and the Access Login Preference

"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.

  • "Something went wrong with discovery" — the hub's error when the typed domain is not registered

for auto discovery, or the UEM/access side cannot complete the lookup.

  • Auto-discovery domain registration — the tenant's email domain must be registered (and

activated with the emailed token) before a typed email address resolves.

  • Enrollment Token — a per-user code sent by email/SMS used with "restrict enrollment to

registered devices"; it is an authorisation control layered on top of enrolment, not a discovery

control.

  • Intelligent Hub — the end-user agent whose first-run screen this error comes from.

Why C are correct

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.

Why the others are wrong

  • A. Allow only known users — this restricts enrolment to users who already exist in the console

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.

  • B. Pre-Register devices — pre-registration creates the device record before the device enrols so

it can be assigned to an organisation group. It is about provisioning ownership, not about how the

user identifies the tenant.

  • D. Enrollment Token — the token proves a particular user is authorised to enrol, which is

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.

2V0-6120 exam tip

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.

4Which is highly recommended to be installed for discovery services integration in a Software as a Service environment (SaaS)?
  • AitWatch Cloud Connector
  • AirWatch Cloud Messaging
  • Workspace ONE Adaptive Connector
  • AirWatch API components
Answer: A

Verdict: A — AirWatch Cloud Connector

The short version

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.

Key concepts

  • AirWatch Cloud Connector (ACC) — on-premises component VMware recommends (and requires) for

directory/discovery services integration in SaaS; performs directory sync and authentication against

AD/LDAP and runs outbound-only.

  • Directory Services integration — console feature that syncs users and groups from AD/LDAP and

assigns them to organisation groups.

  • AirWatch Cloud Messaging (AWCM) — SaaS-hosted message service; the ACC and the console use it to

talk to each other. Nothing to install on premises.

  • AWCM certificate — the client certificate the ACC presents to the SaaS service, which is why the

connector can live behind a restrictive firewall.

  • Outbound-only mode — the ACC never accepts inbound connections; it initiates and polls.

Why A are correct

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.

Why the others are wrong

  • B. AirWatch Cloud Messaging — AWCM is a hosted service, not a box you install. The question asks

which component is "highly recommended to be installed", and nothing is installed for AWCM; the

connector is configured with it.

  • C. Workspace ONE Adaptive Connector — a component of Workspace ONE Experience Management /

DEX telemetry, used to pull device health and user-experience data, not directory services.

  • D. AirWatch API components — the REST API endpoint is a SaaS capability consumed by external

programs; it is not an installable on-premises component and it does not perform directory sync.

2V0-6120 exam tip

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.

5When Single Logout (SLO) is disabled in a third party identity provider configuration of Workspace ONE Access, what is the default action taken upon a user signing out of Workspace ONE Access?
  • The user is redirected back to the Workspace ONE Access catalog.
  • The user is redirected to the third party identity provider URL provided in metadata.
  • The user is redirected to a custom URL provided in the identity provider configuration.
  • The user is redirected to the default Workspace ONE Access login page.
Answer: D

Verdict: D — The user is redirected to the default Workspace ONE Access login page

The short version

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.

Key concepts

  • Single Logout (SLO) — a per-identity-provider setting in Workspace ONE Access that defines what

happens on sign-out and whether the session is terminated at the IdP.

  • Single Sign-On (SSO) — the inbound direction: an assertion from the IdP logs the user into

Access. SLO is the reverse direction.

  • Third-party identity provider metadata — the IdP's endpoints and certificate used for both

directions.

  • Custom URL — an optional post-logout landing page configured on the identity provider entry; it

is honoured through the IdP sign-out call, which is exactly what disabling SLO removes.

Why D are correct

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.

Why the others are wrong

  • A. The Workspace ONE Access catalog — the catalog is the entry point after a successful login;

nothing in the SLO-disabled path bounces an unauthenticated user back into it.

  • B. The third party IdP URL from metadata — returning to the IdP requires an actual sign-out

request, which is precisely what SLO enables. With SLO off, Access never calls the IdP.

  • C. A custom URL from the IdP configuration — a custom post-logout URL only takes effect when

Access performs the federated sign-out; disabling SLO suppresses that call and the custom URL.

2V0-6120 exam tip

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.

6Which is required to deliver a Check In, Check Out experience on an Android Device?
  • Enable VMware Workspace ONE Intelligence.
  • Deliver Launcher profile to the end-user.
  • Use a basic user as a staging account.
  • Block open enrollment into Workspace ONE UEM.
Answer: B

Verdict: B — Deliver Launcher profile to the end-user

The short version

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.

Key concepts

  • CICO (Check In / Check Out) — Boxer checks email, content and app access out to a user and checks

it back in when they are done, so a shared Android device can be handed around safely.

  • Boxer Launcher — the managed home-screen/launcher experience for Android that scopes what the

user can see and launch.

  • Workspace ONE Intelligence — the risk/analytics service (not required for CICO).
  • Staging account — the service account used for silent enrolment, not a CICO control.
  • Open enrollment — enrolment policy, unrelated to the runtime CICO experience.

Why B are correct

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.

Why the others are wrong

  • A. Enable VMware Workspace ONE Intelligence — Intelligence scores device/user risk and drives

remediation. It has no bearing on whether Boxer can check content in and out of a session.

  • C. Use a basic user as a staging account — the staging account exists for silent, unattended

enrolment; the user performing CICO is an interactive, checked-out user, not the staging identity.

  • D. Block open enrollment into Workspace ONE UEM — an enrolment-restriction setting that reduces

who may enrol. It says nothing about the runtime Boxer experience the user gets afterwards.

2V0-6120 exam tip

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.

7Which underlying technology does Workspace ONE Access use to collect Workspace ONE UEM device information?
  • SOAP API
  • REST API
  • AirWatch Cloud Connector (ACC)
  • Security Assertion Markup Language (SAML)
Answer: C

Verdict: C — AirWatch Cloud Connector (ACC)

The short version

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.

Key concepts

  • AirWatch Cloud Connector (ACC) — on-premises proxy in the internal network that performs

directory sync and the UEM-facing integration calls on behalf of the SaaS services.

  • AirWatch Cloud Messaging (AWCM) — the outbound-only SaaS channel the ACC uses to reach Device

Services and the console.

  • REST API — the interface the connector itself uses internally; it is the transport, not the

"underlying technology" being asked about.

  • Device information for conditional access — compliance state, OS version, network and app

posture that Access evaluates in access policies.

  • SAML — assertion-based SSO for users/apps, unrelated to device data collection.

Why C are correct

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.

Why the others are wrong

  • A. SOAP API — Workspace ONE UEM does not expose device information to Access through SOAP; SOAP

is a legacy interface and not the integration contract here.

  • B. REST API — the REST API is how the connector and third-party programs talk to UEM, but the

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.

  • D. SAML — SAML carries identity assertions from an identity provider about a user; it is never

the mechanism for collecting endpoint device state.

2V0-6120 exam tip

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.

8Which three options are supported by Workspace ONE Access? (Choose three.)
  • unified application catalog
  • conditional access
  • Per-App VPN
  • network segmentation
  • encryption
  • Mobile SSO
Answer: B, C, F

Verdict: B, C and F — conditional access, Per-App VPN, and Mobile SSO

The short version

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.

Key concepts

  • Conditional Access — Access evaluates device/user/posture state (via the AirWatch Cloud

Connector) against an access policy before granting an app, and can block or remediate.

  • Per-App VPN / Per-App Tunnel — Access-injected per-application tunnel profiles, giving app-level

access to internal resources without a device-wide VPN.

  • Mobile SSO — brokered authentication from the Intelligent Hub into native and SaaS apps,

including certificate/ biometric-based SSO, using Access policies.

  • Unified application catalog — the Hub Services / Intelligent Hub catalog experience that Access

federates resources into.

  • Network segmentation — VLANs, firewalls and routing design, not a Workspace ONE Access service.

Why B, C and F are correct

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.

Why the others are wrong

  • A. Unified application catalog — the catalog experience is delivered by Workspace ONE 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.

  • D. Network segmentation — segmentation is done with switches, VLANs, firewalls and routing. No

Workspace ONE product segments the physical network for you.

  • E. Encryption — encryption is present everywhere in the platform (TLS, BitLocker, FIPS, content

encryption), but it is not a discrete Access service you enable; naming it as a "supported option"

is a category error.

2V0-6120 exam tip

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.

9Which Workspace ONE UEM feature can assist in sending event log information to a Security Information and Event Management (SIEM) tool?
  • Relay Server Integration
  • Syslog Integration
  • File Storage Integration
  • Certificate Authority Integration
Answer: B

Verdict: B — Syslog Integration

The short version

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.

Key concepts

  • Syslog Integration — Groups & Settings page that ships event data to a syslog collector over

UDP/TCP, typically RFC 3164/5424.

  • SIEM — Security Information and Event Management tool that receives and correlates the events.
  • Console events vs device events — the two event sources you can tick in the syslog configuration.
  • Scheduler settings — the cadence at which events are pushed to the collector.
  • Relay Server — an on-premises UEM component used for device-to-console traffic in large

deployments, not for event forwarding to a SIEM.

Why B are correct

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.

Why the others are wrong

  • A. Relay Server Integration — the relay server relays device traffic between devices and Device

Services in very large installs; it is not an event-forwarding integration and has no SIEM settings.

  • C. File Storage Integration — there is no such UEM integration for shipping events to a file

share; logs to a file share would not be SIEM ingestion anyway.

  • D. Certificate Authority Integration — certificate enrollment integration (SCEP, Microsoft PKI,

Symantec MPKI) distributes device certificates; it carries no event payload to a SIEM.

2V0-6120 exam tip

"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.

10Which two configuration steps must be performed when managing iOS devices? (Choose two.)
  • Obtain an iCloud Account.
  • Obtain an Apple Developer ID.
  • Obtain an Apple ID.
  • Obtain an Apple Server Certificate.
  • Obtain an APNS certificate.
Answer: C, E

Verdict: C and E — Obtain an Apple ID, and Obtain an APNS certificate

The short version

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.

Key concepts

  • Apple ID — the identity an administrator uses to enrol devices and to access Apple resources; also

the identity end users authenticate with.

  • APNs certificate — the Apple Push Notification service certificate uploaded to the UEM console;

without it no command, query result, app install or compliance update can reach the device.

  • Apple Push Notification service — Apple's outbound notification channel to iOS devices.
  • iCloud account — an Apple consumer cloud-storage account, unrelated to UEM enrolment.
  • Apple Server Certificate — belongs to Apple Push Notification provider authentication for

Apple's own push infrastructure, not something an administrator generates for UEM.

  • Apple Developer ID — code-signing identity for macOS apps, not required for iOS management.

Why C and E are correct

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.

Why the others are wrong

  • A. Obtain an iCloud Account — iCloud is consumer file sync. It plays no part in UEM enrolment,

policy delivery or command execution.

  • B. Obtain an Apple Developer ID — the Developer ID is Apple's code-signing identity for macOS

applications; iOS device management needs no Developer ID from the administrator.

  • D. Obtain an Apple Server Certificate — that certificate authenticates Apple's own push providers;

it is not issued or uploaded by a UEM administrator, whereas the APNs certificate is.

2V0-6120 exam tip

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.