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 1

Question 1

A company has verified contoso.example as a Microsoft Entra custom domain. HR needs a new cloud-only employee to sign in as mia@contoso.example tomorrow. No account exists for Mia yet. Which action creates the required sign-in identity?

  1. Create a Microsoft Entra member user whose user principal name is mia@contoso.example and set the approved initial authentication settings.
  2. Create a security group called Mia and assign it a subscription Reader role.
  3. Invite mia@contoso.example as an external B2B guest user from another organization.
  4. Create a resource group called mia and assign its tags to the employee.

Explanation

Correct Answer

A:

A Microsoft Entra member user is the directory object that can represent an employee for cloud sign-in. The requested custom suffix has already been verified, so the administrator can create the cloud identity with the specified UPN and the organization's permitted initial credential and authentication settings. A security group or Azure resource group cannot replace an interactive user object. The administrator should also follow onboarding controls for the account rather than granting broad subscription privileges merely to make sign-in possible.

Incorrect Answers

B:

A security group aggregates identities for authorization or policy targeting; it is not itself the employee's sign-in account. Giving the group Reader at subscription scope would create an access grant, not the named user with a usable UPN. It would also introduce unnecessary Azure access before the employee's actual job role has been established.

C:

B2B guest invitations are intended for collaboration with identities managed by an external organization. The case states that HR needs a new cloud-only workforce member and no external home identity is supplied. Creating a guest invitation would not meet the requested member-user lifecycle or initial sign-in configuration for the company's own employee.

D:

Azure resource groups are management containers for Azure resources such as VMs and storage accounts. Naming a resource group after the employee neither creates a Microsoft Entra directory user nor provisions a UPN. Tags only annotate the resource group's metadata, so this operation cannot establish Mia's required authentication identity.

Question 2

An Entra administrator receives an approved CSV containing 600 new workforce accounts with verified-domain UPNs and required fields. Each account must be provisioned consistently before a scheduled onboarding date. Which approach best reduces manual errors?

  1. Create each user separately through the portal's New user pane, copying values by hand.
  2. Use the supported Microsoft Entra bulk-create user workflow with a validated CSV mapping and inspect processing results.
  3. Upload the CSV as a resource-group tag file so Azure Resource Manager creates all directory users.
  4. Create one shared employee account and assign all 600 people its password.

Explanation

Correct Answer

B:

The supported bulk user creation workflow accepts a CSV prepared to the expected directory user schema, making it appropriate for repetitive, authorized onboarding. The administrator should validate UPN uniqueness, required fields, eligible domains and file format before running it, then inspect the result report for row-specific failures. A bulk operation improves consistency but is not a substitute for post-provisioning checks such as license and authentication onboarding. It creates individual identities, preserving per-user accountability and future lifecycle control.

Incorrect Answers

A:

Manual creation can work for an isolated user, but repeating it hundreds of times increases transcription errors and makes checking for skipped rows difficult. The organization already has a structured approved source. A bulk directory workflow provides traceable results and can expose individual failures rather than relying on a human to remember which names were entered. The operation should run with an authorized directory identity, and its failure report should be reconciled against the approved HR source list.

C:

Azure Resource Manager tags describe Azure resources, while Microsoft Entra users are directory objects. Uploading employee records as a resource-group metadata file does not invoke a supported identity creation API. It would also mishandle personal data by placing workforce details in a management annotation rather than an authorized onboarding process.

D:

A shared identity destroys per-person authentication, auditing and access revocation. There would be no reliable way to determine which of the 600 people performed an action, and disabling one employee's access would affect everybody. The scenario explicitly requires separate workforce accounts, which must be individually created and managed.

Question 3

A consulting company manages its own Microsoft Entra tenant. One of its employees must collaborate in your organization's Microsoft Teams project without receiving a new local workforce account. Your administrators need to revoke the consultant's access at project completion. What should you create?

  1. A Microsoft Entra B2B guest invitation to the consultant's existing external identity, with scoped project membership.
  2. A new shared local member account for every consultant in that partner company.
  3. An Azure subscription Owner assignment to the consultant's company domain.
  4. A public anonymous link to every Teams and SharePoint resource used by the project.

Explanation

Correct Answer

