Skip to main content

IAM analyst interview questions: access-change practice

Practice a first IAM interview with a failed access-removal ticket, a worked solution and clear explanations of the decisions behind it.

Updated by

JW
Jack WalshNov 16, 2026 · 16 min read

Hi, I'm Jack, the owner of Cybersecurity Jobs List and co-founder of Himalayas (himalayas.app) and Cavuno (cavuno.com). Across all my platforms, I work with application security daily: dependency vulnerability scanning, secure authentication, API security, and data protection across hundreds of thousands of users. My technical background is in computer science (UNSW). I studied security engineering and computer networks, and worked as a research assistant on VR experiments that were published in the Journal of Experimental Psychology. I also work with cybersecurity hiring data every day, tracking which companies are posting, what certifications actually appear in listings, how salaries differ by sub-discipline and clearance level, and where the talent gaps are widest. That combination of security practice, engineering at scale, and daily immersion in hiring data shapes the content on this site. I'm currently based in Sydney, Australia.

Share this post

Illustration of two people reviewing an employee access card beside a laptop.
Conceptual illustration created for this guide.

A removal was attempted, but the old permission is still present. What would you say in an IAM analyst interview: the change is complete, the employee can keep the access, or the removal needs further work?

That decision is the starting point for this exercise. Identity and access management (IAM) concerns who can access which resources, such as work applications and reports. If you’re coming from helpdesk or have only lab experience, practice explaining what access should change, who decides, and what evidence would show that the change worked.

These IAM analyst interview questions focus on access-change reasoning for a first IAM role. They aren’t a complete technical interview syllabus or a prediction of any named employer’s questions. Start with the ticket, try your own answer, then use the explanations to understand the decisions behind it.

Work through an access-change ticket

Separate the approved work from the incomplete requests, then decide what evidence would let you close each item.

Fictional practice example

The people, applications, permissions, policies, and illustrative workplace situations in this exercise are invented for practice.

Alex is moving from Finance to Sales. The ticket contains four access items:

  • Enable the approved Sales Workspace Contributor permission.
  • Give Alex the same permissions as a senior Sales colleague, without listing those permissions.
  • Keep Finance access temporarily to finish a handover, without specifying an end date.
  • Remove the old Finance Ledger Editor permission.

A permission is an allowed action in a system, such as viewing or editing a report. The last item has already reached the change stage: an automated workflow attempted to remove Finance Ledger Editor, but a subsequent check in the target application still shows it assigned to Alex.

Supplied facts

For this exercise, the policy says:

  • The relevant application owner approves specific permissions. A manager may request access but cannot substitute for that approval.
  • Temporary Finance access requires the Finance application owner’s approval of the exact permission, handover purpose, and end date.
  • Old Finance access must be removed at the move unless a temporary exception has been approved.
  • Failed automated removals are assigned to application support for investigation. This analyst must not rerun the workflow without that owner’s direction.
  • The Finance application owner must be notified when old Finance access persists.
  • The ticket cannot be marked complete while required removal remains unverified.

The move takes effect today. The Sales application owner has approved Sales Workspace Contributor. The Finance application owner has approved removal of Finance Ledger Editor.

There is no approval for copying the senior colleague’s permissions and no approved Finance handover exception. The application check establishes that the attempted removal didn’t achieve the required result.

Your turn

Write a short answer before reading the solution. Address these four decisions:

  1. Clarify: What would you ask about the copied permissions and Finance handover?
  2. Implement: Which change is specific enough and already approved to carry out?
  3. Verify: What would you check after making that change?
  4. Keep open: Which items remain unresolved, and who needs to act?

Work with the evidence supplied. You don’t need to invent a successful removal or fill in a missing approval to reach a useful answer.

Compare your answer with the evidence

Add and verify the approved Sales permission, hold the unspecified additions, and send the failed Finance removal to application support while keeping it unresolved.

Before acting, confirm Alex’s target account, the specific approval, and your authority to make the change. The account check establishes whose access you’re changing; approval establishes the permitted change; your authority establishes whether you may carry it out.

A brief spoken answer could sound like this:

I would add the approved Sales Workspace Contributor permission and check that it was present in the application. For the colleague’s other permissions, I would ask what tasks Alex needs to perform and get the specific access approved.

