mediummulti selectObjective-mapped

A contractor pool changes every month. The operations team wants Azure role access to stay the same when people join or leave, without editing role assignments for each person. Which two actions should the administrator take? Select two.

Question 1mediummulti select
Full question →

A contractor pool changes every month. The operations team wants Azure role access to stay the same when people join or leave, without editing role assignments for each person. Which two actions should the administrator take? Select two.

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Create a security group in Microsoft Entra ID for the contractor pool.

A security group is the right identity container for changing membership. Contractors can be added or removed from the group without touching the Azure RBAC assignment itself, which keeps access administration simple and consistent over time.

B

Distractor review

Assign the Azure role directly to each contractor account.

Direct user assignments work, but they create maintenance overhead whenever contractors join or leave. That approach does not satisfy the goal of avoiding frequent role assignment changes for individual people.

C

Distractor review

Create a Microsoft 365 group and use it for VM sign-in.

Microsoft 365 groups are not the standard choice for Azure RBAC delegation tasks. They are oriented toward collaboration services, not least-privilege access administration for Azure resources.

D

Best answer

Assign the Azure role to the security group rather than to individual users.

Role assignment to the group is what makes membership changes automatic from an access-control perspective. As long as users are managed in the group, the RBAC assignment remains unchanged and reusable.

E

Distractor review

Use a user-assigned managed identity for each contractor.

Managed identities are for Azure resources, not human contractors. They are attached to workloads, so they do not solve human access delegation or membership-based administration.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Related practice questions

Related AZ-104 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Create a security group in Microsoft Entra ID for the contractor pool. — To reduce ongoing administration, Azure RBAC should be assigned to a security group rather than to each person. The security group becomes the stable access boundary, while contractor turnover is handled only by updating group membership in Microsoft Entra ID. This pattern is the standard way to keep access consistent when users change frequently and avoids repeated role reassignment work. Why others are wrong: Per-user role assignments create unnecessary maintenance, and Microsoft 365 groups are not the preferred identity object for RBAC delegation. Managed identities are tied to Azure workloads, not contractor accounts. The key design choice is to keep the role assignment stable and move user churn into group membership changes instead.

What should I do if I get this AZ-104 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.