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 11

Question 100

Two Azure subscriptions belong to management group mg-sales. The same internal audit service must read resource settings in both subscriptions and in future subscriptions added to mg-sales, but cannot modify anything. Where should Reader be assigned?

  1. As a Microsoft Entra Directory Readers role.
  2. On just one of the two subscriptions.
  3. At the tenant's root management group.
  4. At the mg-sales management group.

Explanation

Correct Answer

D:

Azure RBAC assignments at a management-group scope are inherited by its descendant subscriptions and resource scopes. Assigning Reader to the audit principal on mg-sales gives consistent read-only access to both existing subscriptions and subsequent subscriptions moved under that hierarchy. It does not grant general write privileges. This placement is justified because the requirement explicitly covers the full hierarchy and future descendants; otherwise, separate subscription-level grants would usually be less expansive.

Incorrect Answers

A:

Directory Readers concerns Microsoft Entra identity objects, not the Azure resource configurations in the two subscriptions. It also does not define an RBAC assignment scope across resource management groups. The audit service needs Azure Resource Manager Reader at the mg-sales management-group scope to inspect the specified resources.

B:

A Reader grant at a single subscription does not cross into a sibling subscription. It would miss both the other current subscription and new subscriptions added to the management group. The audit service has a justified organization-unit-wide requirement, so mg-sales is the appropriate common ancestor scope for one inherited assignment.

C:

Tenant-root management-group Reader would inherit into far more subscriptions than those owned by sales. It could expose unrelated business units and fail the explicit boundary at mg-sales. Assigning at the nearest management group containing the intended subscriptions satisfies future inheritance without extending the audit service across the whole tenant.

Question 101

A third-party vendor may manage only App Service app app-orders-prod. The app shares resource group rg-apps with other web apps, and the vendor must not alter those. What is the narrowest useful assignment?

  1. Website Contributor assigned to rg-apps.
  2. Contributor on the subscription containing rg-apps.
  3. Website Contributor assigned directly to app-orders-prod.
  4. Reader assigned directly to app-orders-prod.

Explanation

Correct Answer

C:

Website Contributor is a web-resource management role appropriate for App Service application administration. Assigning it on the individual app resource limits its effect to that web app rather than granting inherited permissions over every sibling app in rg-apps. The engineer should check whether the operations also affect shared App Service plan or other dependent resources, which may require separate authorized actions. The case explicitly forbids vendor control of sibling applications, so scope is crucial.

Incorrect Answers

A:

Resource-group-scoped Website Contributor would inherit to all web apps and other eligible web resources inside the group. Because app-orders-prod shares rg-apps with unrelated applications, this would expand the vendor's authorized administration beyond its contract. The same role assigned to the one app is narrower and matches the stated access boundary.

B:

Subscription Contributor provides broad resource-management permissions across resource groups and service families, not just the assigned web app. It would let the vendor make modifications far outside its permitted application. The request calls for a web-specific role applied to the individual app rather than broad subscription-level infrastructure rights.

D:

Reader at the app would correctly restrict visibility to that resource, but would not permit required App Service configuration and management writes. The vendor needs to manage rather than merely inspect the app. Website Contributor supplies the relevant web-resource operations while preserving the narrow scope.

Question 102

An external auditor is authorized to review the configuration of every Azure resource in subscription sub-audit, including newly deployed resources. They must not change resources. Which Reader assignment meets that requirement?

  1. Assign Reader at the tenant root management group.
  2. Assign Contributor on subscription sub-audit.
  3. Assign Reader on subscription sub-audit.
  4. Assign Reader only on the currently listed VMs.

Explanation

Correct Answer

C:

Reader at the subscription level inherits to resource groups and resources throughout that subscription, including resources deployed after the assignment. It permits observing ARM configuration without general resource-management write actions. Because the auditor has been expressly authorized across the entire subscription, the broader scope is not unnecessary in this case. The grant does not automatically apply to sibling subscriptions or provide all data-plane access to customer content, which remains separately controlled.

Incorrect Answers

A:

