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 22

Question 210

A management group named mg-legacy still contains subscription sub-lab and child management group mg-archive. Governance has approved retiring mg-legacy; both child scopes must remain managed under mg-current without deleting their subscriptions or resources. An attempted deletion of mg-legacy is blocked. What is the required sequence?

  1. With the necessary hierarchy permissions, move sub-lab and mg-archive to approved parent management groups, confirm mg-legacy has no children, and then delete mg-legacy.
  2. Delete mg-legacy first; Azure automatically deletes its child subscriptions but retains their VMs in the tenant root.
  3. Remove only the policy assignments from mg-legacy; management groups with child subscriptions can then be deleted without moving the children.
  4. Change mg-legacy's display name to mg-current; this empties the former management group and removes the original group ID automatically.

Explanation

Correct Answer

A:

Azure cannot delete a management group while child subscriptions or management groups remain. Authorized administrators must move those child scopes to their approved parents, account for inherited governance and hierarchy permissions, verify the target group is empty, and only then delete mg-legacy. This preserves the child resources and tests deletion prerequisites, not initiative assignment.

Incorrect Answers

B:

Deleting a management group with children is blocked; the platform does not silently delete subscriptions or relocate their VMs as a consequence of a management-group delete. Moving the children first is required.

C:

Removing policy assignments changes governance, not the hierarchy. The remaining child management group and subscription still prevent deleting mg-legacy even if its policies have all been unassigned.

D:

The display name is not the same as management-group identity or child membership. Renaming does not move sub-lab or mg-archive or meet the empty-group precondition for deletion.

Question 211

An Azure subscription hosting nonproduction workloads is under a restrictive Production management group. Governance approves moving it to the Test management-group hierarchy while maintaining an auditable least-privilege posture. Which TWO actions should administrators take? Select TWO answers.

  1. Delete the Production management group before moving the subscription.
  2. Assign the subscription Owner role to all operators and assume all inherited controls disappear.
  3. Relocate every virtual machine into the Test management group's Azure region.
  4. Inspect the new inherited Azure Policy and RBAC assignments after the move.
  5. Change the subscription's parent to the approved Test management group.

Explanation

Correct Answers

D:

Changing a subscription's management-group parent changes which ancestor Azure Policy and RBAC assignments apply. After the move, check effective permissions, any deployment denies, policy exemptions and inherited Reader or Contributor grants to confirm the Test baseline does not unintentionally expose or block workloads. This verification is independently necessary: successfully reparenting the subscription alone does not establish that its new governance and authorization outcomes match the approved requirements.

E:

Management groups organize Azure subscriptions for inherited RBAC and Azure Policy assignments. To place the nonproduction subscription under the approved Test governance baseline, an authorized administrator must move its management-group association to that target. This changes the governing hierarchy, not the subscription's billing owner or workload region. Confirm the operator has the required subscription and management-group privileges, and perform the controlled move under the approved change process.

Incorrect Answers

A:

Deleting an entire management group is unnecessary and could disrupt governance across other subscriptions that still require Production policies. The approved operation concerns one subscription's management-group parent, not removal of shared hierarchy resources. Move the eligible subscription under Test and validate inherited roles and policies without destroying Production's governance structure.

B:

Owner is an expansive Azure RBAC permission and does not exempt resources from Azure Policy assignments inherited through the new management-group hierarchy. Giving everyone Owner would increase security risk and does not verify the desired Test baseline. Administrators should adjust the parent within authorized scope and inspect the resulting effective governance settings.

C:

An Azure management group is a governance and subscription-hierarchy container, not a workload-deployment region. Moving a subscription between management groups does not automatically move or require relocating its VMs, disks or VNets. The administrator should reparent the subscription and verify effective inherited controls while leaving workloads in their approved Azure regions.

Question 212

A multinational organization has separate European and North American divisions, each requiring shared but different governance over several Azure subscriptions. Which design is most maintainable?

  1. Use a purposeful management-group hierarchy with division-specific child groups and common controls at a suitable parent.
  2. Place all subscription resources in one global resource group.
  3. Create one subscription Owner assignment for every employee in both divisions.
  4. Use only resource name prefixes to represent the division and stop assigning policies.

