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 2

Question 10

Your tenant currently has only contoso.onmicrosoft.com as a verified user-principal-name suffix. A developer asks to create lee@newbrand.example as a member UPN, but newbrand.example has not been verified in your tenant. What should you do first?

  1. Create the member user with the unverified UPN and ignore any validation error.
  2. Verify ownership of newbrand.example in the tenant, or use an already verified UPN suffix until verification is complete.
  3. Assign Subscription Contributor to the developer, which automatically verifies external domains.
  4. Create an Azure Private DNS zone for newbrand.example and assume it establishes Microsoft Entra domain ownership.

Explanation

Correct Answer

B:

A Microsoft Entra user's UPN suffix must be a tenant-verified domain or an eligible existing tenant suffix. Adding a custom domain to the tenant requires a supported ownership-verification process before it can be used for normal member UPNs. Verify the new domain first, then create or update the user with the intended UPN. Using the already verified onmicrosoft.com suffix is a temporary alternative that creates an actual valid user without asserting ownership of an unverified company domain.

Incorrect Answers

A:

An unverified custom UPN suffix is not usable merely because the developer supplied an address. The directory must ensure that the tenant has ownership of the sign-in domain before assigning it to managed users. Ignoring a validation failure would not create a reliable user object with the requested sign-in name and may encourage an incorrect workaround. Domain verification is a tenant identity-domain operation, not an Azure networking or resource-management privilege grant.

C:

Azure subscription Contributor controls resource management operations at an Azure scope. It cannot prove ownership of an external DNS domain to Microsoft Entra, and it does not grant the necessary directory custom-domain verification permissions. The desired UPN requires a tenant identity-domain operation rather than broader Azure resource-management access.

D:

An Azure Private DNS zone serves private name resolution for linked virtual networks, not public domain ownership verification for Microsoft Entra identities. Creating such a zone does not prove possession of the company's public domain records. The administrator must complete the supported tenant domain verification workflow or choose a verified suffix.

Question 11

A cloud-only Microsoft Entra user was created yesterday with the wrong UPN spelling. The employee already has a user object ID, audit history, and application assignments. What is the best corrective action?

  1. Delete the existing user and create a replacement with a new object ID to obtain the corrected spelling.
  2. Edit the existing user principal name to the approved verified-domain value and check dependent sign-in integrations.
  3. Change the display name only and assume the UPN used for authentication also changes.
  4. Rename the Azure subscription containing the employee's application resources.

Explanation

Correct Answer

B:

The user object ID is the stable directory identity for the existing account and its assignments. Correcting the UPN on that object is the appropriate way to fix the sign-in name without creating a disconnected duplicate identity. The new suffix must remain within permitted verified domains, and applications or user workflows that depend on the old name should be checked. A display name change affects presentation, not necessarily the sign-in identifier. This correction preserves lifecycle and audit continuity.

Incorrect Answers

A:

Deleting and recreating the user would introduce a different directory object ID and could break resource assignments, app references or audit correlation. The problem is the spelling of a mutable sign-in name, not a need to replace the security principal. Updating the existing account is less disruptive and preserves the original identity relationships. Changing UPN may affect integrations using the old string, so assess those dependencies before the rename.

C:

Display name is a user-facing label, while user principal name is an identity field commonly used at sign-in. Changing only the display name cannot guarantee that the mistyped authentication name is corrected. The administrator must inspect and update the existing account's UPN, respecting the supported verified suffix and its dependencies.

D:

Azure subscription names belong to the resource management environment and do not control the sign-in name of an Entra directory user. Renaming the subscription would not fix the UPN typo and might create administrative confusion for unrelated resources. The correction belongs on the existing user object.

Question 12

A company needs a new user who will exist only in Microsoft Entra ID, with no corresponding identity in its on-premises Active Directory or synchronization feed. Which account provisioning method meets that requirement?

  1. Create the person in the on-premises directory and wait for the sync agent to provision the cloud account.
  2. Create a cloud-only member user directly in Microsoft Entra and manage the account there.
  3. Create a management group because it represents a tenant-wide workforce directory.
  4. Create an Azure Storage account with the person's name as a resource tag.

Explanation

Correct Answer

B:

A cloud-only Microsoft Entra user has its source of authority in the cloud directory and does not require a matching on-premises Active Directory account. The administrator can create the member user directly in Entra, set the approved UPN and initial sign-in policy, and manage supported properties through the cloud identity lifecycle. This differs from synchronized identities, for which many attributes originate in the on-premises system. Creating the account at the correct authority source prevents synchronization conflicts or unintended local dependencies.

