The answer is to use Privileged Identity Management (PIM) to require approval for role activation and to implement access reviews. PIM reduces privileged role abuse by enforcing just-in-time activation with an approval workflow, ensuring users only gain elevated permissions when explicitly needed and authorized. Access reviews complement this by periodically verifying that existing role assignments remain necessary, automatically removing stale or excessive privileges. On the Azure Security Engineer Associate AZ-500 exam, this tests your understanding of identity governance controls within Microsoft Entra ID, specifically how to shift from permanent, standing admin access to a time-bound, auditable model. A common trap is confusing broad MFA requirements with targeted privileged role protection—MFA for all users does not prevent abuse of an already-assigned role. Remember the memory tip: “Approve and Review” to keep privileged access secure and lean.
AZ-500 Secure identity and access Practice Question
This AZ-500 practice question tests your understanding of secure identity and access. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your organization uses Microsoft Entra ID. You need to recommend solutions to reduce the risk of privileged role abuse. Which TWO actions should you recommend? (Choose two.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure access reviews for privileged roles to run quarterly.
Option B is correct because PIM provides just-in-time access and approval workflows. Option D is correct because access reviews can periodically verify that role assignments are still needed. Option A is wrong because permanent role assignment increases risk. Option C is wrong because requiring MFA for all users does not target privileged roles. Option E is wrong because disabling sign-in logs reduces visibility.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Assign privileged roles permanently to reduce friction.
Why it's wrong here
Permanent assignments increase risk.
✓
Configure access reviews for privileged roles to run quarterly.
Why this is correct
Access reviews ensure role assignments are still necessary.
Related concept
Authentication checks who the user is.
✗
Disable sign-in logs for privileged users to reduce noise.
Why it's wrong here
Sign-in logs are critical for monitoring.
✓
Use Privileged Identity Management (PIM) to require approval for role activation.
Why this is correct
PIM provides just-in-time access with approval.
Related concept
Authentication checks who the user is.
✗
Require all users to use MFA for all applications.
Why it's wrong here
Does not specifically address privileged roles.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-500 question in full detail.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related AZ-500 questions on access control and AAA configuration.
Secure identity and access — This question tests Secure identity and access — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Configure access reviews for privileged roles to run quarterly. — Option B is correct because PIM provides just-in-time access and approval workflows. Option D is correct because access reviews can periodically verify that role assignments are still needed. Option A is wrong because permanent role assignment increases risk. Option C is wrong because requiring MFA for all users does not target privileged roles. Option E is wrong because disabling sign-in logs reduces visibility.
What should I do if I get this AZ-500 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related AZ-500 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-500 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-500 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.