A:

Microsoft Entra B2B collaboration allows the partner employee to use a home-organization identity while your tenant represents the invited guest and controls local application access. The administrator can invite the specific address, grant only the approved Teams or underlying resource membership, and remove that tenant access when the engagement ends. This separates the partner's authentication lifecycle from your resource authorization. External collaboration settings and cross-tenant policies may still need review, but a new ordinary workforce identity is not required.

Incorrect Answers

B:

Creating shared local accounts for external workers would separate their access from the authentic home-tenant identity and prevent reliable per-user auditing. A new member credential would also add an unnecessary password lifecycle to the project. B2B collaboration is specifically designed to preserve external identity ownership while restricting what the invited person can access in the host tenant.

C:

Azure subscription Owner is a broad Azure Resource Manager authorization role, not an identity invitation or Teams project membership operation. Assigning it would expose resource-management powers far beyond collaboration needs and would not be a justified method of provisioning external guest participation. The project requires narrowly scoped application access to one individual.

D:

Anonymous sharing removes the requirement to authenticate the intended collaborator and cannot ensure that only the partner employee receives access. Sharing broad workspace contents publicly also violates the principle of limiting project access to the invited user. Use the external guest's identity and explicit membership, rather than bypassing identity-based control.

Question 4

An approved provisioning service must create cloud-only Microsoft Entra users at night when no administrator is signed in. The service has an application identity and a reviewed identity-governance policy. Which method supports that noninteractive workflow?

  1. Run a Graph user-creation request with appropriate application permissions and tenant admin consent, validating each new account.
  2. Send an anonymous HTTP POST to Azure Resource Manager's subscription endpoint to create directory users.
  3. Assign the service principal the Azure VM Contributor role and expect user creation to become available.
  4. Store a human Global Administrator password in the script and interactively sign in once per account.

Explanation

Correct Answer

A:

Microsoft Graph exposes directory user operations, including user creation, and an application can act noninteractively when it has the required application permission and administrator approval. The service must validate the new user's required attributes, unique UPN and permitted domain, and log failures without leaking credential material. Azure Resource Manager roles do not substitute for Microsoft Entra directory authorization. Limiting the provisioning identity to the permissions it needs and reviewing its operations provides a safer automation pattern than embedding a privileged person's password.

Incorrect Answers

B:

Azure Resource Manager subscription APIs manage subscription-scoped Azure resources and governance, not anonymous writes to Microsoft Entra directory objects. An unauthenticated request would not have a trusted tenant identity or the required directory privileges. The correct API and permission model must match the actual identity resource being created, which in this case is a Microsoft Entra user.

C:

Virtual Machine Contributor grants management actions for specified Azure VM resources at an assigned Azure scope. It does not confer Microsoft Graph application permissions to create Entra users. Granting unrelated compute rights would increase the automation identity's privileges while leaving the directory provisioning problem unresolved. Directory operations require Entra/Graph authorization instead.

D:

Storing a Global Administrator password in automation creates a long-lived, highly privileged secret and introduces interactive authentication dependencies into an unattended process. A compromise could grant much broader tenant control than user provisioning needs. Use an application identity with least-privileged approved Microsoft Graph permissions and controlled credential or managed-identity handling where supported.

Question 5

A new employee must authenticate to a company application. The operations team also wants one reusable identity collection for assigning Azure Reader to a set of employees. Which design distinguishes these two directory objects correctly?

  1. Create only an Azure resource group; its name can act as both login and access collection.
  2. Create the employee as a Microsoft Entra user, and use a separate eligible security group to aggregate people for RBAC.
  3. Create an Entra security group with the employee's display name and use that group to authenticate interactively.
  4. Create a public storage container and treat possession of its URL as workforce authentication.

Explanation

Correct Answer

B:

A user object represents the individual security principal for sign-in, whereas an Entra security group represents a membership set that can be assigned Azure RBAC and other eligible permissions. The application can authenticate the employee as a user while administrators maintain group membership to control authorization for multiple people consistently. This separation supports account lifecycle, auditability and least privilege. A group may be granted a role, but it cannot replace the employee's personal sign-in identity.

Incorrect Answers

A:

An Azure resource group organizes resources for management scope, policy and deployment, but it is not a Microsoft Entra login identity or membership group. Its name and tags do not create a security principal that can authenticate to the application. Using a resource group for both functions confuses Azure resource organization with directory authentication and authorization. When an engineer leaves the team, group membership can be removed without deleting the personal directory account or rewriting every role assignment.

C:

A security group can receive assignments and contain users, but it is not a substitute for a person's interactive account. Creating only a group omits the credential and individual identity needed for authentication and auditing. Membership of an eligible security group should be attached to existing user objects rather than treated as a shared user account.

D:

A public storage URL is a resource locator and does not prove the identity of a company employee. Sharing an anonymous container can expose data without any user-specific access record. Authentication should use the employee's Entra account, and group-based access should be granted using the appropriate role and scope, not a URL.

Question 6

An Azure engineering team has eight individual Microsoft Entra users. The team must be granted Reader access to every resource in the development resource group, and membership changes should not require eight new role assignments. Which TWO actions are appropriate? Select TWO answers.

  1. Create an eligible Microsoft Entra security group and put the engineers into it.
  2. Assign Azure RBAC Reader to that group at the development resource-group scope.
  3. Assign each engineer Global Administrator so group membership is unnecessary.
  4. Create a distribution-only mail list and use it as the Azure management role holder.
  5. Place the engineers' email addresses into a resource-group tag as the authorization list.

Explanation

Correct Answers

A:

A security group provides a single directory security principal whose membership administrators can update without changing the underlying resource role assignment. Each of the eight users can be added to the group, and future authorized membership changes become a directory operation rather than repeated Azure RBAC changes. The group itself is not a sign-in account, and its membership does not grant Azure Reader until the separate scoped role assignment exists. Group ownership and membership administration should also remain appropriately restricted.

B:

Azure RBAC role assignments combine a principal, a role definition and an Azure resource scope. Assigning Reader to the security group at the development resource group grants read-only management access to eligible group members for the contained resources, subject to other Azure controls. This avoids unnecessary Reader access to production or unrelated subscription resources. The assignment works together with the membership group rather than replacing the need to maintain individual user objects.

Incorrect Answers

C:

Global Administrator is a powerful Microsoft Entra directory role, not the minimum Azure RBAC permission for viewing a development resource group. It does not establish the intended scoped Azure Reader group assignment and grants unnecessary tenant-wide directory administration. The requirement can be met using a regular security group and a narrowly scoped Reader role.

D:

A mail distribution list is designed to route messages, not to serve as an ordinary Azure resource access security principal. The scenario asks for resource management authorization, which needs an eligible Entra security group and Azure RBAC assignment. Choosing a mail-only group would not provide the reliable access-control model needed for engineers in that development group.

E:

Resource tags are searchable metadata values; Azure RBAC does not evaluate a tag containing email addresses as a principal membership list. A resource-group tag would not authorize the engineers to view resources. The access policy must refer to an actual security principal through a proper role assignment at the correct resource scope.

Question 7

A department requests a membership collection that provides its staff with a shared Outlook inbox and calendar, and the same membership should support Microsoft 365 collaboration workloads. It does not need to act solely as an Azure RBAC access group. What type is most appropriate?

  1. A Microsoft Entra administrative unit, because it automatically creates an Outlook group inbox.
  2. A Microsoft 365 group with the required collaboration resources and managed membership.
  3. A resource group in Azure, because it provisions Exchange group mailboxes by name.
  4. A distribution-only contact with no group identity or collaboration membership.

Explanation

Correct Answer

B:

Microsoft 365 groups provide a collaboration-oriented membership model linked to supported workloads such as an Outlook group inbox and shared calendar. This makes the group type a closer fit than a security-only collection when the business specifically needs shared collaboration resources. Administrators can manage membership under tenant controls and grant application access separately as required. The choice of group type is driven by the requested mailbox/calendar capability, not by a need to confer Azure subscription permissions.

Incorrect Answers

A:

An administrative unit is a Microsoft Entra directory management scope for delegating administrative rights over selected directory objects. It is not a collaboration workspace and does not automatically generate an Outlook inbox or calendar for members. Using it as if it were a Microsoft 365 group would confuse administrative scoping with shared team communication resources. The group type and tenant policy should be checked because not every mail-enabled collection supplies the requested collaboration services.