Incorrect Answers

A:

Creating the account first in Windows Server Active Directory makes it an on-premises-sourced identity if it is synchronized to Entra. That is the opposite of the explicit cloud-only requirement. It would also introduce local password and attribute management responsibilities that the company has chosen not to use for this person. Authentication settings and license assignments can then be governed under the standard cloud identity policy for that individual.

C:

Azure management groups organize subscriptions for governance and inherited Azure Policy or RBAC. They are not workforce directories and do not represent individual user authentication objects. Creating a management group cannot supply a cloud-only UPN or the directory account's login settings. It solves a different administrative problem.

D:

A storage account is a data resource, and its tag values are arbitrary metadata rather than identity records. It cannot authenticate an employee to Entra-backed applications or create a directory security principal. Identity provisioning must occur through the supported Entra user management or Microsoft Graph interface.

Question 13

An identity engineer has designed a dynamic group membership rule for employees in two departments. Before enabling it for an important access-control group, the engineer wants to confirm that the selected attributes produce the intended user set. What is the safest next step?

  1. Activate the rule immediately and remove accidental users only after they access protected data.
  2. Use the supported rule-validation or membership preview facilities and review actual directory attributes before enabling the rule.
  3. Switch to a distribution-only group to guarantee resource RBAC still works without a membership rule.
  4. Grant all existing directory users a subscription-wide Reader role while the rule is tested.

Explanation

Correct Answer

B:

Dynamic membership is evaluated from directory attributes, so an incorrect expression can add or exclude a large set of users without a manual approval at each membership change. The administrator should validate supported rule syntax and property values, preview or test the matches where the tenant's capabilities allow it, and then apply the rule under the appropriate group licensing and access controls. Reviewing the predicted membership before enabling sensitive authorization helps catch unintended attribute combinations or missing data early.

Incorrect Answers

A:

Turning on an unreviewed rule for a sensitive group can grant access to unintended members before administrators notice. Manual cleanup afterward does not erase any access already exercised. The goal is preventive validation of the rule against current user attributes, not a production trial without membership acceptance checks. This check is especially important when the resulting group membership drives sensitive application access or licensing entitlements.

C:

A mail distribution list does not substitute for a supported security principal used in Azure RBAC assignments. Changing the group to a distribution-only object would not solve uncertainty about which users satisfy the dynamic attribute expression. The safer approach is to inspect and validate the intended rule on the appropriate Entra group type.

D:

Granting broad subscription Reader access during testing would bypass the intended group membership control and expose unrelated resources to users who should not have access. The dynamic rule should be validated without creating a temporary tenant-wide or subscription-wide permission grant. The scenario requires controlled group membership, not a parallel blanket access path.

Question 14

A project coordinator created an Exchange mail distribution list named AppOperators. Azure Access control (IAM) does not accept that mail-only list as the principal for a Reader role assignment on an application resource group. Which explanation correctly identifies the root cause?

  1. Azure RBAC Reader cannot be assigned to any group at resource-group scope; only subscriptions are allowed.
  2. A distribution list will work after the administrator adds its SMTP address to the resource group tags.
  3. An administrator must first assign the distribution list a Microsoft Entra Global Administrator role.
  4. A mail-only distribution list routes messages but is not an eligible Azure RBAC security principal; use an appropriately managed Entra security group instead.

Explanation

Correct Answer

D:

Mail distribution lists organize recipients for email delivery, whereas Azure resource role assignments require a supported Microsoft Entra security principal. A mail-only distribution list does not become an Azure RBAC principal simply because its members are employees. Use an eligible security group whose membership is governed by access policy, then have an appropriately authorized administrator assign the intended resource role. This explains the failure without repeating the separate question about the whole two-step provisioning process.

Incorrect Answers

A:

Azure RBAC supports assigning the Reader role to eligible users, groups, or service principals at resource-group scope. The error is the type of mail-only list chosen, not the resource scope itself. Moving the assignment up to subscription would grant far broader access and would still not transform that distribution object into a security principal recognized by Azure resource authorization.

B:

Resource tags are metadata for inventory, automation, or cost analysis; they are not access-control entries and do not authorize mail recipients to view a resource. Storing an SMTP address in a tag does not change the underlying group object into an eligible Microsoft Entra security principal. Azure IAM must evaluate an actual supported principal and role assignment.

