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 14

Question 130

A managed identity has Storage Blob Data Contributor at the correct container scope, but its requests from an unapproved public network are rejected by the storage account firewall. What should you investigate?

  1. The storage network restrictions and approved connectivity path; RBAC data grants do not bypass the firewall.
  2. Assign Storage Blob Data Owner at subscription scope.
  3. Assign Owner to the identity on the storage account resource.
  4. Enable blob versioning on the storage account.

Explanation

Correct Answer

A:

Azure Storage evaluates network access controls independently from the caller's Microsoft Entra data-plane authorization. Even an identity with valid Blob Data Contributor permissions can fail when requests originate outside permitted network paths. Inspect storage account public network access, selected network and subnet rules, or the private endpoint and DNS configuration appropriate to the workload. Do not expand the identity's Azure RBAC role merely to overcome a firewall denial; doing so would increase privileges without fixing connectivity.

Incorrect Answers

B:

Data Owner grants more blob permissions and may include ownership and ACL actions, but it does not override storage account firewall restrictions. Subscription scope would also expose unrelated accounts. The current failure is linked to the calling network's eligibility, so the administrator must correct or use an approved network path rather than elevating data permissions.

C:

Resource Owner is a powerful ARM role, but the storage firewall still enforces its network rules on data requests. Broadening management access does not make a disallowed public client become an approved source. Investigate the account's network configuration and client origin while retaining the already adequate blob data role.

D:

Blob versioning records earlier versions of objects; it does not authorize traffic from denied networks or change firewall rules. A configuration that improves recovery of overwritten blobs cannot fix network-level access rejection. Use the approved virtual network, private endpoint, or carefully scoped firewall rule appropriate to the service's design.

Question 131

A service principal received a new Reader role assignment a minute ago, but its previously issued token and client still show AuthorizationFailed for the intended resource. What is the appropriate troubleshooting approach?

  1. Confirm the principal and assignment scope, allow for RBAC propagation, and refresh credentials or tokens where relevant.
  2. Change the principal's display name and retry with its old token.
  3. Delete and recreate the Azure subscription.
  4. Immediately give the service principal subscription Owner.

Explanation

Correct Answer

A:

Azure RBAC changes can take time to propagate through authorization caches and clients. Before adding more roles, verify that the service principal's object ID matches the role assignment, the Reader role covers the intended resource, and no applicable deny blocks the action. Then obtain fresh authentication credentials or a token where the client caches authorization information, and retry after reasonable propagation. A duplicate broad role assignment is not a substitute for validating identity, scope, and eventual consistency.

Incorrect Answers

B:

Display names are not the security identifier used to evaluate a service principal's Azure RBAC grant. Keeping a previously issued token may also preserve stale client-side authorization behavior. The correct checks concern the immutable principal object ID, assignment scope, propagation, and any relevant token refresh—not cosmetic identity labels.

C:

A subscription's lifecycle is unrelated to a recently assigned Reader role taking effect for a service principal. Recreating the subscription would be destructive and would not diagnose authorization caching. Verify the identity and role assignment and allow appropriate propagation before making any broader environmental change.

D:

Owner would greatly expand resource and access-management privileges without demonstrating that the original Reader assignment was wrong. A short delay after a new grant may involve caching or propagation, not missing write permissions. Check the principal, scope, token, and effective access first rather than escalating to a broad administrative role.

Question 132

A Microsoft Entra Global Administrator signs into a new Azure subscription and discovers they are not automatically its Owner. Which explanation is correct?

  1. Any Global Administrator automatically receives Storage Blob Data Owner on every account.
  2. Entra directory roles and Azure resource RBAC roles are separate; subscription access needs an appropriate Azure role assignment or authorized elevation workflow.
  3. Global Administrator is identical to Azure subscription Owner.
  4. Assigning Reader at one resource group makes the administrator subscription Owner.

Explanation

Correct Answer

B:

Global Administrator is a powerful Microsoft Entra directory role, but it does not automatically make the holder Owner of every Azure subscription. Azure Resource Manager permissions are governed by Azure RBAC role assignments and their scopes. An eligible Global Administrator may use the documented elevated-access process to gain an appropriate access-management role when authorized, but this is an explicit security action rather than an automatic Owner grant. The organization should use least-privilege subscription assignments and record any elevation.

Incorrect Answers

A:

Blob data-plane roles are separate from both Microsoft Entra directory administration and general Azure management roles. Directory-wide Global Administrator does not automatically confer access to customer blobs through Microsoft Entra OAuth. Appropriate Azure RBAC data-role assignments and network restrictions govern that separate kind of resource access.

C:

The identity directory and Azure resource management planes use different authorization models. A Global Administrator can administer many tenant identity settings without necessarily holding Owner at a given subscription. Conflating these roles would incorrectly assume automatic resource control; the principal needs applicable Azure RBAC rights or a supported authorized elevation process.

D:

Reader grants read-only resource visibility within its assigned scope and descendants. It does not elevate the principal to Owner, allow access-grant management, or expand authority to a parent subscription. Azure RBAC is additive by explicit role assignments; a resource-group Reader cannot be interpreted as subscription-wide ownership.

Question 133

A partner's B2B guest account successfully authenticates to the tenant but receives AuthorizationFailed when attempting to list resources in rg-project. The guest needs read-only project visibility. What is missing?

  1. A new invitation to the same guest email without any resource role.
  2. An appropriate Azure RBAC Reader assignment to the guest on rg-project.
  3. A subscription Owner role for the guest.
  4. Key Vault Secrets User on the subscription.

Explanation

Correct Answer

B:

Successful Microsoft Entra B2B authentication proves that the partner can establish an identity in the resource tenant; it does not automatically authorize Azure Resource Manager operations. Assigning Reader to the guest principal on rg-project provides read-only access within the required resource-group scope. The guest may still be subject to tenant policy or conditional access, but the specific error concerns resource authorization. Do not give a directory-wide privileged role when the business requirement is only scoped project visibility.

Incorrect Answers

A:

Repeating a B2B invitation does not create Azure resource RBAC permissions. The guest already signs in successfully, so the authentication path works. The missing element is an authorization grant on the project resource group. Add the appropriate Azure Reader role rather than issuing a redundant identity invitation.

C:

Subscription Owner would grant broad resource-management and access-assignment capabilities to an external collaborator. The guest needs only to view resources inside one project resource group. A Reader assignment at rg-project provides the required Azure RBAC management visibility without exposing unrelated subscription resources or administrative powers.

D:

Key Vault Secrets User is a data role for reading secret values from eligible Key Vaults. It does not authorize listing general Azure Resource Manager resources inside rg-project. The guest needs read-only management-plane visibility to the resource group, making Reader on that resource group the correct role and scope.

Question 134

An analyst holds Storage Blob Data Reader on a storage account with an Azure ABAC role assignment condition requiring blob index tag Project=Blue. The analyst cannot read a blob tagged Project=Red. Why?

  1. Changing the storage account's redundancy to GRS will permit the read.
  2. The analyst must be given subscription Owner for tag conditions to work.
  3. The role's condition does not match the blob's attributes for that read request.
  4. Storage Blob Data Reader can never be restricted by tag attributes.

Explanation

Correct Answer

C:

Azure ABAC conditions narrow certain Azure RBAC role assignment permissions by evaluating resource, request, environment, or principal attributes for supported data actions. The assigned Blob Data Reader may nominally include blob reads, but its condition permits the specific operation only when the required Project tag matches. A Red-tagged blob therefore fails that conditional allow, unless another applicable permission source independently authorizes the request. The administrator should inspect the actual condition and blob index tags rather than assuming the role name alone guarantees access.

Incorrect Answers

A:

Storage redundancy controls durability and replication of data across copies or regions; it does not alter Azure ABAC authorization conditions. A Red-tagged blob remains outside a Project=Blue conditional grant regardless of whether the account is locally or geographically replicated. Correct the intended tag or role condition only through an authorized access-control change.

B:

Owner is a broad management and access role, not a requirement for a caller to satisfy a blob ABAC read condition. Giving subscription Owner to the analyst would be an inappropriate privilege escalation. The issue is the mismatch between the blob's Project tag and the condition on the existing data role assignment.

D:

Azure supports attribute-based conditions on supported blob data-role assignments, including restrictions based on blob index tag values. The role name alone does not fully describe the effective permission when a condition is attached. The Red blob does not satisfy Project=Blue, which explains why this conditional grant cannot authorize its read.

Question 135

A user has Reader inherited at resource-group scope and Contributor assigned directly on one VM within that group. What effective operations can the user perform on the VM and its siblings?

  1. The user becomes Owner of the resource group because two roles were combined.
  2. Use Contributor's permitted management actions on that VM while retaining only Reader access to sibling resources, barring other grants.
  3. The inherited Reader role cancels Contributor on the VM.
  4. Contributor on the VM automatically expands to every sibling resource in the group.

Explanation

Correct Answer

B:

Role assignments in Azure are additive within their individual scopes. The VM-specific Contributor grant supplies permitted resource-management actions on that VM, while Reader inherited from the resource group allows read-only visibility across the other resources. The Contributor grant does not propagate sideways to sibling VMs or upward to the group. Other deny assignments, locks, policy conditions, and separate role grants can affect actual results, so this interpretation assumes no additional relevant permissions.