Explanation

Correct Answer

A:

Management groups allow subscriptions to be organized in a hierarchy so organization-wide controls can reside at appropriate ancestors while regional or divisional policies are applied to narrower child groups. Create a structure matching the stable governance boundaries rather than simply the number of subscriptions. Evaluate inherited assignments and avoid unnecessarily deep trees. This supports consistent common policy without forcing European and North American divisions into identical local rules.

Incorrect Answers

B:

Resource groups belong to individual subscriptions; a single resource group cannot span the organization's independent subscriptions or replace their governance hierarchy. It would also collapse useful workload boundaries. Management groups provide the appropriate cross-subscription organizational scope. The proposed global container is not supported by the subscription hierarchy.

C:

Granting widespread Owner rights would weaken separation of duties and expose unrelated resources. Owner assignment does not provide policy hierarchy or distinguish regional compliance boundaries. Use properly scoped management-group roles and policies aligned to administrative responsibility instead. Administrative rights should follow responsibility and least privilege at each hierarchy level.

D:

Naming conventions help inventory but do not enforce controls or grant inherited governance permissions. Resource names may not be editable and do not provide the desired subscription-level access and policy boundaries. Use division-aware management-group assignments for enforceable and maintainable controls.

Question 213

An engineer tries to add an Azure VM directly as a child of the tenant root management group and receives no supported option. What is the correct explanation?

  1. Management groups organize subscriptions; VMs remain resources in resource groups inside subscriptions.
  2. Create a new storage account and place the VM inside it before assigning the management group.
  3. VMs must always live directly under the root management group to inherit Azure Policy.
  4. A VM can be added directly if the engineer assigns the Network Contributor role.

Explanation

Correct Answer

A:

Azure management groups are organizational and governance scopes above subscriptions, not direct containers for virtual machines. A VM is deployed into a resource group belonging to a subscription; the subscription can then be associated with a management group for inherited policy or RBAC. Understand the hierarchy as management groups, subscriptions, resource groups and individual resources. The missing option is a resource-hierarchy distinction, not a permission to move a VM outside its subscription.

Incorrect Answers

B:

A storage account is not a general container for Azure VM resources and cannot substitute for a subscription or resource group. This proposal confuses infrastructure data storage with administrative resource hierarchy. Keep the VM in its resource group and associate the subscription with the desired management group.

C:

Policies can inherit from management groups through their descendant subscriptions and resource groups. A VM does not need—and cannot have—a direct management-group child relationship for that inheritance. Place the resource in its supported resource group and subscription hierarchy. Azure RBAC role assignment cannot change this supported parent-child relationship.

D:

Network Contributor grants network-resource management actions at a supported scope. It cannot change Azure's resource hierarchy or make a VM an eligible direct child of a management group. The management-group child object is a subscription or child management group, not a VM.

Question 214

An auditor's Reader role was assigned at tenant root management-group scope. New Azure subscriptions unexpectedly become visible to the auditor. How can security narrow future access correctly?

  1. Remove or narrow the broad ancestor assignment and make targeted Reader grants at approved descendant scopes.
  2. Add Reader at each individual subscription while retaining the root Reader assignment.
  3. Assign a CanNotDelete lock to the root management group.
  4. Change the regions of the newly created subscriptions.

Explanation

Correct Answer

A:

An RBAC role assigned at the root management group can inherit into descendant subscriptions. That explains why new subscriptions are visible even without explicit local grants. To narrow the auditor's reach, adjust or remove the ancestor assignment and grant Reader only at the agreed child management groups or individual subscriptions. Adding a narrower Reader role at one subscription does not subtract access already inherited from the root; fix the grant that creates the broad scope.

Incorrect Answers

B:

Azure RBAC permits additive role assignments. New narrower grants do not negate an ancestor Reader grant that already reaches all subscriptions. This would create redundant assignments while leaving unexpected visibility intact. Remove or reduce the inappropriate root-scope role and reassign only where authorized.

