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 13

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.

Question 121

A user has Reader inherited from management group mg-core and Contributor assigned directly at resource group rg-analytics. What is the user's effective Azure resource management access inside rg-analytics?

  1. Contributor operations within rg-analytics, plus inherited read visibility elsewhere under mg-core.
  2. Owner within rg-analytics, including unrestricted role assignment management.
  3. Only Reader throughout mg-core, because the parent role takes priority.
  4. Contributor on every subscription beneath mg-core.

Explanation

Correct Answer

A:

Azure RBAC allow assignments combine additively within their applicable scopes. Contributor on rg-analytics supplies the resource management writes allowed by that role for resources inside the group, while the inherited management-group Reader grant continues to provide read visibility across the broader hierarchy. The narrower Contributor grant does not elevate the user in sibling resource groups. Applicable deny assignments, policy restrictions, locks, and role conditions can still block particular operations despite the listed grants.

Incorrect Answers

B:

Contributor and Reader grants do not automatically combine into Owner. Contributor ordinarily excludes managing Azure role assignments, and inherited Reader supplies only read operations. The user can perform Contributor's resource writes in rg-analytics but cannot assume access-delegation rights without an additional eligible authorization role.

C:

Azure RBAC does not apply a rule in which a higher-level Reader role overrides a descendant Contributor assignment. The user receives both allow roles wherever their scopes apply. On rg-analytics, the scoped Contributor grants management writes; outside that group, the inherited Reader continues to provide read access without corresponding writes.

D:

The Contributor assignment is attached only to rg-analytics; it does not inherit upward into the management group or sideways into other subscriptions. The broader inherited Reader grants visibility to more resources but does not carry Contributor writes with it. Scope determines where each role's actions apply, not where the principal happens to sign in.

Question 122

A data analyst has Contributor on a storage account for management-plane settings and Storage Blob Data Reader on one of its containers. The analyst authenticates with OAuth to read blobs. Which interpretation is correct?

  1. Blob read access comes from the container Data Reader role; the account Contributor role manages ARM resources.
  2. The container-scoped Blob Data Reader grants data access to every storage account in the subscription.
  3. Contributor on the account automatically provides OAuth write and delete access to all blobs.
  4. The user has neither management nor blob read access because two roles cannot be combined.

Explanation

Correct Answer

A:

Azure separates management actions in the control plane from data actions for blob content. Storage Blob Data Reader supplies the OAuth read operation on the specific container, while Contributor on the account permits many management-plane configuration operations without automatically giving the principal blob DataActions. The scopes and action types must be considered together. The role combination does not imply blob write permission, and any storage network restrictions remain independent from both role grants.

Incorrect Answers

B:

An Azure role assignment on one container inherits only to relevant descendants of that container, not to sibling containers or other storage accounts. The data reader permits the targeted container reads and does not expand through the subscription. The principal's management-plane Contributor grant also does not transform the data role into a subscription-wide assignment.

C:

The generic Contributor role is a broad ARM resource-management role, not automatically a storage blob data contributor role for Microsoft Entra OAuth requests. Its management capabilities may expose other authorization paths, including access-key operations, but those are different from blob DataActions. The analyst's OAuth data access is governed by the separately assigned container Blob Data Reader.

D:

Azure RBAC supports multiple role assignments for one principal, including assignments at different scopes and permission planes. The effective allow rights are evaluated together, subject to conditions and denies. In this case the principal has management rights on the account and data read rights on the container; the role grants are not mutually exclusive.

Question 123

An engineer is Contributor on resource group rg-app but receives an authorization failure when attempting to assign Reader to a teammate. What is the most accurate reason?

  1. Resource groups cannot be used as scopes for Azure role assignments.
  2. Contributor's roleAssignments/write capability activates only after 24 hours.
  3. Contributor does not include roleAssignments/write; an authorized access administrator must make the grant.
  4. The teammate must first receive Storage Blob Data Reader.

Explanation

Correct Answer

C:

Contributor is intended for managing Azure resources but excludes the management operation for granting Azure RBAC roles. Creating Reader access for another principal invokes Microsoft.Authorization/roleAssignments/write, which requires a role such as Role Based Access Control Administrator, User Access Administrator, or Owner at an applicable scope. The engineer's ability to deploy applications does not imply access-delegation authority. An appropriate delegate can perform the requested role assignment without broadening the engineer's infrastructure permissions.

Incorrect Answers

A:

Resource groups are one of Azure RBAC's supported assignment scopes, along with management groups, subscriptions, and individual resources. The target scope is therefore valid. The failure arises from the caller's missing role-assignment write permission, not an inherent limitation preventing grants at resource-group scope.

B:

Contributor does not acquire excluded access-management actions merely by waiting for propagation. Its built-in permissions deliberately omit the authorization writes required to create role assignments. This is a role-definition issue, not a delay after assignment. A separately authorized access administrator must grant the teammate Reader at the appropriate scope.

D:

The requested access is Azure Reader on a resource group, not blob content authorization. Giving the teammate a storage data role would not authorize the engineer to create a resource-group role assignment. The action is blocked because the engineer's own Contributor role lacks roleAssignments/write, which a proper access-admin principal must exercise.

