5V0-62.22 · Question #28
A newly-hired administrator has opened a ticket with the Internal IT Helpdesk, stating that they can login but do not have access to the Scheduler settings located at Groups & Settings > All…
The correct answers are most likely B and E, based on the context of VMware Workspace ONE UEM (the navigation path Groups & Settings > All Settings > Admin > Scheduler is a Workspace ONE UEM path). Why B is correct: In Workspace ONE, an administrator can have the correct roles…
Question
A newly-hired administrator has opened a ticket with the Internal IT Helpdesk, stating that they can login but do not have access to the Scheduler settings located at Groups & Settings > All Settings > Admin > Scheduler A colleague performing the same role can see and access this entitlement. What are two reasons that the newly-hired admin is having this difficulty? (Choose two.)
Options
- AThe newly-hired administrator needs to accept the EULA before sensitive configuration settings
- BThe newly-hired administrator has the correct roles assigned but has not selected the applicable
- DThe newly-hired administrator needs to navigate to Accounts > Administrators > Roles and assign
- EThe newly-hired administrator has the incorrect roles assigned or was not yet provided the correct
Explanation
The correct answers are most likely B and E, based on the context of VMware Workspace ONE UEM (the navigation path Groups & Settings > All Settings > Admin > Scheduler is a Workspace ONE UEM path).
Why B is correct: In Workspace ONE, an administrator can have the correct roles assigned but still lack access if they haven't selected (or been scoped to) the applicable Organization Group. Role permissions are scoped per org group, so even a valid role may not grant access if the admin isn't operating within the right group context.
Why E is correct: The most straightforward reason for missing entitlements is that the role assigned to the new admin simply doesn't include the Scheduler permission - either the wrong role was assigned, or the role wasn't assigned at all yet, which is a common onboarding oversight.
Why A is wrong: EULA acceptance is a one-time onboarding step that gates initial login, not specific feature entitlements - the question already states the admin can log in, ruling this out.
Why D is wrong: D describes the resolution path (where to go to fix the roles), not a reason for the problem - the question asks for causes, not remediation steps.
Memory tip: Think of Workspace ONE access issues as a two-layer check - first ask "does the role exist and include this permission?" (E), then ask "is the admin scoped to the right org group?" (B). Both layers must align for access to work.
Topics
Community Discussion
No community discussion yet for this question.