mcAfee Secure Website
23

Microsoft AZ-104 Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

AZ-104 Training Materials $44.99

Reliable & Actual Study Materials for AZ-104 Exam Success

The Latest AZ-104 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-104 Video Course

    AZ-104 Training Course

    132 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Administrator (AZ-104) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
    exam =35
  • exam =37
    AZ-104 Video Course

    Training Course

    132 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 3

Question 20

An Azure subscription Contributor is asked to reset a cloud-only employee's Microsoft Entra password. The account is managed in Entra, and the Contributor's reset attempt fails for insufficient directory permissions. What is the appropriate remedy?

  1. Grant that operator subscription Owner, because all Azure resource roles automatically confer directory password reset privileges.
  2. Have an authorized directory administrator perform the reset, or delegate only a directory role whose scope permits it.
  3. Add the affected user to a storage-account file share to trigger automatic password reset.
  4. Grant the operator the Microsoft Entra Directory Readers role and retry the password reset.

Explanation

Correct Answer

B:

Password resets for Microsoft Entra directory users require the relevant authorized directory role and can depend on the target user's role or protection level. Route the operation to a suitably privileged identity administrator or assign a least-privilege supported role where organizational policy permits. Validate the delegated role's actual target-user eligibility rather than assuming Azure subscription Contributor can act on directory credentials. This respects the separation between resource-management RBAC and identity-administration permissions.

Incorrect Answers

A:

Subscription Owner is an Azure resource-management role, not an all-purpose Microsoft Entra directory role. Broadening Azure RBAC authority does not grant the required password reset permission for an Entra user. It also expands cloud infrastructure privileges unnecessarily, contrary to the limited administrative task.

C:

Azure Files handles file shares and related storage access; joining a user to a share has no mechanism for resetting their Microsoft Entra password. It also risks granting unrelated data-plane access. The failed operation is a directory authorization issue, so storage configuration cannot satisfy its prerequisite.

D:

Directory Readers provides directory read capabilities but does not authorize resetting arbitrary user passwords. Even though it is an Entra role rather than Azure RBAC, its permissions are insufficient for the intended credential operation. A properly scoped password-reset-capable administrator must perform or receive delegated authority for the task.

Question 21

An employee's surname is synchronized from on-premises Active Directory into Microsoft Entra ID. The cloud administrator changes the surname in Entra, but the next synchronization restores the old value. Where should the authoritative correction be made?

  1. In the source Active Directory user attributes, followed by the normal synchronization cycle.
  2. On the Azure subscription's billing profile because Entra reads names from invoices.
  3. Keep changing the synced user’s surname directly in the Entra portal after each synchronization.
  4. By permanently disabling Microsoft Entra Connect so the cloud value is never replaced.

Explanation

Correct Answer

A:

The on-premises directory is the source of authority for the synced identity and the relevant profile fields. Update the employee's name in the source AD account, then allow synchronization to publish the new value to Microsoft Entra ID. Confirm the resulting identity after the next sync and check applications that consume it. Editing a cloud copy alone is unreliable when the directory synchronization process owns that attribute and continues to send the old value.

Incorrect Answers

B:

Billing profiles account for Azure charges and business financial information; they are not authoritative for synchronized Microsoft Entra user surnames. Changing an invoice field would not update the on-premises directory. The synchronization engine would still propagate its existing identity value, perpetuating the observed mismatch.

C:

The latest synchronized value comes from on-premises Active Directory, where the user's mastered profile fields are managed. Repeating cloud-side edits would be overwritten again and would not correct the source of authority. Update the original AD user attribute and let identity synchronization publish the approved change.

D:

Disabling directory synchronization is a disproportionate response and can affect the entire hybrid identity lifecycle. The organization explicitly uses synchronized accounts, so its source-of-authority model should be respected. Fix the attribute where it is mastered and let the configured synchronization propagate the approved correction.

Question 22

A cloud-only Microsoft Entra security group was deleted yesterday, removing a team's access. The tenant uses the supported public-cloud preview for cloud security group soft deletion, and the original group must be recovered. What action should the administrator attempt?

  1. Create a new distribution list with the same display name, assuming the old object ID is reused.
  2. Wait until the fixed 30-day deletion retention period expires and then recreate the group.
  3. Find the group in Deleted groups, restore it using the supported workflow, and verify memberships and effective access.
  4. Restore only an Azure resource group; Entra groups are never eligible for soft-delete recovery.

Explanation

Correct Answer

C:

Microsoft documents recovery of cloud security groups during its supported preview in public clouds, subject to feature limits. Because this group was deleted yesterday, it is within the documented 30-day window; an authorized administrator can locate the original in Deleted groups and invoke Restore. Inspect the recovered object, group membership, and the downstream resource roles because asynchronous restoration and access propagation may need verification. Do not generalize this preview to distribution groups or unsupported tenants.

