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 12

Question 110

A deployment identity holds Virtual Machine Contributor on an existing VM but a redeployment fails when it tries to create a new NIC and attach it to a subnet. What should you inspect or change?

  1. Assign Reader on the VM only.
  2. Assign Storage Blob Data Contributor on the subscription.
  3. Add another Virtual Machine Contributor grant to the same VM.
  4. Grant the required network-resource and subnet-join operations at the relevant dependency scopes.

Explanation

Correct Answer

D:

Virtual Machine Contributor focuses on compute management and does not automatically provide full network management rights for creating NICs or joining subnets. A deployment that creates dependent networking resources requires permissions for those resources at their own scopes, often through a network-specific role or narrowly defined custom actions. The correct fix is to inspect the failed Microsoft.Network operation and assign only the missing dependency rights, not to assume the VM role covers every resource in the template.

Incorrect Answers

A:

Reader on the VM allows inspection of its management properties but supplies no NIC creation or subnet-join write operations. The authorization failure occurs against the network resources needed by redeployment, not the VM's read visibility. The identity must receive the appropriate Microsoft.Network permissions at the NIC and subnet locations.

B:

Blob Data Contributor authorizes operations on blob objects, not creation of Azure network interfaces or subnet attachment. The failing deployment operation is on the Microsoft.Network resource provider. A data-plane storage role would leave that failure unchanged and expose unrelated blob data permissions across the subscription.

C:

Duplicating the existing compute role on the same VM does not add the missing network permission set. Azure RBAC permissions depend on both the role definition's allowed actions and the operation's resource scope. The deployment needs appropriate NIC and subnet rights, so adding the same VM role again cannot resolve this separate dependency.

Question 111

A build pipeline uses one managed identity to read objects from storage account stbuild and retrieve a secret from vault kvbuild. It must not access peer accounts, vaults, or other resource families. Which assignment design best fits?

  1. Assign subscription Owner to the managed identity.
  2. Assign Key Vault Secrets User on the entire resource group only.
  3. Assign a suitable blob data reader to stbuild and Key Vault Secrets User to kvbuild, each at its own resource scope.
  4. Assign Storage Blob Data Reader on both storage account and Key Vault.

Explanation

Correct Answer

C:

The pipeline accesses two distinct Azure data services through Microsoft Entra authorization. A Storage Blob Data Reader assignment on the intended account supplies blob read operations, while Key Vault Secrets User on the intended RBAC-enabled vault supplies secret value retrieval. Keeping each grant on its own resource avoids a broad subscription or resource-group role that could reach unrelated data. The identity's token and network paths must also be correct, but neither service's role substitutes for the other's data permissions.

Incorrect Answers

A:

Owner on the subscription would provide extensive infrastructure and access-management authority, far beyond the pipeline's two read operations. It also does not automatically supply every service data-plane permission through OAuth. The safer solution is to grant each required data role on the specific storage account and vault instead of trusting a broad subscription role.

B:

Key Vault Secrets User supports secret value reading but does not permit reading Azure Blob Storage objects. A resource-group-wide grant could also cover other vaults in that group, exceeding the request. Use separate, resource-scoped roles: the storage blob data reader on stbuild and the secrets reader on kvbuild.

D:

Storage Blob Data Reader works with Azure Storage blob data actions, not Key Vault secret retrieval operations. Even if assigned at a broad scope, it does not become a Key Vault Secrets User role. The pipeline requires separate service-specific data permissions for each resource, with the vault secret read role assigned independently.

Question 112

A company runs separate production subscriptions for two regulated clients. Each deployment identity should manage only its corresponding client's subscription; neither should inherit rights over the other. What access pattern best enforces this?

  1. Assign one shared subscription Owner identity at the parent management group.
  2. Assign Reader to both identities on both subscriptions.
  3. Use the same global service principal with Owner in both subscriptions.
  4. Use distinct service principals or managed identities with separate subscription-scoped role grants.

Explanation

Correct Answer

D:

Separate principal identities make it easier to attribute and restrict deployment actions to the correct customer environment. Assign each identity only the resource-management role required on its own subscription, then verify there are no parent management-group, group membership, or additional grants spanning both environments. Azure RBAC's scope inheritance can otherwise grant unexpected cross-subscription rights. Separate subscriptions alone do not guarantee isolation if the same broadly privileged principal is reused or inherits rights from a common ancestor.

Incorrect Answers

A:

A common parent-management-group Owner assignment would grant both customer environments broad control and role-grant authority through inheritance. That directly violates the requirement that deployment identities stay within their own client boundary. Use independently scoped identities and review effective permissions across the hierarchy rather than broadening their common ancestor rights.