Incorrect Answers

A:

Combining Reader and Contributor assignments does not automatically create an Owner grant or add roleAssignments/write permission. The user's effective operations are the union of the actual granted actions at each scope. They remain scoped Contributor on the VM and read-only on sibling resources, not a resource-group access administrator.

C:

Azure RBAC does not use a more general read-only grant to override a narrower positive Contributor role assignment. The two allows combine where their scopes overlap. The user can perform the actions granted by Contributor on the one VM, while the Reader grant remains effective for visibility throughout the group.

D:

An Azure role assignment on an individual VM does not inherit to sibling resources at the same or higher management scope. Contributor's permitted writes apply at its own VM resource scope. Other resources in the group receive only the Reader privileges inherited from the group unless a separate assignment grants additional actions.

Question 136

A user has Storage Blob Data Reader at container scope and can download blobs using a Microsoft Entra OAuth SDK, but the Azure portal cannot navigate to the storage account's data browse interface. The user has no ARM permissions. What should be added without increasing data write access?

  1. Key Vault Secrets User on the application's key vault.
  2. Owner of the Azure subscription to guarantee all account and data access.
  3. Storage Blob Data Contributor on the whole storage account.
  4. Reader on the storage account, retaining the container-scoped Blob Data Reader.

Explanation

Correct Answer

D:

Azure portal navigation to a storage account often requires Azure Resource Manager Reader visibility in addition to the data-plane Blob Data Reader already held by the user. The existing container role proves blob OAuth read permission works through the SDK. Adding account-scoped Reader supplies the missing control-plane visibility without permitting blob writes or increasing the scope of data access. This inverts the usual troubleshooting case in which ARM Reader exists but blob DataActions are missing.

Incorrect Answers

A:

Key Vault Secrets User grants permissions for vault secret values under the suitable access model; it does not supply Azure Resource Manager visibility for a storage account in the portal. The known working OAuth SDK path indicates a control-plane browsing issue, not missing secret permissions. Use storage-account Reader separately.

B:

Subscription Owner is far broader than required for portal navigation and includes significant resource and role-management privileges. The user already has exactly the necessary blob read DataActions and needs only the account's ARM metadata view. Assigning Owner would ignore the scenario's read-only, least-privilege constraint and could create avoidable exposure.

C:

The SDK already downloads blobs successfully using the existing container-scoped Data Reader role. Adding Data Contributor would grant write and delete rights and possibly extend them to other containers, violating least privilege while failing to target the missing portal resource-browse visibility. A management-plane Reader grant is the relevant addition.

Question 137

A VM administrator has Azure RBAC Owner on a resource, but attempts to update its ARM configuration fail after a ReadOnly lock was applied to the parent resource group. Which rule explains the failure?

  1. The inherited management lock blocks applicable control-plane writes regardless of the user's Owner role.
  2. Subscription Owner always bypasses all ReadOnly locks.
  3. Changing a blob's access tier will remove the parent's lock.
  4. Reader on the VM should be replaced with Contributor.

Explanation

Correct Answer

A:

Azure management locks are designed to restrict resource operations across all users and roles, including Owner. A ReadOnly lock applied to a resource group is inherited by descendant resources and blocks applicable Azure Resource Manager updates, even when RBAC allows those writes. The administrator should inspect the most restrictive lock in the hierarchy and obtain authorized lock-management assistance for an approved change. This is distinct from reducing the user's role assignment or from restricting data-plane actions inside a service.

Incorrect Answers

B:

Azure management locks override normal management-plane permissions, so Owner cannot simply ignore an inherited ReadOnly restriction. A successful RBAC allow check does not guarantee the update succeeds when a lock blocks the operation. An authorized lock administrator must address the lock through a controlled workflow before the resource is changed.

C:

Blob access tier is a data management setting unrelated to management locks on a parent resource group. Altering storage tiers cannot remove or override a ReadOnly lock controlling a VM's ARM update. The correct remedy is to inspect the inherited lock and follow the organization's approved lock change process.

D:

The principal already has Owner, which is more privileged than Contributor for ordinary resource-management operations. The authorization failure results from a ReadOnly lock inherited from the parent group, not an insufficient allow role. Adding or replacing Azure RBAC grants will not remove the lock's restriction on management writes.

Question 138

An admin removes a user's Reader membership from one Entra security group, but the user can still view the Azure resource group. What should be investigated before claiming revocation has failed?

  1. Delete and recreate the Azure resource group.
  2. Remove the storage account's encryption key.
  3. Other direct and inherited RBAC grants, remaining group memberships, and access propagation or cached tokens.
  4. Add a new Reader role directly to the user.