Incorrect Answers

A:

A distribution list is a mail-delivery object and is not a substitute for the deleted security group's access principal. Reusing a display name does not recreate the same directory object ID or restore its assignments. Distribution groups are also excluded from the stated Entra group soft-delete feature.

B:

Deleted Microsoft 365 groups and supported cloud security groups are retained for a limited 30-day recovery window; waiting past it risks permanent loss. The situation is only one day old, and the tenant explicitly has the relevant preview enabled. Recovery should occur while the original group is still restorable, not after retention expires.

D:

An Azure resource group is an infrastructure management container, not the Microsoft Entra directory group that holds the staff principal. Restoring infrastructure would not necessarily recover the deleted identity object or its memberships. The preview specifically supports cloud security group recovery under the documented conditions.

Question 23

Two Microsoft Entra security groups are both displayed as 'OpsReaders', but they have different object IDs and different Azure role assignments. An administrator must remove a departing contractor from only the group granting production access. Which identifier should guide the change?

  1. The common display name, since names are globally unique inside the tenant.
  2. Whichever OpsReaders group was most recently modified.
  3. The resource-group display label associated with one of the groups.
  4. The specific Microsoft Entra group object ID linked to the production role assignment.

Explanation

Correct Answer

D:

Azure RBAC assignments identify their security principals by directory object ID, so correlating that ID with the Microsoft Entra group resolves an ambiguous display name. First inspect the production assignment's principal identity, then modify membership in that exact group and verify effective access. This avoids accidentally modifying the other similarly named group or assuming that a visible name is unique. The same practice supports auditability when a group is later renamed.

Incorrect Answers

A:

Display names are not reliable unique identifiers for Microsoft Entra groups, and this case explicitly contains two matching names. Choosing by label can remove access from an unrelated group while leaving the sensitive grant intact. Use the directory object's immutable identifier linked to the actual role assignment to distinguish them.

B:

Modification time does not indicate which group's RBAC principal controls the production environment. A harmless membership update might make the wrong group appear newer. The required evidence is the ID on the production assignment, not an incidental timestamp that may change during routine administration.

C:

An Azure resource-group name identifies a management container rather than a directory security principal. Several identity groups may hold roles on the same resource group. Comparing only resource names would not establish which OpsReaders object has the production assignment or which membership must be changed.

Question 24

A contractor's Azure resource access is inherited through membership in a Microsoft Entra security group. The contractor's project ends today, but other group members must retain access. What is the most targeted first change?

  1. Delete the group and create it again without the contractor.
  2. Remove the contractor from the relevant group and verify that no separate access assignments remain.
  3. Delete the Azure subscription containing the protected resources.
  4. Place a CanNotDelete lock on the contractor's user account.

Explanation

Correct Answer

B:

The group's Azure role assignment grants access to its members, so removing the departing contractor from that group removes that inherited route once directory and token state propagate. Check other groups and direct role assignments to avoid incorrectly declaring complete revocation. Other approved members remain in the group and continue receiving its resource permissions. Revocation may also require session review for already issued tokens, depending on the application and risk policy.

Incorrect Answers

A:

Deleting the group removes its identity for every member and can break role assignments that reference its object ID. The requirement explicitly preserves other members' access. Removing one membership is more proportionate than destroying a shared security principal used by the team.

C:

Deleting a subscription would affect all resources, billing and administrators under that scope, far beyond the single contractor's entitlement. It would not be an acceptable access-removal mechanism for an operational project. Identity membership management gives a targeted way to revoke a specific inherited grant.

D:

An Azure management lock applies to resource deletion or write operations, not directly to Microsoft Entra group membership. A user directory object is not protected by a resource-group CanNotDelete lock in the manner suggested. The contractor's access comes from a security principal and RBAC, so adjust that relationship.

Question 25

A project lead is already the owner of an Entra security group and can add members to it. The lead tries to assign that group the Azure Reader role at the production resource-group scope, but Access control (IAM) denies the role assignment. What permission is actually missing?

  1. The ability to send email to the group’s members, which is mandatory for Azure RBAC.
  2. The ability to reset passwords of every account in the group.
  3. The Azure role-assignment write permission at the intended resource scope, held by an appropriately authorized RBAC administrator.
  4. An entitlement to edit the group’s display name in Microsoft Entra.

Explanation

Correct Answer

C:

Ownership of a Microsoft Entra security group controls certain directory membership operations, but it does not automatically grant permission to create Azure resource role assignments. The Azure portal requires Microsoft.Authorization/roleAssignments/write at the target scope, for example through a narrowly scoped Role Based Access Control Administrator or User Access Administrator grant. The group remains a valid principal; the lead lacks authority over the resource group’s IAM assignments. A permitted administrator should grant Reader at the required scope without escalating to subscription Owner unnecessarily.