Question 124

A user can restart an Azure VM even though the VM's Access control (IAM) page lists no direct assignment to that user. Which investigation most directly explains the effective grant?

  1. Create a new direct Owner assignment before investigating.
  2. Check only whether the user is a local operating-system administrator.
  3. Inspect role assignments inherited from the resource group, subscription, and management group, including group principals.
  4. Assume the VM is publicly accessible and no RBAC is required.

Explanation

Correct Answer

C:

Azure RBAC permissions may arise from ancestor scopes or from role assignments to Microsoft Entra groups containing the user. A VM's direct assignment list does not by itself describe every applicable authorization path. Check inherited role assignments at the resource group, subscription, and management-group levels, then examine the relevant principal and its group memberships. A scoped Virtual Machine Contributor or broader management grant can authorize the restart even without a direct user-to-VM assignment.

Incorrect Answers

A:

The user already has the ability to restart the VM, so assigning Owner would expand privileges without identifying the existing authorization source. Owner also allows broad resource management and access delegation. The correct diagnostic is to enumerate inherited and group-based grants before making any potentially unnecessary role changes.

B:

Local guest OS administration and Azure control-plane VM management are different security boundaries. A local administrator account may sign in to the guest but does not inherently receive Microsoft.Compute/virtualMachines/restart/action through Azure RBAC. The user could hold the restart permission through a parent or group role, so inspect effective Azure resource access.

D:

Public network reachability does not confer permission to perform an Azure Resource Manager VM restart action. Restarting an Azure VM resource still requires an authorized management operation. The missing direct grant should prompt investigation of inherited roles and group assignments, not an assumption that network exposure overrides Azure RBAC.

Question 125

Group sg-ops has Contributor assigned on resource group rg-ops. A new engineer joined sg-ops but has no personal role assignment. How can the engineer receive Azure resource access?

  1. The engineer automatically becomes subscription Owner when added to sg-ops.
  2. Azure role assignments apply only to users, never to groups.
  3. Through the group's Contributor role assignment, subject to effective group membership and propagation.
  4. The engineer must create a new subscription to activate group access.

Explanation

Correct Answer

C:

Azure RBAC permits role assignments to Microsoft Entra security groups, and their members can receive the relevant Azure resource permissions through that group. The engineer does not need an individual assignment if the authenticated principal is an effective member of sg-ops. The inherited group grant applies to rg-ops and its descendants, not to unrelated resource groups. Allow for membership and access-token propagation and verify that no deny or other applicable restriction prevents the requested operation.

Incorrect Answers

A:

The group is assigned Contributor at one resource-group scope, not Owner at subscription scope. Group membership carries the permissions of the actual assignment and its inheritance boundary. It does not upgrade Contributor into Owner or expand the role to every resource group in the subscription.

B:

Azure RBAC supports users, Microsoft Entra groups, service principals, and managed identities as principals for role assignments. Group assignment is a standard method of centralizing permissions as staff membership changes. The engineer can gain the group's role without a separate direct grant, assuming the membership and authorization evaluation are effective.

D:

Azure RBAC group membership is evaluated for the existing resource hierarchy; creating another subscription would not activate or modify a role on rg-ops. If access does not appear immediately, the administrator should verify the engineer's group membership and allow for documented propagation rather than reorganizing subscriptions.

Question 126

A subscription inherits governance from management group `mg-core`. An operator is ELIGIBLE for the Reader role on `mg-core` through Microsoft Entra Privileged Identity Management; there is no active Reader assignment, no other access grant and no deny assignment. The resource group's Check access panel shows the inherited eligible role, but the operator cannot open its VM inventory. The tenant has the required PIM licensing and approval workflow. Which step explains and resolves the missing access?

  1. Treat an eligible management-group Reader role as already active on all child resource groups; retry without initiating PIM activation.
  2. Add the operator to the guest OS Administrators group on the VM, assuming Azure control-plane IAM is managed inside Windows.
  3. Create a new resource group with the same name and move the VM there, because the inherited eligible assignment prevents existing resources from being listed.
  4. Activate the eligible Azure resource Reader role through PIM, satisfy any approval or authentication requirements, and verify the temporary active assignment at the inherited or approved reduced scope.

Explanation

Correct Answer

D:

Microsoft documents that PIM eligibility requires a supported activation request; activation temporarily makes the Azure role active, potentially after MFA or approval. The management-group role can be activated at its permitted inherited scope or a supported reduced scope, then effective resource access can be rechecked.

Incorrect Answers

A:

Eligibility records permission that can be activated; it is not an active Azure RBAC grant. Until PIM issues the time-limited active role assignment, the user's VM-inventory request has no effective Reader authorization. Merely retrying cannot change that state.

B:

Guest-operating-system administrator membership controls management inside a VM, not Azure Resource Manager listing and reading the VM resource in the portal. The failure occurs before any guest OS session and is governed by Azure RBAC.

C:

Creating another resource group does not activate the user's PIM eligibility. The management-group eligibility concerns the existing hierarchy and must be activated before Azure resource operations are authorized; moving VMs would add disruption without a permission fix.