For the Finance handover, I would ask what access is needed, why, and until when, so the Finance owner can decide. There’s no approved exception, so the request doesn’t pause the required removal. I would assign the failed removal to application support, notify the Finance owner, and keep it open. Under this policy, I wouldn’t rerun the workflow without application support’s direction.

Here’s how to mark your answer against each part of the task.

Clarify

Ask for the work Alex needs to do and the specific permissions that work requires.

For the coworker-copy request, a colleague’s name isn’t an itemized request. You need the application, the intended tasks, and the allowed actions being requested. These details establish the request’s scope: exactly what access the proposed change covers.

For the Finance handover, ask what work remains, which permission it needs, and when that work will finish. Clarify whether the request concerns Finance Ledger Editor. The Finance owner then has a concrete exception to consider instead of an open-ended request to “keep Finance access.”

Neither incomplete request needs to prevent the separately approved Sales change from proceeding.

Implement

Carry out the approved Sales Workspace Contributor change after the account, approval, and authority checks.

Keep the senior colleague’s unspecified permissions on hold. The existing Sales approval covers the named permission, not every permission Alex might later request.

Don’t treat the handover request as permission to retain Finance Ledger Editor. Removal is approved, and there’s no approved exception. However, the earlier automated attempt failed, and this policy assigns investigation to application support. Your next action for that item is the required handoff, not an independent rerun.

That restriction belongs to this exercise’s policy. It doesn’t mean retrying a failed workflow is inherently wrong in every system.

Verify

Check the resulting permission in the target application and record what you observed and when.

For Sales Workspace Contributor, recording that you submitted the change isn’t enough to establish that Alex has the permission. Check its resulting state. Only test whether Alex can complete the intended task if you’re authorized to conduct that test.

For Finance Ledger Editor, the current evidence is already clear: the application still shows the permission after the automated removal attempt. Record that observation and its time alongside the attempted action. If the ticket lacks the check’s timestamp, obtain or record a fresh observation rather than inventing one.

This is verification: checking whether the action achieved its intended result. “Removal attempted” and “permission removed” describe different things.

Keep open

Keep the incomplete requests and failed removal open with a named next owner and follow-up.

The extra Sales permissions need a defined request and the relevant application owner’s decision. The handover needs its missing details and the Finance owner’s decision.

Assign the failed removal to application support with the attempted action and the observed application state. Notify the Finance owner that the old access persists, as this policy requires. Record who owns the investigation and when you’ll next follow up; the exercise doesn’t supply a deadline, so don’t invent a required response time.

You don’t need to diagnose the failure to make a useful handoff. You do need to preserve the distinction between the approved removal and its unsuccessful result.

Track each item separately

Keep requested, approved, implemented, and verified states separate so the ticket doesn’t imply more progress than the evidence supports.

This table shows the state when you receive the ticket. Your proposed Sales change hasn’t happened yet.

Access itemEvidence and next step
Sales Workspace ContributorApproved: Sales owner approved
Implemented: Not yet implemented
Verified: No result checked yet
Next step: Analyst to implement, then record the observed result and time
Senior colleague’s other permissionsApproved: No approval or itemized scope
Implemented: No additional grants
Verified: No implementation to verify
Next step: Requester to clarify tasks and permissions; relevant owner to decide
Temporary Finance handoverApproved: No approved exception
Implemented: No authorized retention decision
Verified: No approved duration to check against
Next step: Requester to supply purpose, permission, and end date; Finance owner to decide
Finance Ledger Editor removalApproved: Finance owner approved removal
Implemented: Automated removal attempted
Verified: Target app still shows permission; record check time
Next step: Application support to investigate; notify Finance owner and record next follow-up

A request records what someone wants. Approval records the authorized decision. Implementation records the action taken. Verification records the observed result.

Update the ledger as evidence arrives. If Sales access is granted and checked, record those events. Until Finance removal is confirmed, its status remains unresolved. Calling it removed would contradict the application check; calling it approved handover access would invent an exception.

IAM analyst interview questions to practice

Use these questions to explain the concepts behind the ticket, then connect each answer to a specific decision.