B:

Reader cannot perform the resource write operations needed for a deployment identity. It also gives each identity visibility into the other client's resources, despite a requirement for independent scope. Each deployment identity should receive only its required deployment rights on its own subscription, with no sibling or parent grants.

C:

The same principal could technically access both subscriptions, but that defeats the stated requirement for separate deployment identities without cross-environment permissions. Compromise or misuse of that identity could affect both regulated clients. Creating distinct principals with independent grants preserves clearer security and accountability boundaries.

Question 113

An Azure support team has 30 engineers in the Entra security group sg-ops. Every engineer should receive the same Reader access to resource group rg-reporting, and membership changes should not require new individual Azure grants. What should you do?

  1. Assign Contributor to sg-ops at subscription scope.
  2. Assign Reader individually to the current 30 engineers.
  3. Assign Reader to security group sg-ops at rg-reporting.
  4. Create a resource lock on rg-reporting instead of a role assignment.

Explanation

Correct Answer

C:

Azure RBAC can use a Microsoft Entra group as the assigned principal. Giving the group Reader on rg-reporting lets its members receive the group's read-only access to resources in that scope, without creating separate role assignments for every engineer. When membership changes, effective access follows the relevant group membership and token or authorization propagation behavior. The underlying RBAC grant stays at the resource-group scope, so it does not provide Reader across unrelated groups or subscriptions.

Incorrect Answers

A:

Contributor includes write permissions, and subscription scope covers every resource group under that subscription. Both the role and scope are much broader than the team's read-only need for rg-reporting. A group-based Reader assignment at the one resource group follows the intended privilege boundary and still supports dynamic membership changes.

B:

Individual Reader assignments would work for the engineers on today's list, but new members would need additional grants and leavers would need separate cleanup. That contradicts the stated goal of membership-driven authorization. One role assignment to the Entra security group centralizes the access mapping at the correct resource-group scope.

D:

Management locks constrain certain Azure Resource Manager operations but do not grant a group permission to view resources. Locking the group cannot substitute for Reader authorization. The question asks how to distribute read access based on Entra security-group membership, which is achieved with an Azure RBAC role assignment to that group.

Question 114

An Azure VM's system-assigned managed identity must read secret values from one Azure Key Vault using the RBAC authorization model. It must not enumerate secrets from other vaults or change the vault configuration. What should you assign?

  1. Key Vault Secrets Officer at subscription scope.
  2. Reader on the target subscription.
  3. Virtual Machine Contributor on the VM.
  4. Key Vault Secrets User to the VM's managed identity on the target vault.

Explanation

Correct Answer

D:

Key Vault Secrets User grants the ability to read the contents of secrets in a vault that uses the Azure RBAC permission model. Assigning it to the actual managed identity at the individual vault scope limits the authorization to that vault without adding management-plane configuration writes. The application must acquire an appropriate token as the managed identity and satisfy any network restrictions. A Microsoft Entra directory role or general VM resource role cannot replace Key Vault's service-specific data permission.

Incorrect Answers

A:

Secrets Officer includes operations to manage secret data, not only read existing values, and subscription scope could cover unrelated Key Vault resources. The VM needs read-only access to one vault. The narrower Secrets User role assigned directly on that vault prevents unnecessary secret writes and cross-vault exposure.

B:

Azure Reader permits viewing management-plane resource properties, not the sensitive contents of Key Vault secrets under Azure RBAC authorization. A subscription Reader assignment would broaden resource visibility while failing to supply the required secret read operation. Use the dedicated Key Vault Secrets User data role at the target vault scope.

C:

Virtual Machine Contributor gives Azure compute-management permissions, not Key Vault secret value DataActions. Having authority over a VM does not automatically authorize the workload's managed identity to read a separate vault. Assign the Key Vault Secrets User role to the identity on the specific vault rather than elevating VM administration rights.

Question 115

A principal is assigned subscription Owner, but an Azure resource operation is blocked by a system-protected deny assignment on a nested resource. Which conclusion is correct?

  1. Change the principal's Microsoft Entra display name and retry.
  2. Add Contributor on the resource to supersede the denial.
  3. The deny assignment can block the operation despite Owner; inspect the protected deny rule and its applicable scope.
  4. Owner always overrides every deny assignment in the subscription.

Explanation

Correct Answer

C:

Azure RBAC evaluates deny assignments separately from ordinary allow role assignments. An inherited Owner role does not override an applicable deny action that matches the attempted operation, and system-protected deny assignments are managed by Azure features rather than directly edited like normal grants. The administrator should inspect the deny assignment's actions, principals, exclusions, and inheritance settings, then remediate through the controlling Azure feature or supported workflow. Granting more ordinary allow roles will not negate an effective denial.

Incorrect Answers

A:

A user or service principal display name does not define Azure RBAC deny-assignment permissions. The denial evaluates the principal, actions, and scope in the authorization request. Changing presentation metadata leaves those controls unchanged, so it cannot resolve a policy-protected resource operation that has an effective deny assignment.

B:

Azure RBAC allow assignments are additive, but an applicable deny assignment is not removed by attaching another allow role to the same or narrower resource. Contributor also cannot create a privileged exception to a system-protected deny. The resource's operation remains blocked until the controlling mechanism is addressed through a supported path.

D:

Owner is a broad allow role, but Azure deny assignments are designed to block specified operations even when a principal has otherwise sufficient role grants. Ignoring the deny rule would lead to incorrect escalation attempts. The correct diagnostic is to examine the effective deny assignment and understand which Azure service created or protects it.

Question 116

A developer holds Contributor on existing resource group rg-app. The developer can deploy inside rg-app but receives AuthorizationFailed trying to create a second resource group rg-new. Why, and how can it be resolved?

  1. Change a resource lock on rg-app.
  2. Creating rg-new needs resource-group create permission at subscription scope or an authorized administrator to precreate it.
  3. Assign another Contributor role on rg-app.
  4. Assign Reader on rg-new before it exists.

Explanation

Correct Answer

B:

Azure resource groups are children of subscriptions. A Contributor assignment on existing rg-app grants rights only inside that group; it cannot authorize creation of a sibling resource group at the subscription parent scope. The administrator can provide a narrowly appropriate subscription-level resourceGroups/write permission, or create rg-new and grant the developer access there. This distinction separates creating the management container from deploying resources into a container that already exists.

Incorrect Answers

A:

A lock on the existing group can constrain modifications to its descendants, but it does not grant authorization to create a new sibling group. The error concerns lack of the relevant parent-scope write action, not a lock preventing changes in rg-app. The administrator must address the subscription resource-group creation permission or precreate the destination.

C:

Repeating the same Contributor assignment at rg-app adds no new subscription-level permissions. Azure RBAC inheritance flows downward from a scope, not laterally to new sibling resource groups. The failed request targets a new resource group under the subscription, so its create operation must be authorized at the parent scope.

D:

Reader does not include resource-group creation rights, and an RBAC assignment to a nonexistent target group cannot solve the parent-scope authorization requirement. The operation to create a new resource group is evaluated at the subscription boundary. The developer must use an authorized subscription-level creator or have the target group provisioned first.

Question 117

Two applications use separate containers in storage account stapps. App A must read container app-a; App B must read container app-b. Both apps have managed identities. What is the least-privileged RBAC design?

  1. Assign one shared managed identity Storage Blob Data Contributor on the account.
  2. Assign Reader on the two App Service resources only.
  3. Assign Storage Blob Data Reader to each application's managed identity only on its corresponding container.
  4. Assign Storage Blob Data Reader to both managed identities at storage-account scope.

Explanation

Correct Answer

C:

Container-scoped Storage Blob Data Reader assignments authorize the relevant managed identity to list and read blobs only in its application's container. Using separate principals prevents one workload from inheriting the other workload's permissions through a shared identity. Because both containers share a storage account, a storage-account-level grant would be broader than necessary. This design controls the Azure Storage data plane while leaving storage firewall, private networking, and application token acquisition to their own independent checks.

Incorrect Answers

A:

Sharing a principal obscures which application performed an operation, while Blob Data Contributor adds write and delete privileges beyond the read-only requirement. Account scope also includes both containers and any future ones. Independent managed identities with container-scoped Data Reader assignments better enforce workload and data isolation.

B:

The Azure Reader role on App Service resources concerns application management metadata, not authorization for a managed identity to read Azure Storage blobs. Even if both apps can inspect their own resource configuration, their calls to storage still need a matching data-plane role. Assign Blob Data Reader to each identity on its container.

D:

Storage-account scope would give each identity blob read access across both app-a and app-b containers, defeating the separation between applications. The same role is usable, but its parent scope causes overreach. Each managed identity should receive the reader role only at the container it serves.

Question 118