Question 127

An automation identity has a custom Azure role `VM-Ops` assigned to resource group `rg-prod`. The role allows `Microsoft.Compute/virtualMachines/*` but lists `Microsoft.Compute/virtualMachines/delete` under `NotActions`. The identity also has a separate Contributor role assignment at the same resource group. An audit shows it can still delete VM `vm-prod`. The custom role is not to be changed. Which action actually removes the deletion permission?

  1. Remove or narrow the separate Contributor assignment so no remaining applicable role grants the VM delete action; retain the custom role with its `NotActions` exclusion.
  2. Add `Microsoft.Compute/virtualMachines/delete` to `NotActions` a second time; the duplicated entry becomes an explicit deny across all role grants.
  3. Assign Reader directly on `vm-prod`; a narrower-scope read-only role automatically overrides Contributor at the resource group.
  4. Remove `Microsoft.Compute/virtualMachines/delete` from the custom role's `DataActions` list while leaving the Contributor grant unchanged.

Explanation

Correct Answer

A:

Azure RBAC grants effective actions across all applicable role assignments. `NotActions` excludes the delete action from the `VM-Ops` role only; Contributor independently permits VM deletion. Removing or properly narrowing that separate Contributor grant removes the remaining delete permission while retaining the intended custom role.

Incorrect Answers

B:

`NotActions` is not a deny assignment, and repeating an exclusion does not transform it into one. The independent Contributor role still includes the VM delete management action, so this edit does not remove effective deletion rights.

C:

Azure RBAC allow grants are additive: a direct Reader grant on the VM does not cancel Contributor inherited from `rg-prod`. The identity can still perform the delete operation through the broader Contributor assignment.

D:

VM deletion is a Resource Manager management-plane action, not a data-plane `DataActions` operation. Editing the unrelated `DataActions` field of a custom role cannot revoke a delete permission already granted by the separate Contributor assignment.

Question 128

A deployment stack created a system-protected deny assignment for `*/delete` on a protected resource. Its Principals field contains the system-defined All Principals GUID, but the explicit ExcludePrincipals list contains the object ID of a break-glass administrator. That administrator also holds Azure Owner at the resource scope, and there are no other deny assignments or locks. What is the authorization outcome for that administrator’s delete action?

  1. The administrator is excluded from this deny assignment, so it does not block their delete action; the existing Owner role can authorize the deletion in the stated absence of other blockers.
  2. The All Principals entry always overrides ExcludePrincipals, so even explicitly excluded administrators are unconditionally denied.
  3. Assign the administrator Reader on the protected resource to negate the wildcard delete restriction without changing the deny assignment.
  4. Edit the system-protected deny assignment directly to remove its ExcludePrincipals entry; this grants the administrator deletion rights.

Explanation

Correct Answer

A:

An explicit ExcludePrincipals object ID exempts that identity from this otherwise broad deny assignment. With Owner granting the needed delete operation and no other lock or deny, this deny record no longer blocks the action.

Incorrect Answers

B:

Microsoft documents the All Principals system-defined principal combined with ExcludePrincipals precisely to exclude selected identities. All Principals does not erase that explicit exception.

C:

Azure RBAC role grants are additive and Reader does not remove the deny assignment. The preexisting Owner rights and the deny exclusion, not a narrower Reader role, govern this case.

D:

Azure manages and protects deny assignments; they cannot be directly edited to grant ad hoc access. Removing an exclusion would also make the administrator subject to the denial, the opposite of the proposed result.

Question 129

A user has Reader on a storage account resource and can display its properties in the Azure portal, but an application using that user's Entra token cannot download blobs. What permission is missing?

  1. Role Based Access Control Administrator at the subscription scope.
  2. Another generic Reader assignment on the same account.
  3. A suitable blob data role such as Storage Blob Data Reader on the requested container or account.
  4. Virtual Machine Contributor on the application host VM.

Explanation

Correct Answer

C:

Azure Reader provides control-plane visibility to storage account properties but does not include the blob DataActions required for OAuth data requests. Assigning Storage Blob Data Reader to the correct Microsoft Entra principal at the relevant container or account supplies the missing blob read operation. The portal's resource listing and the application's content download are separate permission checks. The storage firewall and any applicable role conditions must also permit the request, so data roles do not bypass independent network restrictions.

Incorrect Answers

A:

RBAC Administrator can manage access assignments where permitted but does not inherently provide the data-plane permission to download blob contents. It may be able to assign the required role, yet the application principal still needs Storage Blob Data Reader for OAuth reads. Granting broad assignment administration to solve a content read would be unnecessary and risky.

B:

Adding a duplicate ARM Reader assignment does not introduce blob data actions. It would preserve the ability to view management settings but leave OAuth blob-content authorization unresolved. The user needs a storage-specific data role, not additional copies of the control-plane Reader role that is already effective.

D:

Virtual Machine Contributor controls the compute resource, including supported VM management actions, but not the blob data permission enforced by Azure Storage. The host's resource role does not determine which blobs an Entra token can read. Assign a suitable storage blob data role to the actual application caller instead.

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.