C:

Microsoft Entra Global Administrator is a powerful directory administrative role, not a prerequisite for a group to receive Azure Reader. Assigning it to a mail-only distribution list would not repair the principal type, and using high privilege for simple resource viewing would violate least privilege. An eligible security group with an appropriately scoped resource role is the intended authorization structure.

Question 15

A project group needs someone to approve and maintain its Entra security-group membership. The designated team lead must not gain the ability to change Azure subscriptions or manage every directory user. What should an administrator assign?

  1. Azure subscription Owner, which allows unrestricted access to every related directory group.
  2. Tenant-wide Global Administrator so the lead can approve any member change.
  3. Eligible ownership of the specified Microsoft Entra group or a narrowly scoped membership administration role.
  4. Azure VM Contributor on the resource group containing the team's applications.

Explanation

Correct Answer

C:

Group ownership or an appropriately scoped directory membership administration permission permits management of the designated group's approved member set without granting broad tenant or Azure subscription privileges. The administrator should use the permission model supported for the group type and protect any role-assignable or privileged group with its additional controls. This matches the stated job of maintaining one membership collection. Azure RBAC subscription roles govern cloud resources, whereas Entra group membership is a directory object administration operation.

Incorrect Answers

A:

Subscription Owner is a very broad Azure resource-management role and does not serve as a narrowly scoped directory group membership assignment. Granting it would expose unrelated resource operations and unnecessarily expand the lead's authority. The requirement is to administer one Entra security group, not take ownership of every resource in an Azure subscription.

B:

Global Administrator can manage extensive Microsoft Entra directory settings and identities, far beyond the intended group. Giving that role to a project lead for routine membership changes violates the required scope of authority. The organization should delegate eligible ownership of the specific group or a carefully constrained directory role instead. The exact ownership capability should be checked for this group type, particularly when privileged role assignments impose extra restrictions.

D:

Virtual Machine Contributor grants management actions for Azure VMs within a scope; it does not make the holder the owner or membership administrator of a Microsoft Entra security group. The lead could manage unrelated compute objects while still lacking the directory permission needed to approve group members. Use a group-specific Entra permission.

Question 16

A Microsoft Entra employee changes their legal surname. The account already has application assignments, authentication methods, and an object ID referenced by audit processes. HR wants the new name displayed, but the underlying identity must remain continuous. What should the administrator do?

  1. Change the existing user's display name and relevant profile attributes while keeping the same directory object.
  2. Delete the account and create a replacement using the new surname.
  3. Change only the employee’s mail nickname while leaving the incorrect display name and surname unchanged.
  4. Create a separate B2B guest identity with the new surname and grant it the old account's access.

Explanation

Correct Answer

A:

Updating the existing Microsoft Entra user preserves the object's identity and its established access relationships while changing the user-facing name fields. The immutable object ID continues to correlate audit records and application references even when a display name changes. Review any downstream application that caches user attributes, but do not destroy the user object merely to correct a name. Changes to these profile fields are directory operations rather than Azure resource-group changes.

Incorrect Answers

B:

Deleting and recreating an identity generates a different object ID, disrupting assignments and audit references tied to the original account. Some deleted-object recovery features cannot automatically rebind every external application integration. The stated requirement is a profile update with continuity, which makes recreation unnecessary and potentially destructive.

C:

A mail nickname can participate in email-related naming but is not a substitute for updating the user's legal surname or display name. HR explicitly needs the new name shown across directory-backed applications. Correct the appropriate profile attributes on the existing user object so identity continuity is preserved.

D:

B2B identities support collaboration with users from outside the organization, not surname updates for an existing employee account. Creating a second identity would fracture authentication, membership, and audit trails. The original user object already fulfills the internal sign-in requirement, so modify its permitted attributes directly.

Question 17

An Entra security group uses a dynamic rule based on the Department attribute. A cloud-only employee transfers from Support to Finance, yet still has Support access because the old attribute remains. Which action should you take first?

  1. Remove the user manually from the evaluated dynamic group's member list without changing their profile.
  2. Update the authoritative Department field on the employee's existing user account and allow the membership rule to reevaluate.
  3. Create a new Finance subscription so the user inherits a different Department value.
  4. Change the employee's display name to include Finance and expect the dynamic rule to match automatically.

Explanation

Correct Answer

B:

A dynamic group evaluates specified Microsoft Entra user properties, so the erroneous Department attribute is the operative cause of the stale membership. Correct the employee's authoritative department value, then allow the rule processing cycle to recalculate which groups include the person. Check the resulting effective group access because processing is asynchronous and other assignments may remain. This repairs the source of the entitlement rather than temporarily masking the symptom.

Incorrect Answers

A:

Administrators cannot reliably solve an attribute-driven membership problem by manually editing users who are included by a dynamic rule. The rule continues to evaluate the stored Department attribute and can restore the same incorrect membership. Direct changes to an evaluated dynamic group's members are not the intended control path. Update the source data or the rule itself instead.

C:

Azure subscriptions define resource ownership, billing, and management boundaries; creating one cannot update an employee's Microsoft Entra Department property. It would also introduce unnecessary governance and cost implications. The existing group is driven by a directory attribute, not the subscription in which resources happen to reside.

D:

A display name is a presentation attribute and does not substitute for the Department field referenced by the group's dynamic membership expression. Appending Finance to a name leaves the original rule input unchanged. Correct the attribute used by the rule, then verify which users the rule actually includes.

Question 18

A cloud-only Microsoft Entra user may be compromised. Security needs to prevent new logins quickly while it investigates, without deleting the account or interrupting unrelated employees. Which administrative action directly addresses the sign-in risk?

  1. Remove the user from one ordinary application group, leaving sign-in enabled.
  2. Place a CanNotDelete lock on the Azure resource group containing the user's applications.
  3. Block sign-in for the affected Microsoft Entra user and evaluate revocation of existing sessions.
  4. Revoke one application assignment but leave the user’s tenant sign-in status enabled.

Explanation

Correct Answer

C:

Blocking sign-in on the identified Microsoft Entra user directly prevents the account from completing new tenant sign-ins while preserving the directory object for investigation. Because previously issued sessions or tokens may remain active for some time, incident response should also consider the supported session-revocation and credential-remediation actions. This is an identity-level containment measure and does not require deleting the user, thereby preserving evidence and account relationships.

Incorrect Answers

A:

Removing one group may reduce access to that particular application, but it does not prevent the account from authenticating to the tenant or other assigned services. A compromised credential could still obtain access through direct grants or other groups. The requested emergency control operates at the user sign-in boundary, not a single entitlement.

B:

Azure management locks protect resource operations through the control plane; they do not disable Microsoft Entra authentication for a user. The resource group is a container for infrastructure and cannot serve as an account suspension mechanism. Applying a lock could obstruct administrators trying to manage applications during the incident.

D:

Removing one application entitlement reduces access to that service but does not stop the compromised account from signing into the tenant or other applications. The security requirement concerns new authentication across the user identity. Block sign-in at the directory account level, then review existing sessions and grants.

Question 19

A cloud-only Microsoft Entra member currently signs in as nora@oldbrand.example. The organization has verified newbrand.example and must change Nora's sign-in name without losing her group memberships and resource assignments. What is the best approach?

  1. Delete Nora and create a new account using nora@newbrand.example so it has a new object ID.
  2. Add a new verified domain but create a second user account rather than update Nora’s UPN.
  3. Convert Nora to an external guest in the same tenant before changing her address.
  4. Update Nora's existing user principal name to the verified suffix and assess applications that depend on the old UPN.

Explanation

Correct Answer

D:

Changing the existing user principal name retains the underlying Microsoft Entra object ID and normally preserves directory group and resource relationships. The suffix is verified, satisfying the tenant's custom-domain requirement. Before switching, identify apps or scripts that use the old UPN as a literal key and plan the associated sign-in communication. The distinction between an immutable object identifier and a mutable sign-in name is what allows a controlled rename.

Incorrect Answers

A:

A deleted-and-recreated member receives a new object ID that may no longer match access grants, audit references, or integrations. The problem is a sign-in name change, not a demand for a new identity. Replacing the user increases migration risk and can orphan permissions tied to the original directory object.

B:

The new domain is already verified, so the naming prerequisite is satisfied; the issue is how to preserve Nora's identity. Creating a second user would receive a different object ID and could separate her existing application and group assignments. Change the UPN on the original user instead.

C:

Guest accounts are designed for external collaboration and are not required to rename an internal employee's UPN. Conversion would complicate the identity lifecycle and does not address the specified application dependencies. The user already has the correct member identity and needs a field update, not a new category of account.

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.