Management group mg-compliance contains subscriptions sub-audit-a, sub-audit-b, and sub-restricted. An external reviewer may inspect Azure resources in only the two audit subscriptions; sub-restricted must remain entirely outside the reviewer's Azure RBAC read access. The subscription hierarchy cannot be changed. Which Reader assignment strategy meets that boundary?

  1. Assign Reader once at mg-compliance because child subscriptions can override inherited access with a narrower Reader role.
  2. Assign Reader at the tenant root management group and put a CanNotDelete lock on sub-restricted.
  3. Assign the Microsoft Entra Directory Readers role and assume it provides resource Reader access on only approved subscriptions.
  4. Assign Reader separately at sub-audit-a and sub-audit-b, without assigning the reviewer a parent management-group Reader grant.

Explanation

Correct Answer

D:

Azure RBAC role assignments may be scoped to individual subscriptions. Separate Reader grants to the two approved subscriptions include their child resources but do not grant Reader on sibling sub-restricted when no ancestor grant applies.

Incorrect Answers

A:

A management-group Reader assignment is inherited by every descendant subscription, including sub-restricted. Adding a narrower Reader grant does not subtract the inherited permission because Azure RBAC allowances are additive.

B:

Tenant-root Reader would expose an even broader hierarchy, and a management lock cannot selectively revoke a user's read-only Azure RBAC rights. Locks limit management operations, not visibility assignments.

C:

Microsoft Entra Directory Readers governs identity-directory visibility, not Azure Resource Manager resource Reader access at the required subscription scopes.

Question 119

An engineer accidentally assigned Owner to an application identity at the tenant root management group for a temporary staging task. The identity should manage only one staging resource group. What is the correct remediation?

  1. Rename the managed identity and wait for permission propagation.
  2. Add Reader on the staging resource group and keep root Owner.
  3. Remove the root Owner grant and assign a narrowly appropriate role on the staging resource group.
  4. Move the staging resource group to another subscription but retain root Owner.

Explanation

Correct Answer

C:

A role assignment at the tenant root management group can inherit throughout the management hierarchy and authorize actions in many subscriptions. Removing that unintended Owner assignment eliminates its broad resource and role-grant permissions. The engineer can then assign a least-privilege management role at the specific staging resource group, and check other inherited or direct grants for residual access. Adding a weaker role at staging without removing root Owner would not reduce the identity's effective privileges.

Incorrect Answers

A:

Display names do not determine the scope or actions associated with an Azure RBAC assignment. Renaming the principal would not remove the inherited tenant-root Owner role, even after cache or token refresh. The faulty authorization grant must be explicitly revoked or changed and its effective impact reviewed.

B:

Reader at staging would be additive to the existing root Owner grant. It would not subtract inherited Owner permissions on staging or the wider tenant hierarchy. This fails to remediate the overprivileged assignment. The root grant must be removed, then the identity should receive only the role and scope justified by the staging work.

D:

Relocating a resource group would not reliably remove an identity's permissions inherited from tenant-root management-group scope, and could introduce unnecessary deployment changes. The problem is a broad authorization assignment, not resource geography. Remove the root Owner grant and place a narrower role on the approved staging scope.

Question 120

A service principal synchronizes metadata for three named storage accounts spread across different resource groups in a subscription. It may not manage any other storage accounts. How should its Azure RBAC permissions be scoped?

  1. Grant Owner on the management group containing the subscription.
  2. Create separate role assignments on each of the three named storage account resources.
  3. Assign the storage management role once at subscription scope.
  4. Assign the role at the parent resource groups of all three accounts.

Explanation

Correct Answer

B:

Azure RBAC can scope a principal's role directly to an individual resource. Three account-level assignments give the automation exactly the necessary reach even though the accounts are in different resource groups. This avoids granting the same role to other accounts in a common resource group or across the subscription. Choose the role definition based on whether the process reads management settings or actually edits them, then assess all effective inherited assignments for unexpected additional permissions.

Incorrect Answers

A:

Management-group Owner would confer extensive resource-control and access-administration rights across an entire hierarchy, far outside the three-account automation task. This dramatically overprivileges the service principal. Assigning only the needed role on the three named storage resources provides a narrower and more auditable security boundary.

C:

A subscription-scope storage role would inherit to other storage accounts in the subscription, not just the three approved endpoints. The automation is prohibited from affecting those unrelated accounts. Three resource-level grants preserve the exact selection without making the service principal an administrator across every storage account in that subscription.

D:

Resource-group-level grants can include other resources and storage accounts co-located with each target. Because the contract names only three particular accounts, group scopes may be broader than required. Assigning the role directly on each account avoids exposing sibling accounts in those groups.