Incorrect Answers

A:

Sending group email is unrelated to assigning Azure resource roles, and mail capabilities do not provide permissions over the Azure Authorization resource provider. The lead already owns the group but cannot grant its members resource access merely by contacting them. A scoped Azure RBAC assignment administrator must manage the actual role assignment.

B:

Password reset authority is a directory authentication permission and does not confer Azure RBAC role-assignment capabilities. Granting it to a group owner would add sensitive identity powers that are unnecessary for the Reader grant. The failure occurs in Azure Access control, which checks an authorization operation at the resource scope rather than a credential administration action.

D:

A group’s display name is a directory presentation property, not an Azure role-assignment authorization capability. Being allowed to change it would not create Reader access or satisfy the resource provider’s write permission check. Because the group already exists and has the intended members, the missing operation concerns role assignments at production resource-group scope, not directory metadata.

Question 26

Microsoft Entra dynamic security group sg-finance should contain only users whose authoritative Department is exactly `Finance`. Its current rule is `(user.department -contains "Fin")`; several legitimate `Support-FinOps` employees are incorrectly included because their Department values contain that substring. HR confirms all Department attributes are accurate. Which change directly fixes the membership rule without altering correct employee records?

  1. Replace the rule with `(user.department -eq "Finance")`, validate Finance and Support-FinOps test accounts, and allow the dynamic membership processor to recalculate the group.
  2. Manually remove the Support-FinOps users from the evaluated group but leave the `-contains "Fin"` expression unchanged.
  3. Change the Support-FinOps employees' authoritative Department properties to `Other` while retaining the broad `-contains "Fin"` rule.
  4. Rename the dynamic group to `Finance-Only`, since a group name automatically restricts all `Department` comparisons to exact matches.

Explanation

Correct Answer

A:

Microsoft Entra dynamic membership supports both `-contains` (substring) and `-eq` (exact equality). The present expression accepts Support-FinOps as well as Finance; changing the rule to equality removes those unintended matches without corrupting correct HR data. Validate sample users on the Validate Rules tab and allow asynchronous reevaluation to propagate. This differs from a different case where the attribute itself is stale.

Incorrect Answers

B:

Dynamic-group membership is calculated from the stored expression and user attributes; manual removals do not permanently repair an overbroad predicate. Because Support-FinOps continues to satisfy `-contains "Fin"`, the membership engine will continue selecting those accounts. Fix the rule itself and validate expected results instead of curating a supposedly dynamic group manually.

C:

HR has verified that Support-FinOps is the correct department value. Falsifying authoritative directory data to evade a broken group filter would damage identity governance and any other application relying on Department. Use the supported exact-equality operator in the dynamic rule; correcting an accurate source property is not an acceptable substitute.

D:

A group display name is descriptive metadata, not a dynamic membership predicate. Renaming the group leaves `(user.department -contains "Fin")` intact and can still admit any account with a matching substring. Only the rule expression and its evaluation determine automatic membership for these accounts.

Question 27

A user is a direct member of GroupB, which is itself nested inside GroupA. An application claims to honor GroupA access, but the user is denied. The administrator knows that services differ in how they evaluate nested groups. What should be checked?

  1. Assume every Microsoft cloud workload necessarily expands nested group membership for all authorization decisions.
  2. Assign the user Global Administrator to bypass the nested-group restriction.
  3. Rename GroupB so it is alphabetically adjacent to GroupA.
  4. Verify the specific application's support for transitive group membership and use a supported direct-membership design if required.

Explanation

Correct Answer

D:

The directory can represent nested groups, but the application or Azure feature consuming them determines whether nested membership is honored for the relevant authorization operation. Identify the exact service and inspect its documented direct-versus-transitive membership behavior; if unsupported, add eligible users directly or choose a supported access mechanism. This avoids claiming the nested relationship automatically grants rights and preserves least privilege. In particular, group-based licensing is documented as not supporting nested-group license inheritance.

Incorrect Answers

A:

Nested directory membership does not guarantee that every consuming service recursively evaluates all group relationships. Some applications or licensing features use direct members only. Assuming universal transitive behavior would leave the observed denial unexplained and might cause repeated ineffective grants.

B:

Global Administrator is a tenant-wide administrative privilege unrelated to whether the application resolves nested security-group membership. Granting it would massively expand risk while leaving service-specific authorization semantics unclear. Evaluate the actual membership and application's access implementation instead of escalating unrelated directory authority.

C:

Group names are labels, not predicates that force transitive authorization. Alphabetic order has no effect on Entra group expansion or the way a consuming application maps roles. The nested relationship must be assessed using supported membership semantics and access configuration.

Question 28