Root-management-group Reader would include resources across multiple subscriptions rather than only sub-audit. The auditor's authorization is specifically subscription-bound, so root-scope visibility is excessive. Grant Reader on the named subscription to preserve the data-separation boundary while covering all of its descendants.

B:

Contributor can create and alter most Azure resources within its scope, which is incompatible with a read-only external audit. The scope would cover the intended inventory, but the role definition is far too powerful. Subscription Reader provides visibility without routine management write capabilities.

D:

VM-level Reader assignments would not cover other resource types such as storage accounts, VNets, and newly created resources. The auditor requires complete subscription-wide configuration visibility rather than a snapshot of specific compute resources. A subscription-level Reader assignment is an inherited grant aligned with the full inventory boundary.

Question 103

An application already has an approved Storage Blob Data Contributor role definition. It should update blobs in container receipts only; the same storage account contains private containers for other customers. Where must the role assignment be placed?

  1. On the parent storage account resource.
  2. On the resource group containing the storage account.
  3. On the receipts container resource.
  4. On the subscription containing the resource group.

Explanation

Correct Answer

C:

Azure Storage supports data-role assignments at the individual blob container scope. Applying Blob Data Contributor on receipts gives the application read, write, and delete operations for that container but not sibling containers. The role is already approved, so the security decision is about the assignment scope rather than selecting a new role. Assigning it higher on the storage account or resource group would produce inherited access to additional customer data and break isolation.

Incorrect Answers

A:

A storage-account-level Blob Data Contributor grant would apply to all eligible containers beneath the account, including customer containers outside the application requirement. The role definition is not the problem; its broader scope is. Assign it at the named receipts container so the authorization is limited to that data partition.

B:

Resource-group-level Azure RBAC assignments inherit into eligible storage resources across that group. That would permit data operations in other accounts and containers if present, a clear conflict with customer isolation. The app needs only one container, so the assignment should be made on that container resource instead.

D:

Subscription-scope Blob Data Contributor could authorize writes and deletes to blobs throughout multiple storage accounts. This is broader than account scope and sharply exceeds the approved receipts-only boundary. Azure RBAC scope must be as narrow as the resource set required by the application, not as broad as the owning subscription.

Question 104

A pipeline must deploy resources into existing groups rg-blue and rg-green. Both are in one subscription with other production groups that the pipeline must not modify. What access assignment strategy should be used?

  1. Assign Contributor once at subscription scope.
  2. Assign Contributor only on rg-blue.
  3. Assign Contributor separately on rg-blue and rg-green.
  4. Assign Reader on both resource groups.

Explanation

Correct Answer

C:

Contributor at a resource-group scope permits ordinary resource deployment inside that group and its descendants without granting write rights to sibling groups. Two assignments covering rg-blue and rg-green match the pipeline's two approved destinations. Azure RBAC permissions are additive, so separate grants on both groups give the required combined reach. Subscription Contributor would be simpler to administer but would authorize changes to unrelated production groups and violate least privilege.

Incorrect Answers

A:

Subscription Contributor grants deployment rights across every resource group in the subscription, not only rg-blue and rg-green. That gives the pipeline authority over unrelated production workloads. Because both target resource groups already exist, the pipeline can receive group-level Contributor on each and avoid broad subscription permissions.

B:

A grant on rg-blue does not automatically extend to sibling rg-green; Azure RBAC inherits down a scope hierarchy, not sideways to peer resource groups. The pipeline would be unauthorized to deploy into the second approved destination. Two distinct group-scoped grants are required to meet both deployment targets.

D:

Reader at both target groups would provide visibility but cannot create or update resources through the pipeline. The scopes would be correctly limited, yet the role definition would still lack the needed deployment write actions. Contributor assigned on those two groups grants the actual operations without affecting other resource groups.

Question 105