C:

Resource-management locks restrict supported control-plane mutations or deletion; they do not cancel inherited RBAC read visibility. A lock cannot replace role scope correction for an auditor who sees unintended subscriptions. Address the ancestor Reader assignment directly. Effective read access remains governed by the inherited role assignments.

D:

Management-group RBAC inheritance is driven by administrative scope and the subscription hierarchy, not the geographic region of resources. Changing region settings would not withdraw the auditor's permissions and could create unrelated operational problems. Narrow the root-level grant instead. The broad role assignment would still apply to the descendant subscription.

Question 215

Management group `mg-corp` has one Azure Policy assignment that denies creation of storage accounts with public network access. Governance has approved excluding the entire child subscription `sub-lab` from this assignment indefinitely because a separate baseline controls that subscription. The other child subscriptions must remain subject to the deny assignment. The excluded subscription must NOT appear as Exempted in this assignment's compliance results; its resources should instead be outside this assignment's evaluation scope. What precise change meets these requirements?

  1. Grant subscription Owner to the sub-lab deployment identity so Azure Policy deny stops evaluating only that subscription.
  2. Remove the assignment from mg-corp and reassign it independently to every other child resource; this is the required way to exclude just one child subscription.
  3. Update the management-group assignment's `notScopes` to contain the resource ID of sub-lab, leaving the assignment applied to other in-scope children.
  4. Create a time-limited policy exemption at sub-lab with expiry and an Exempted compliance record, without changing the assignment's excluded scopes.

Explanation

Correct Answer

C:

Azure Policy assignments inherit from management groups to their children. Adding sub-lab's full subscription resource ID to the assignment's `notScopes` removes that descendant from the assignment's applicability and compliance denominator while leaving the shared deny on other child subscriptions. Microsoft distinguishes this exclusion from a tracked exemption.

Incorrect Answers

A:

Azure RBAC Owner does not bypass a policy deny evaluation. Assigning broader permissions to the sub-lab deployment identity would expand its resource access without changing the inclusion/exclusion scopes of the inherited management-group policy assignment.

B:

Removing the parent assignment can interrupt enforcement across every descendant subscription. Azure Policy supports excluded scopes in the existing assignment, so recreating separate independent assignments is unnecessary and increases governance drift risk.

D:

An Azure Policy exemption is a separate waiver or mitigation object and is reflected as Exempted in compliance reporting; a time-limited exemption also does not meet the explicit indefinite out-of-scope requirement. The case instead calls for `notScopes` on the parent assignment.

Question 216

An administrator changes an Azure management group's display name to match a new business-unit name. The business owner expects all contained subscription IDs and VM resource IDs to change automatically. What should the administrator clarify?

  1. The management-group display-name change does not automatically rewrite subscription and VM resource identifiers.
  2. The rename removes all inherited policy and RBAC assignments until every subscription is reauthorized.
  3. Every VM must be stopped and recreated whenever the management-group display name changes.
  4. The display-name update automatically creates replacement subscription IDs and copies all resources.

Explanation

Correct Answer

A:

The management group's display name is presentation metadata for its governance container. Renaming it does not recreate descendant subscriptions, reassign their subscription IDs, or rewrite Azure VM resource IDs. Changes to hierarchical associations and actual resource identities are separate operations with their own consequences. Verify that the display-name update succeeded while retaining existing subscriptions and resources unless explicitly authorized moves or redeployments are separately planned.

Incorrect Answers

B:

Changing a group's display name is different from modifying its hierarchy placement or assigned policy and RBAC scopes. Existing governance assignments do not automatically vanish solely because the display label changes. Review the resulting metadata but do not perform unnecessary blanket reassignment of permissions.

C:

A VM resides within a resource group and subscription, not directly inside the management group. A parent governance label change has no general requirement to restart or recreate every descendant VM. Such operations would introduce unnecessary outage and data risk without satisfying the display-name requirement.

D:

Subscription identifiers are not derived from a parent management group's human-readable display name. Changing that label does not trigger subscription replacement or resource copies. Treat governance metadata separately from resource identity, deployment and migration operations. A display name is not part of a subscription's immutable provider identifier.