An audit script uses a Microsoft Entra user's display name to reconcile historical actions. After the user changes their name, the script wrongly treats the account as a new person. Which field is most suitable for durable identity correlation?

  1. The user's current display name, because it is unique and never changes.
  2. The user's Microsoft Entra object ID, retaining UPN as a sign-in identifier and display name as a presentation value.
  3. Use the user principal name as the permanent unique key because it can never change after the account is created.
  4. The most recent password reset timestamp, which is guaranteed unique for an account.

Explanation

Correct Answer

B:

The Microsoft Entra object ID identifies the directory object consistently while its display name and user principal name can change for legitimate reasons. Update the script to associate records with the stable ID and retain historical labels for readability when needed. UPN is often the user's sign-in name, but treating it as an immutable identity key would recreate the same rename problem. This design also reduces accidental cross-user matches when two people share a displayed name.

Incorrect Answers

A:

Display names are mutable presentation attributes and can be shared by multiple users. Using them as durable identity keys causes exactly the false-identity split described after a surname change. A human-readable label is useful for reports but should not replace a stable directory object identifier in joins or audit correlation.

C:

The UPN is often the sign-in identifier, but it can change when an employee's name or verified domain changes. Treating it as immutable recreates the audit-correlation problem in another field. Microsoft Entra object ID is the stable directory identifier for the identity object.

D:

Password reset times change whenever recovery or administrative actions occur and may be absent for some users. They are not an identity namespace and cannot reliably correlate historic events to a specific account. Authentication events should be associated with the directory object's stable identifier instead.

Question 29

An administrator can manage Azure VMs as subscription Contributor but gets a permissions error when editing a Microsoft Entra user's job title. The user is cloud-only. Where should the administrator check authorization?

  1. Upgrade the administrator from subscription Contributor to subscription Owner to enable editing Entra job information.
  2. The subscription's storage redundancy model, which controls directory property writes.
  3. Microsoft Entra directory role permissions for editing that user's profile, not just Azure RBAC.
  4. Assign the administrator an Azure User Access Administrator role at the subscription scope.

Explanation

Correct Answer

C:

Managing Microsoft Entra users is a directory control operation, and Azure subscription Contributor does not implicitly provide directory administration permissions. Check which directory role can edit the requested attribute of this target account, including any role scope or protection constraints. Use a properly delegated directory administrator or least-privileged supported role rather than granting more Azure infrastructure rights. This directly addresses why VM changes succeed but the profile update is denied.

Incorrect Answers

A:

Subscription Owner extends Azure resource-management privileges, not the Microsoft Entra directory roles that govern profile updates. The administrator might then change more cloud infrastructure while still lacking the correct user-property permission. Review the permitted Entra directory role and target account restrictions instead.

B:

Storage replication determines how storage data copies are maintained; it has no role in who may update Entra user profiles. Subscription Contributor does not turn a storage-account configuration into a directory permission. The governing permissions are those exposed by the identity directory's role model.

D:

The User Access Administrator role manages Azure role assignments rather than ordinary Microsoft Entra identity profile data. It belongs to the Azure control plane, not the directory user attribute write boundary. The requested job-title edit needs an appropriate directory administrator permission, so this role would not directly resolve the error.

Question 30

A cloud-only Microsoft Entra user was accidentally deleted five days ago. The account supported several application relationships, and IT wants to restore the original object if possible instead of creating a new identity. What is the correct next step?

  1. Recreate an identically named account and assume it inherits the original object ID automatically.
  2. Wait until the 30-day retention window expires before attempting recovery.
  3. Restore an Azure resource group containing the person's former applications.
  4. Find the user under Deleted users, restore the original within the supported window, and verify recovered access and licensing.

Explanation

Correct Answer

D:

Microsoft documents a 30-day suspended state for recently deleted Microsoft Entra users, so the administrator can restore the existing identity from Deleted users within the available window. Restoration preserves the original directory object's organization information rather than creating a new identity. After recovery, inspect group membership, effective application grants, and license availability; Microsoft notes license assignments can be restored even when capacity is low. This establishes what actually recovered before declaring user access repaired.

Incorrect Answers

A:

Creating a new account with an identical sign-in label gives it a different directory identity rather than restoring the original object ID. Existing application and group references may still target the deleted principal. The tenant has a supported recovery window, making restoration preferable to premature recreation.

B:

Recently deleted users remain restorable for 30 days, after which permanent deletion begins and recovery is unavailable. The account was deleted only five days ago, so waiting would decrease the opportunity to restore it. Act during the window and check that recovery succeeds before access is assumed to be available.

C:

An Azure resource group holds infrastructure resources, not the soft-deleted Microsoft Entra user object. Recovering or redeploying infrastructure would not automatically restore identity attributes, authentication settings, or directory relationships. The problem requires the directory's Deleted users recovery workflow with identity-level administrative authorization.