C:

Azure resource groups contain Azure cloud resources and define management boundaries for deployments, tags and RBAC. They do not create Exchange Online collaboration mailboxes or calendars. The requested artifacts are associated with Microsoft 365 collaboration, so a similarly named Azure management container cannot satisfy the group's functional requirements.

D:

A distribution contact or simple mail-only address may route messages, but it does not establish the full Microsoft 365 group collaboration lifecycle requested here. The scenario requires shared calendar and supported team resources managed for a common member set. An ordinary distribution-only object lacks the integrated group collaboration model, even if it receives email.

Question 8

A support company's Entra accounts include a reliable Department attribute. Staff frequently transfer between departments, and the support application needs a security group whose membership reflects current Department=Support values automatically. What should the administrator configure?

  1. Use assigned group membership and manually review every user at the end of each year.
  2. Create an eligible dynamic security group with a validated Department attribute membership rule.
  3. Give each department manager the Azure subscription Owner role so they can change user directory attributes freely.
  4. Use a plain resource-group tag called Department=Support as the membership controller.

Explanation

Correct Answer

B:

Dynamic group membership evaluates configured directory attributes against a rule, allowing membership to change when authoritative user data such as Department changes. Create a supported dynamic security group, validate its matches, and account for licensing and evaluation delays. A user transfer then changes the attribute that the rule consumes instead of requiring manual edits to the group membership. This produces a more consistent access collection for a frequently changing department than a static group.

Incorrect Answers

A:

Assigned membership depends on explicit administrator add/remove operations and does not automatically follow Department attribute changes. With frequent transfers, annual manual reviews would leave users in the wrong group for long periods. A dynamic rule is more suited to this attribute-driven policy, provided the tenant meets its licensing and group type requirements. This design depends on accurate authoritative attributes, so department data quality is part of the ongoing membership control.

C:

Azure subscription Owner grants broad resource management rights, not a mechanism to define dynamic Microsoft Entra group membership. Granting those permissions to department managers would increase access far beyond the requested security-group administration. Directory attributes and dynamic group rules should be governed through the appropriate Entra controls instead.

D:

Resource-group tags label Azure management resources and are not the input data evaluated for Entra dynamic security-group membership. A Department tag on an Azure resource group does not automatically add or remove users from a directory security group. The membership rule should reference the users' directory attributes and be evaluated by Microsoft Entra.

Question 9

A privileged operations team has a security group that controls access to sensitive Azure resources. Management requires every new member to undergo individual approval; staff attributes must never enroll people automatically. Which membership type best matches this requirement?

  1. Dynamic membership based on Department so every current operations employee joins automatically.
  2. An assigned-membership security group with controlled approvals for member additions and removals.
  3. A public anonymous group where users join by visiting a shared URL.
  4. An Azure resource-group tag listing everyone with a similar job title.

Explanation

Correct Answer

B:

Assigned group membership is appropriate when a security-sensitive set of members must be changed only through explicit authorized operations. The team can maintain a controlled approval workflow and have administrators or properly delegated owners add approved users to the security group. This preserves an auditable membership boundary independently of changing organizational attributes. Dynamic membership would be inappropriate because a department or title change might grant access without the case-specific approval that management requires.

Incorrect Answers

A:

An attribute-based dynamic group automatically adjusts membership when its rule evaluates true. That is useful for broad role-based organizational grouping, but this scenario expressly forbids automatic enrollment into a sensitive privileged group. A user could gain the relevant attribute without passing the required individual access approval process. The approval record can be checked during periodic access reviews, independently of automatic attribute-based group processing.

C:

A public group that anyone can join has no meaningful administrative membership control and would undermine the intended privilege boundary. The Azure resources are sensitive, and membership must be limited to authorized users. An explicitly controlled Entra security group offers an identity-backed principal for RBAC while preserving membership approval.

D:

Azure tags are resource metadata, not Microsoft Entra membership or access-control lists. Placing names or job titles in tags does not enforce an approval workflow and does not independently authorize a person through Azure RBAC. The correct design uses an eligible security principal with restricted membership management.

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.