Question 217

A Synapse Analytics serverless SQL pool in workspace syn-ops must read a private Blob container in storage account stanalytics01. The workspace and storage account belong to the same Microsoft Entra tenant. The storage account permits only selected networks, and the workspace is a supported resource instance that cannot use a designated VNet subnet or stable public egress IP for these requests. The workspace identity already has Storage Blob Data Reader but receives network-denied responses. Which narrowly scoped firewall change solves the network denial without opening the account to every Azure resource?

  1. Enable anonymous container access, then tell the workspace to retry without an identity.
  2. Give the workspace identity Storage Blob Data Owner at subscription scope and leave the network rules unchanged.
  3. Add a resource instance network rule permitting the specific Microsoft.Synapse/workspaces/syn-ops resource, retaining its separate Blob data RBAC assignment.
  4. Allow the workspace's RFC 1918 private IP as a public storage firewall IP-address rule, without identifying the resource instance.

Explanation

Correct Answer

C:

Azure Storage resource instance rules admit network requests from supported Azure resource identities that cannot be isolated by a subnet or public-IP rule. Microsoft documents Microsoft.Synapse/workspaces as an eligible resource type and requires the resource to be in the same tenant as the storage account, though subscriptions may differ. Such a rule permits access through the public endpoint but does not independently grant Blob data rights; the existing managed-identity RBAC must still authorize reads.

Incorrect Answers

A:

Anonymous Blob access changes authorization for container content; it does not give the Synapse service a network exception through a selected-networks storage firewall. It would also weaken the required private data protection. The supported control is a rule identifying the eligible Azure resource instance, alongside the existing identity-based Blob authorization.

B:

Storage Blob Data Owner grants much broader Blob data capabilities, and the existing Blob Data Reader authorization is already adequate for reads. Azure Storage evaluates public-endpoint network admission independently of Blob data RBAC; increasing the role does not admit a blocked resource instance. Keep least privilege and add a specific network rule instead.

D:

Public IPv4 firewall rules are not configured by entering an Azure resource's RFC 1918 private address. Even a real stable public IP is unavailable in this case, so an IP rule cannot reliably identify the supported Synapse workspace. A resource instance rule names the authorized workspace resource and avoids allowing unrelated Azure services.

Question 218

Storage account stsecure has public access limited to selected networks. An Azure VM added to a new subnet gets a network-denied response despite holding Storage Blob Data Reader. What should the administrator check first?

  1. Upgrade the VM's identity from Blob Data Reader to Blob Data Owner.
  2. Disable Azure Policy on the containing subscription to allow all storage traffic.
  3. Confirm the VM's source subnet is allowed by storage firewall rules and has the required service endpoint or private route.
  4. Rotate both storage access keys and replace the VM image.

Explanation

Correct Answer

C:

A valid Blob Data Reader grant proves only that the principal may read supported data if the request reaches the storage service. Selected-network firewall settings can still deny a VM on an unlisted subnet. Inspect the VM's actual route, the source subnet rule and service endpoint or configured private endpoint connectivity. Fix the network path under the approved architecture without granting greater blob privileges to a correctly authorized identity.

Incorrect Answers

A:

Increasing data-plane rights does not bypass a storage firewall network denial. Blob Data Owner would add excessive data control, while the identity already has the read permission stated in the case. Check network access rules and source connectivity before changing any authorization role.

B:

The failure is a runtime storage-network access decision, not evidence that an Azure Policy assignment is actively denying a deployment. Removing subscription governance would have much wider consequences and would not necessarily change the account firewall. Validate the selected-network configuration before touching policy.

D:

The request authenticates through Microsoft Entra RBAC and is blocked by the configured network boundary. Regenerating shared keys or rebuilding the machine does not add its subnet to allowed networks. Those changes add downtime and security risk without addressing the observed firewall denial.

Question 219