What’s the difference between authentication and authorization?

Authentication establishes who someone is. Authorization determines what they’re allowed to access.

Imagine an employee signing into a work system. The system checks that they are who they claim to be. That’s authentication. The employee then tries to open a payroll report. Whether they’re allowed to read it is a separate decision: authorization. Being recognized as an employee doesn’t mean they can read everyone’s pay.

Microsoft explains this distinction in its authentication and authorization guidance.

A natural interview answer could be:

Authentication is about establishing who you are. Authorization is about what you’re allowed to do. An employee might successfully sign into a work system but still have no permission to open a payroll report. If someone reported an access problem, I would first clarify whether they couldn’t sign in or could sign in but couldn’t open what they needed.

The distinction helps you choose what to investigate. A successful sign-in doesn’t prove that access should be granted, and an access-denied message doesn’t necessarily mean the password needs resetting.

Would you copy a coworker’s permissions, and what happens to old access?

Clarify the required work before adding permissions, and address old access separately when someone changes roles.

The ticket demonstrated both decisions. Alex’s senior colleague might be able to edit a report when Alex only needs to read it. Copying everything would grant more than the stated task requires. Least privilege means limiting access to what someone needs for their assigned tasks.

Also check for separation of duties: limits on combinations of privileges that could enable misuse. For example, a company might separate permission to prepare a payment from permission to approve it alone. The conflicting combinations depend on its policy.

For old access, Alex’s handover request needs a specific purpose and end date before the owner can decide. The failed removal then needs verification, even though the decision to remove access is already approved. In your answer, connect these concepts to the ticket rather than repeating definitions without explaining what you’d do.

What do joiner, mover, and leaver mean?

A joiner enters an organization, a mover changes roles within it, and a leaver departs. Microsoft uses these phases in its lifecycle workflows documentation.

Each change raises a different access question.

Joiner: a new employee needs starting access

A joiner needs access for their starting tasks at the approved time.

For a new Sales employee, your starting point is the authorized starting information and approved access. There’s no previous Finance role to reconcile in this example.

For a joiner, I would use the authorized starting information to establish the access needed for their initial tasks. I would make the approved changes at the intended start time, then check that the resulting permissions matched the request.

Mover: an existing employee changes roles

A mover needs their existing access reconsidered alongside access for the new role.

Alex’s Finance-to-Sales move illustrates why adding new access is only part of the work. Old permissions need a removal decision or a defined exception.

For a mover, I would compare the new role’s access needs with the permissions the employee already has. In Alex’s ticket, I would add the approved Sales access, clarify the handover exception, and track the failed Finance removal until its result was verified.

Treating a mover as a new starter with an existing account leaves their previous permissions unaddressed.

Leaver: an employee leaves the organization

A leaver needs access ended at the approved effective time, with the relevant accounts and sessions checked.

Consider a Sales employee whose departure instruction specifies ending access to work applications. A concrete answer should describe the removal work, not just say “follow the procedure.”

At the approved effective time, I would disable the relevant sign-in, revoke sessions using the applicable system controls, and check application-level accounts and required removals. I would record what was confirmed and escalate remaining access. I wouldn’t claim every session had ended just because sign-in was blocked.

The exact controls depend on the systems involved. Microsoft’s access revocation guidance explains the Entra context and its limits.

Does blocking sign-in end every application session?

No. Don’t promise that blocking sign-in immediately ends every existing application session.

An employee might already have an application open when their sign-in is blocked. The application may maintain its own session, the ongoing signed-in state that lets the person keep using it. That can be separate from the session maintained by the identity provider, the service used to establish their identity when signing in.

Microsoft Entra cannot directly revoke an application-issued session token, the application’s own record of that signed-in state. That’s why the leaver answer includes application-level checks.

I would check the affected applications’ account and session behavior after using the applicable revocation controls. If an application still allowed access, or I couldn’t verify its state, I would report that as unresolved.

Explain this as an Entra example and check the actual application behavior. Don’t turn a completed sign-in block into an unsupported claim that all access has ended.

What is an access review, and who decides whether access stays?

An access review checks whether someone still needs existing access, with the designated reviewer deciding whether it stays.

