The city needs to confirm that Access admin and directory-admin roles exist so a delegated IAM technician can sign in. What should the operator identify?
Select an answer to reveal the explanation.
Short Explanation
Roles already hang on the Access wall. Point at admin versus directory admin; do not architect a new castle.
Full Explanation
To confirm Access admin and directory-admin roles exist so a delegated IAM technician can sign in, the operator should identify admin and directory-admin roles in the Workspace ONE Access console without designing a new RBAC model from scratch. Navigate-and-identify stops at recognizing the roles needed for delegation. Designing a custom NSX RBAC matrix is unrelated networking RBAC. Horizon Help Desk roles are not Access directory admin roles. UEM compliance policies do not double as Access admin roles. Exam caveat: role names can vary slightly by tenant configuration—identify the administrative and directory administration roles present rather than inventing parallel systems. Operational check: open Access Roles, confirm admin and directory-admin (or equivalent) roles exist, assign the delegated technician appropriately, have them sign in, and verify they can view directory status without full super-admin rights if least privilege is required. In municipal EUC operations, record the console path and the rejected alternatives in the change ticket so the next on-call technician repeats the same evidence-first workflow for city staff. Re-validate after the next maintenance window that the same control still holds for the civic tenant.