An enterprise must let applications read blobs using a private IP inside VNet vnet-prod. Public endpoint traffic must be disabled, and workloads must use the normal storage account host name without mapping individual IPs manually. Which THREE actions are required? Select THREE answers.

  1. Enable anonymous public container access to simplify private IP routing.
  2. Create a new Azure public IP and attach it to the private endpoint.
  3. Assign Storage Blob Data Owner to every user at the subscription scope.
  4. Configure the corresponding privatelink.blob.core.windows.net private DNS zone and link the client virtual network.
  5. Create a private endpoint for the storage account's Blob subresource in an approved subnet.
  6. Disable public network access for the storage account after validating the required private path.

Explanation

Correct Answers

D:

The standard Blob service hostname needs to resolve to the private endpoint IP from authorized clients. Linking the appropriate private DNS zone to the workload virtual network and ensuring the private endpoint's A record exists enables that resolution. Without correct DNS, a client might still resolve the service's public address, even though a private endpoint exists. Confirm actual name resolution from the application's subnet rather than assuming endpoint deployment automatically updates every DNS system.

E:

A Blob private endpoint provides a private network interface and IP address reachable through the enterprise virtual network for the chosen storage subresource. It allows clients to send blob traffic privately rather than depend on the account's public endpoint. Creating the endpoint is independent of enforcing public access restrictions and resolving the normal hostname, so those controls must also be configured for the entire requirement.

F:

Disabling public network access enforces the requirement that the account not accept traffic through its public service endpoint. A private endpoint can coexist with an enabled public endpoint, so creating one alone does not prohibit public requests. Validate that authorized clients can reach the private IP, then apply the account's public access restriction and confirm the service remains reachable through the intended private link.

Incorrect Answers

A:

Anonymous container access changes blob authorization exposure and has no role in establishing a private IP, mapping DNS to a private endpoint or disabling the public storage endpoint. It would undermine confidentiality and would not satisfy the network restriction. Keep authentication intact and deploy private connectivity and the corresponding DNS configuration.

B:

A storage private endpoint uses an Azure virtual-network private address, not a public IP resource attached to the endpoint. Associating a public frontend would contradict the requirement to keep blob traffic private. The proper design uses private endpoint networking, correct private DNS and disabled public account access rather than public address allocation.

C:

A wide data-owner grant does not create private network connectivity or private DNS resolution. It could expose sensitive blobs across unrelated accounts and is unnecessary for read-only workloads. The three required infrastructure changes are the Blob private endpoint, corresponding private DNS resolution and public endpoint restriction; data authorization should remain least privileged separately.

Question 220

An external partner's gateway sends traffic from a stable public IPv4 address to a storage account. Security permits that gateway only and wants every other public source denied. What should be configured?

  1. A narrow IP-based network rule for the partner's actual public IPv4 address, with selected networks enforced.
  2. Allow the entire 0.0.0.0/0 range in the storage firewall.
  3. Enable a virtual network service endpoint on the partner's on-premises Ethernet adapter.
  4. Assign Reader on the resource group containing the storage account.

Explanation

Correct Answer

A:

Storage firewall IP network rules can permit eligible public IPv4 source addresses while the account's default selected-network restriction denies other public origins. Add only the verified partner egress address or smallest supported range, not a broad public CIDR, and keep storage authentication and authorization independently enforced. Review NAT changes with the partner because the firewall evaluates the public source seen by Azure Storage, not necessarily an internal workstation's address.

Incorrect Answers

B:

Allowing every public IPv4 source would remove the requested origin restriction and expose the storage endpoint to other internet clients, even if normal authentication still applies. Use a narrow verified partner egress rule rather than a universal allow range. Authentication is not a replacement for the specified network control.

C:

Azure service endpoints are configured for supported Azure virtual-network subnets, not arbitrary on-premises network adapters. An external gateway using a public egress IP should be covered by an appropriate storage IP firewall rule or another approved private connectivity design. A fictitious endpoint setting cannot authorize its traffic.

D:

Resource-group Reader allows ARM configuration visibility; it does not create a storage firewall IP allowlist entry. The partner needs an approved network path, followed by appropriate storage data authorization, not a generic management role. Add the required public-source network rule instead.