Microsoft describes access reviews as a way to assess continued access need. For example, an application owner might review whether Alex still needs a permission after changing roles.

You could say:

I would gather the person’s access information and send it to the designated reviewer. I would record their decisions, then track required changes and check the results. If a decision was missing, I would keep that item open and follow up.

Sending someone a list is a step in the review, not evidence that it’s complete. Ask how often the employer runs reviews rather than assuming a schedule.

How would you handle an urgent MFA recovery request?

Establish which approved identity check the person can complete before changing their multifactor authentication (MFA) methods or starting account recovery.

MFA asks for different kinds of proof that you are the person signing in, such as a password you know and a registered device you possess. Microsoft’s explanation of MFA describes how those factors work together.

Someone might say they’ve lost their usual sign-in method and need immediate help. The risk to consider is social engineering: someone persuading support to act as if they were the employee. Urgency and a convincing story don’t establish identity.

First, determine whether the person can still use a registered sign-in method accepted by the employer’s approved flow. If they can, the applicable process may allow them to bind a replacement authenticator, meaning connect a new authentication method to their account. If they can’t meet the required checks, use the formal recovery route.

Depending on employer policy, recovery options may include prearranged recovery codes or repeated identity proofing, where the person completes the required identity-establishment process again. NIST’s guidance distinguishes authenticator binding from account recovery and describes recovery methods and notifications. The permitted method depends on the applicable assurance requirements and policy.

A distinct sample answer is:

I would check whether the employee could use another registered method through the approved flow. If not, I would route them through formal recovery using an allowed method, such as a prearranged recovery code or repeated identity proofing. I wouldn’t reset their method based only on details they gave me over the phone.

Don’t request a password or sign-in code over a call. Don’t rely on caller-supplied personal details or a newly supplied phone number alone. Help the person reach the approved check, then complete the required notifications and escalation.

Explain experience you actually have

Use a real example for past work and “I would” for a proposed response. A clear boundary lets you discuss transferable skills without claiming ownership you didn’t have.

If asked about a tool you haven’t administered, you could say: “I haven't administered [tool]. My actual experience is [true example]. I would need the approved procedure and guidance for the product-specific steps.”

If your experience is in helpdesk

Choose an access-related ticket you actually handled, then describe your contribution accurately.

If your work involved receiving the request and passing it to another team, explain what you clarified, what you recorded, and where you handed it over. If you also performed an authorized change, identify that change and explain how you personally checked the result. Use the version that matches your experience.

“I routed the ticket to the IAM team” and “I administered access” are different claims. You can explain the connection without hiding where your experience ends.

You can then bridge into the practice scenario:

I would apply the same care to documenting the request and its approval. For this ticket, I would separate the approved Sales permission from the unresolved requests and track the failed removal through escalation.

Supply your own real example before that hypothetical response. A prepared answer should help you remember the facts, not replace them.

If your experience is only in a lab

Label the setting as a lab and describe only what you actually configured or observed.

If you practiced assigning and removing access, explain which permissions you changed and how you checked the result. If you only studied a walkthrough, say that. Reading a procedure, performing a lab task, and administering workplace access are different experiences.

For this ticket, you can still explain your judgment:

I would check that the approved Sales change worked and leave the failed Finance removal open. The application still shows the permission, so I would hand that evidence to application support and follow up on the investigation.

Give the interviewer a clear account of what you know and what you would need guidance to perform. You don’t need to add invented users, outcomes, or responsibilities to make the example useful.

Rehearse before the interview

Practice explaining the decision, the authority behind it, and the evidence needed to call it complete.

  • Explain scope and risk: What access is needed, and what could go wrong if too much is granted or old access remains?
  • Identify who decides: Who can approve this permission or exception?
  • Verify the result: What observation would establish that the authorized change worked?
  • Acknowledge unknowns: What remains open, who owns it, and when will you follow up?

Match your preparation to the actual employer’s job description. Then close the solution and answer Alex’s ticket aloud using Clarify, Implement, Verify, Keep open. Compare your answer with the ledger, paying particular attention to any place you described an attempted action as a confirmed result.

Related posts

We use cookies

We use cookies to understand how this board is used and to improve it. Analytics run only if you accept. Cookie Policy