The security team delegates limited Azure RBAC access administration for resource group `rg-sandbox`. Delegate `ops-helper` may create or remove only Backup Reader and Backup Contributor role assignments for Entra group `sg-backup` within `rg-sandbox`. The delegate must not assign Owner, grant access to another group, or manage assignments in sibling resource groups. Which configuration enforces these limits?

  1. Grant `ops-helper` Role Based Access Control Administrator on `rg-sandbox`, with conditions restricting role definition IDs and the `sg-backup` principal ID for both role-assignment creation and deletion.
  2. Grant `ops-helper` Contributor on `rg-sandbox`; Contributor also includes unrestricted `Microsoft.Authorization/roleAssignments/write`.
  3. Grant `ops-helper` Role Based Access Control Administrator at subscription scope without a condition and depend on administrators to follow a policy document.
  4. Grant `ops-helper` Backup Contributor on the Recovery Services vault and assume that backup operations rights include granting other identities Azure roles.

Explanation

Correct Answer

A:

Role Based Access Control Administrator permits Azure role-assignment administration at the assigned scope. A condition on the delegate's assignment can restrict the roles and principal IDs for both write and delete operations; Microsoft documents that the request attributes apply to creation and resource attributes to deletion. Resource-group scope keeps those delegated changes from reaching sibling groups.

Incorrect Answers

B:

Azure Contributor permits resource management but explicitly excludes Azure RBAC role assignment creation and deletion. Granting Contributor at `rg-sandbox` would not authorize the requested delegation, even though it can deploy other resources in that group.

C:

Unconditional Role Based Access Control Administrator at the subscription would permit role assignments across all resource groups, including unrelated production resources. A written rule does not enforce the required role and principal restrictions; the delegated assignment needs a narrow scope and conditions.

D:

Backup Contributor administers supported backup policies and protection operations, not Azure RBAC roleAssignments/write for other principals. Assigning that role on a vault cannot delegate controlled role grants in `rg-sandbox`.

Question 106

A deployment service principal already holds Network Contributor on resource group `rg-appnet` to manage its virtual networks. It now must edit the inbound rule of the existing NSG `nsg-edge` in a separate resource group `rg-security`. Azure returns AuthorizationFailed, and the security group contains unrelated protected networking resources. What is the narrowest appropriate additional Azure role assignment for this NSG-only change?

  1. Assign Reader on the nsg-edge NSG; viewing the existing configuration automatically grants write to its rules.
  2. Assign subscription Owner to the deployment principal; NSG modifications cannot be authorized at a single-resource scope.
  3. Reassign Network Contributor on rg-appnet where it already exists, because a role on one resource group automatically covers all other groups.
  4. Assign Network Contributor to the service principal at the individual nsg-edge resource scope in rg-security, preserving the existing rg-appnet assignment.

Explanation

Correct Answer

D:

The built-in Network Contributor role includes Microsoft.Network management Actions such as NSG changes. Assign it on the exact nsg-edge resource to allow only the required NSG administration, without granting changes to other networking resources in rg-security or broader subscription privileges.

Incorrect Answers

A:

Reader permits reading the resource and configuration but does not provide Microsoft.Network/networkSecurityGroups/write. A read-only assignment cannot solve the described authorization failure for changing an NSG rule.

B:

Owner is much broader than the needed networking operation and permits changing Azure role assignments. Azure RBAC roles can be assigned directly at resource scope, so granting subscription Owner is unnecessary and violates the separation-of-duties requirement.

C:

Azure role assignments are inherited downward within their assigned scope, not sideways to sibling resource groups. Reassigning the same role in rg-appnet does not authorize writes to nsg-edge in rg-security.

Question 107

An operator may administer role assignments within subscription sub-research but has no authorization over a sibling subscription sub-production. What RBAC assignment scope should be used?

  1. The parent management group containing both subscriptions.
  2. One resource group inside sub-research only.
  3. The sub-research subscription scope only.
  4. The tenant root management group.

Explanation

Correct Answer

C:

An Azure role assignment's scope defines the resource hierarchy in which its permissions can operate. Granting the approved access-administration role at sub-research allows role-management operations inside that subscription and its descendants, but not inside sibling sub-production. The role definition determines which actions are possible; the scope prevents the same role from reaching the other subscription. Do not assign the role at the common management group if the operator is responsible for only one child subscription.

Incorrect Answers

A:

A role grant at the common management group is inherited by both child subscriptions. That would allow the operator's permitted role-assignment actions in sub-production as well as sub-research, violating the segregation requirement. The grant belongs on the named subscription, not on an ancestor shared with a prohibited sibling.

B:

A resource-group-scoped grant would restrict role administration to that group, potentially preventing legitimate access changes on other resource groups in sub-research. The scenario authorizes the whole research subscription. Assign at the subscription level to cover its entire intended hierarchy without touching the sibling subscription.

D:

A root-level role grant can reach a wide set of subscriptions in the tenant. The operator's permitted scope is only sub-research, making this assignment substantially excessive. Resource hierarchy inheritance works downward from the grant; using the root would broaden access in precisely the way the case forbids.

Question 108

A Reader role was assigned to an audit group at management group mg-platform last month. Yesterday a new subscription was moved beneath mg-platform, and its resources suddenly appear in the group's portal inventory. What explains this?

  1. The subscription's storage account access keys were distributed to the group.
  2. A hidden Reader grant was automatically copied into every resource group.
  3. The audit group automatically became subscription Owner.
  4. The existing Reader role assignment is inherited from mg-platform by the new subscription.

Explanation

Correct Answer

D:

Azure RBAC inheritance follows the management group, subscription, resource group, and resource hierarchy. Adding a subscription beneath mg-platform brings that subscription's resources under the scope of the existing Reader role assignment. No new local Reader grant is required for that inherited visibility. Administrators should review inherited authorizations whenever they move subscriptions among management groups, because a hierarchy change can broaden effective access even though no role assignment was edited on the subscription itself.

Incorrect Answers

A:

Storage account keys concern data and account authorization, not the appearance of Azure Resource Manager resources in a subscription portal inventory. A management-group Reader assignment already explains the read visibility. There is no need to assume keys were shared, and such key distribution would not be equivalent to inheriting Azure resource RBAC permissions.

B:

Inheritance does not require Azure to copy the parent assignment into each child resource group as a new local grant. The original assignment remains at the management-group scope and is evaluated for descendant resources. Looking only for direct role assignments on the subscription would therefore miss the actual source of effective access.

C:

An inherited Reader role grants read-only resource visibility, not Owner's management and role-assignment powers. Seeing the newly moved subscription does not imply any escalation to infrastructure administration. The visibility follows the existing management-group Reader assignment, and the effective role remains Reader unless other grants exist.

Question 109

A principal has inherited Contributor at subscription scope. A resource owner assigns Reader directly on a sensitive VM, hoping to prohibit writes on that VM. What will the extra Reader assignment do?

  1. It will not remove the inherited Contributor permissions; the parent grant must be narrowed or removed.
  2. It will convert Contributor to Reader after the principal signs out.
  3. It will override Contributor because the VM is a narrower scope.
  4. It will revoke Contributor on all other VMs in that subscription.

Explanation

Correct Answer

A:

Azure RBAC allow permissions are additive across direct and inherited role assignments. A child-resource Reader assignment cannot subtract the management write actions the principal already receives through subscription Contributor. To enforce the lower privilege, an authorized administrator must remove or narrow the parent assignment, change identity/group access, or otherwise redesign the role scope. Merely adding a weaker role to the VM leaves the effective Contributor permission available there.

Incorrect Answers

B:

Refreshing a token or signing out does not turn additive RBAC grants into a restrictive hierarchy. Credential refresh may affect when role changes become visible, but no removal of the Contributor assignment has occurred here. The principal remains entitled to inherited Contributor actions unless authorization is changed at the source of that grant.

C:

Azure RBAC does not use a 'most specific allow role wins' rule that replaces inherited privileges with a weaker child assignment. Subscription Contributor continues to grant the allowed write actions on descendant resources. Adding VM Reader is an additional permission source and does not revoke Contributor. The broader grant itself must be changed.

D:

A new role grant on one VM does not modify or delete the existing Contributor assignment at subscription scope. The inherited role remains effective on other descendants as well as the sensitive VM. A targeted VM Reader assignment is not a mechanism for revoking a parent-scope permission across the subscription.

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.