Explanation

Correct Answer

C:

Azure RBAC permissions may come from multiple direct, group, and ancestor assignments. Removing one group membership does not revoke permissions supplied by another group or a direct role assignment. The administrator should inspect the principal's effective access across management group, subscription, and resource-group scopes, and allow for documented membership or token propagation where relevant. Confirm which principal is making the request and whether a separate valid grant explains the retained read access rather than assuming a single group controlled everything.

Incorrect Answers

A:

Resource-group deletion is destructive and unrelated to identifying why a user retains authorization. The access could be inherited from a subscription role or a different security group. Deleting workloads would not be a responsible way to revoke or diagnose permissions; inspect the Azure RBAC effective access graph instead.

B:

Changing encryption-key availability affects storage data protection and service functionality, not general Azure Resource Manager Reader authorization for a resource group. It risks an outage while leaving the underlying access grants unexplained. The appropriate checks concern RBAC principals, scopes, memberships, and propagation rather than data encryption settings.

D:

Creating a direct Reader assignment would preserve or expand the very read access the administrator is attempting to revoke. It does nothing to identify the source of remaining privileges. The correct investigation is to enumerate all applicable role and group assignments and evaluate whether the membership change has propagated.

Question 139

A custom Azure role contains Microsoft.Compute/virtualMachines/read but no VM write or start actions. No other relevant grants exist. Can a user with that role restart an Azure VM?

  1. Yes, because read permission includes all non-destructive VM operations.
  2. Yes, because the role is custom rather than built in.
  3. Yes, if the VM belongs to a resource group with a Delete lock.
  4. No; the role's read action does not authorize the VM restart operation.

Explanation

Correct Answer

D:

Azure custom role definitions specify permitted management actions, and the caller can only perform an operation when an applicable role allows the required action. Microsoft.Compute/virtualMachines/read supports viewing VM properties but not starting or restarting the resource. Under the stated assumption of no additional grants, the principal lacks the necessary action. An authorized administrator must update the custom role or assign an appropriate VM management role, after reviewing the exact required operation and its scope.

Incorrect Answers

A:

Azure RBAC does not infer arbitrary action permissions from a resource read permission. Restarting a VM is a management action, not merely retrieving resource properties. The custom role deliberately contains only the read operation, so the user cannot assume restart rights without a role definition that includes the required action.

B:

Custom roles are not automatically privileged beyond their explicit allowed Actions and DataActions. Their actual permissions depend on the operations included in the definition and the assignment's scope. A custom role containing only VM read does not confer restart merely because an administrator authored the role.

C:

A management Delete lock restricts applicable deletion operations and does not add missing Azure RBAC permissions. It cannot transform a read-only custom role into a VM restart role. The caller must possess the management action necessary for the restart, regardless of whether a Delete lock exists on the resource.

Question 140

A deployment identity has Owner at subscription scope, but a new VM is rejected with RequestDisallowedByPolicy for an unapproved size. What should the team do first?

  1. Inspect the applicable Azure Policy assignment and its allowed-size parameters, then use an approved VM size or authorized exemption.
  2. Disable Microsoft Entra authentication for the deployment identity.
  3. Add Storage Blob Data Owner on the resource group.
  4. Assign a second Owner role directly to the VM.

Explanation

Correct Answer

A:

Azure Policy with a deny effect can reject resource create or update requests that violate assigned governance requirements, even if the deploying principal has broad Azure RBAC Owner rights. The error identifies a policy decision rather than a missing resource-management permission. Inspect the effective policy at subscription and management-group scopes, confirm the allowed VM SKUs, and correct the deployment or request a documented exception where permitted. Adding more RBAC roles will not override a valid deny policy.

Incorrect Answers

B:

Changing authentication mechanisms cannot make a policy-prohibited VM size compliant with Azure resource governance. The deployment request is reaching Azure Policy and being rejected by its deny condition. The fix concerns the policy parameters, selected SKU, or a properly authorized exemption, not a reduction in identity authentication controls.

C:

Storage Blob Data Owner governs blob-data operations and has no bearing on whether an Azure Policy permits a VM size. Granting it would expose unrelated storage data privileges without resolving the deployment denial. The administrator should examine the applicable policy and choose an approved VM SKU instead.

D:

Adding another Owner allow assignment does not neutralize Azure Policy's deny evaluation, and a rejected VM may not exist as an assignable resource. The identity already has extensive management rights. The deployment is blocked because the selected SKU violates governance settings, so the team must address the policy requirement or approved exception process.