Pass Your Microsoft AZ-104 Exam Easy!

Microsoft AZ-104 Exam Questions & Answers, Accurate & Verified By IT Experts

Instant Download, Free Fast Updates, 99.6% Pass Rate

AZ-104 Premium Bundle

$79.99

Microsoft AZ-104 Premium Bundle

AZ-104 Premium File: 606 Questions & Answers

Last Update: Sep 24, 2026

AZ-104 Training Course: 132 Video Lectures

AZ-104 PDF Study Guide: 458 Pages

AZ-104 Bundle gives you unlimited access to "AZ-104" files. However, this does not replace the need for a .vce exam simulator. To download VCE exam simulator click here
Microsoft AZ-104 Premium Bundle
Microsoft AZ-104 Premium Bundle

AZ-104 Premium File: 606 Questions & Answers

Last Update: Sep 24, 2026

AZ-104 Training Course: 132 Video Lectures

AZ-104 PDF Study Guide: 458 Pages

$79.99

AZ-104 Bundle gives you unlimited access to "AZ-104" files. However, this does not replace the need for a .vce exam simulator. To download your .vce exam simulator click here

Microsoft AZ-104 Practice Test 12

Question 110

Five Azure subscriptions belong to one business unit, while all other subscriptions must remain outside a new region-restriction policy. The five are children of one dedicated management group and the other subscriptions are not its descendants. Where is the narrowest common assignment?

  1. Assign the policy at the tenant root management group without exclusions.
  2. Grant Owner to every user in the five subscriptions instead of assigning a policy.
  3. Create resource-group tags but leave the allowed-locations policy unassigned.
  4. Assign the allowed-locations Azure Policy at the dedicated management group that contains exactly those five subscriptions.

Explanation

Correct Answer

D:

A policy assignment inherits to that management group’s descendant subscriptions without reaching sibling branches, matching the requested common boundary.

Incorrect Answers

A:

Root scope also covers unrelated subscriptions and violates the explicit restriction against affecting other business units.

B:

RBAC Owner changes authorization; it does not enforce the requested resource-location governance restriction.

C:

Tags can classify costs and environments but do not themselves reject prohibited deployment locations.

Question 111

A subscription moves under a management group with an assigned Azure Policy initiative. Its resources become noncompliant even though nobody assigned that initiative directly on the subscription. Why can this happen?

  1. Assignments inherited through the management-group hierarchy also apply to descendant subscriptions unless exclusions or exemptions apply.
  2. A subscription always ignores management-group policies until an owner duplicates the initiative assignment at subscription scope.
  3. The original resource group location automatically copies the policy definitions into each resource as an editable setting.
  4. The new management group silently grants its members Contributor permission, causing compliance status to reset.
  5. Only a child resource group can inherit an initiative; a subscription directly below a management group is excluded from inheritance.

Explanation

Correct Answer

A:

Management-group policy scope covers contained subscriptions, so reassignment in the hierarchy changes the effective governance inherited by the subscription.

Incorrect Answers

B:

Azure Policy supports inherited assignments; an explicit duplicate is not a prerequisite for evaluation.

C:

Policy assignment inheritance is based on scope hierarchy, not a data-plane copy of definitions or geography.

D:

Policy compliance and RBAC role grants are distinct mechanisms; a management-group policy need not create access grants.

E:

Subscriptions are descendants in the supported hierarchy and are within inherited assignment scope.

Question 112

A user has write privileges in multiple subscriptions but no local role grants. What should the access review inspect?

  1. Place the five subscriptions under an appropriate management group and assign policy there
  2. Assign the authorized role at only the designated subscription scope
  3. Governance assignments inherit down the management-group hierarchy
  4. Inspect inherited RBAC roles at parent management groups

Explanation

Correct Answer

D:

Parent-level grants can extend into descendant subscriptions even without local assignment records.

Incorrect Answers

A:

Management groups organize subscription governance and allow scoped inheritance. The stated constraint is different: parent-level grants can extend into descendant subscriptions even without local assignment records.

B:

A management-group assignment could unintentionally extend the same rights to sibling subscriptions. The stated constraint is different: parent-level grants can extend into descendant subscriptions even without local assignment records.

C:

Child subscriptions are within parent assignment scope unless excluded or exempted. The stated constraint is different: parent-level grants can extend into descendant subscriptions even without local assignment records.

Question 113

An administrator proposes moving a production subscription under a new management group. What preparation is essential?

  1. Compare effective inherited policy and RBAC before and after the move
  2. Management-group reparenting changes governance hierarchy, not deployed resource regions
  3. Governance assignments inherit down the management-group hierarchy
  4. Place the five subscriptions under an appropriate management group and assign policy there

Explanation

Correct Answer

A:

Reparenting changes governance inheritance and can alter access and policy evaluation.

Incorrect Answers

B:

Regional placement of VMs remains a resource attribute and requires a separate migration plan. The stated constraint is different: reparenting changes governance inheritance and can alter access and policy evaluation.

C:

Child subscriptions are within parent assignment scope unless excluded or exempted. The stated constraint is different: reparenting changes governance inheritance and can alter access and policy evaluation.

D:

Management groups organize subscription governance and allow scoped inheritance. The stated constraint is different: reparenting changes governance inheritance and can alter access and policy evaluation.

Question 114

An engineer needs Azure Policy to apply only to one subscription, but the proposed assignment scope is the tenant root management group. What change prevents the assignment from governing unrelated subscriptions?

  1. Recreate the same policy assignment at the tenant root management group, assuming the policy definition title limits its effect to one subscription.
  2. Management-group reparenting changes governance hierarchy, not deployed resource regions
  3. Governance assignments inherit down the management-group hierarchy
  4. Restrict the assignment to the intended subscription rather than tenant root

Explanation

Correct Answer

D:

Azure Policy assignments enforce or evaluate controls at the assigned scope and eligible descendants. Because only one subscription is authorized for the proposed standard, the proper configuration is to restrict the assignment to that subscription rather than tenant root. This preserves unrelated subscriptions' existing governance and avoids inadvertently denying their deployments or marking them noncompliant. Confirm which principal can create the subscription-scoped assignment, then check effective policy coverage, exclusion lists, and any documented exemptions. An assignment created at the tenant root remains broad even if its description mentions only one subscription; the actual scope must match the approval.

Incorrect Answers

A:

Creating the same assignment at the root would preserve the original excessive scope. Azure Policy assignment coverage comes from the target scope and effective exclusions, not a name suggesting a narrower audience. If the tenant root includes other business subscriptions, all descendants may be subject to that policy. The requested control should affect one subscription, so moving or recreating the assignment at root is not a safe fix. Select the intended subscription scope instead, then inspect inherited assignments, exclusions and exemptions without weakening independent governance on other subscriptions.

B:

A management-group reparenting changes which management-group assignments a subscription inherits, but it does not convert an existing root-scoped Azure Policy assignment into a subscription-only assignment. It is also unrelated to where the subscription's resources are physically deployed. This scenario does not request a hierarchy restructure; it requests preventing a new policy from affecting unrelated subscriptions. Moving resources or changing the management-group tree would be more disruptive and still leave an overly broad tenant-root assignment possible. Correct the Azure Policy assignment scope to the designated subscription, then validate its effective coverage.

C:

Management-group inheritance explains why a root assignment might affect every descendant subscription, but it is a description of the scope risk rather than the configuration change requested. Here the engineer has already selected the tenant root and must prevent governance spillover into other business subscriptions. Simply identifying that root policies inherit does not change an assignment or exclude descendants. The administrator should assign at the actual target subscription, check effective Policy assignments on the intended resources, and confirm unrelated subscriptions are outside the new assignment. Inheritance is the technical reason for the correction, not an alternative implementation of it.

Question 115

A subscription is reassigned to another management group, and a stakeholder believes its VMs automatically change Azure region. What is correct?

  1. Assess each resource's supported migration path rather than treating the group's metadata region as deployment location
  2. Compare effective inherited policy and RBAC before and after the move
  3. Place the five subscriptions under an appropriate management group and assign policy there
  4. Management-group reparenting changes governance hierarchy, not deployed resource regions

Explanation

Correct Answer

D:

Regional placement of VMs remains a resource attribute and requires a separate migration plan.

Incorrect Answers

A:

A resource group's metadata location and member resource regions are distinct. The stated constraint is different: regional placement of VMs remains a resource attribute and requires a separate migration plan.

B:

Reparenting changes governance inheritance and can alter access and policy evaluation. The stated constraint is different: regional placement of VMs remains a resource attribute and requires a separate migration plan.

C:

Management groups organize subscription governance and allow scoped inheritance. The stated constraint is different: regional placement of VMs remains a resource attribute and requires a separate migration plan.

Question 116

A corporate developer has Storage Blob Data Reader on a storage account. Public network access is enabled with default Deny, but the developer connects through the company NAT public IP, which is absent from the storage firewall allowlist. No private endpoint is available. Which least-scope network change permits the approved client to try reading blobs without changing its data role?

  1. Enable the trusted Microsoft services bypass for every client on the corporate internet
  2. Add only the verified corporate NAT public egress IP to the storage firewall IP rules
  3. Add a Microsoft.Storage service endpoint on the developer laptop itself
  4. Grant Storage Blob Data Contributor at subscription scope in place of the existing Reader role
  5. Add the client laptop’s RFC1918 private IP to the storage account public IP firewall rules

Explanation

Correct Answer

B:

Storage public endpoint firewall rules can permit approved public client addresses when public network access is enabled. The specific failure is that the company NAT source IP is not permitted under a default-deny policy. Add that controlled public address or appropriate supported range after validating the egress identity, retain default Deny, and re-test the blob request. Blob Data Reader remains the separate data-plane authorization; a network allow does not itself grant access to private blob contents.

Incorrect Answers

A:

Trusted-services exceptions apply to particular supported Azure service scenarios, not to any developer workstation merely because it is used for Azure work. The client is outside the allowed VNet and connects through the company NAT public IP. Enabling a trusted-services bypass is neither a general corporate egress rule nor a substitute for correctly scoped IP allowlisting. Such an exception would leave the reported public client unapproved, and could broaden access paths unnecessarily.

C:

Azure Storage service endpoints are configured for supported Azure virtual network subnets and used with corresponding storage virtual-network rules. A workstation traversing corporate NAT on the public internet does not become a VNet subnet by receiving a service-endpoint label. The scenario specifies that no approved VNet path or private endpoint is available. The appropriate network fix is a narrowly allowed verified corporate public egress IP, not a fictitious laptop service endpoint.

D:

Blob Data Contributor adds write and other data actions that the developer does not need, and it does not alter public endpoint firewall allowlists. The scenario already states that the required read role is present and pinpoints the denied NAT IP. Broadening the role therefore exposes more blob data operations while leaving connectivity blocked. Keep the least-privilege read assignment and correct the network admission separately.

E:

A corporate laptop behind NAT reaches the public storage endpoint from its translated public source IP, not the machine’s local RFC1918 address. Public IP allowlists do not simply match that private laptop address. In this case the account uses default-deny public network rules and lacks the real corporate NAT IP. Choose the verified public egress IP for the necessary approval rather than entering an address not observed by the service.

Question 117

A multitenant App Service web app cannot read from Azure Blob Storage because its outbound requests do not originate from the approved VNet subnet `web-egress`. That subnet ALREADY has a Microsoft.Storage service endpoint and an allowed Storage firewall virtual-network rule; the app has NO VNet integration. The design must retain the existing Storage public endpoint rather than add a private endpoint. Which App Service networking setting is missing?

  1. Verify service endpoint/private route and matching storage firewall rule plus data permission
  2. Check whether that trusted Azure service is explicitly supported by the storage firewall exception
  3. Use an approved private endpoint and correct private DNS routing
  4. Configure regional App Service virtual-network integration to the existing approved `web-egress` subnet

Explanation

Correct Answer

D:

Regional App Service VNet integration lets a multitenant App Service app send supported outbound traffic through a designated delegated subnet; it doesn't move the app's inbound listener inside that subnet. The `web-egress` subnet already has the Microsoft.Storage service endpoint and Storage virtual-network allow rule, but a web app without VNet integration can't use those subnet permissions. Connect the app to the supported integration subnet, checking regional/tier and subnet prerequisites. Service-endpoint traffic will then use the integrated route; confirm effective outbound connectivity and separately authorize the workload for Blob data operations. This tests an App Service networking requirement, not the Storage rule creation tested elsewhere.

Incorrect Answers

A:

A Storage service endpoint rule, firewall allowlist, and Blob data role are separate checks that matter after the application is actually sending outbound traffic through its integrated subnet. The question explicitly states that the Microsoft.Storage endpoint and Storage firewall VNet rule are already configured for `web-egress`. Rechecking those existing settings does not make a multitenant App Service app use that subnet; its public outbound traffic can still miss the rule. Add App Service regional VNet integration to the approved subnet first, then verify service-endpoint routing and Blob authorization as separate post-change validations.

B:

Storage trusted-service exceptions are limited to explicitly documented Microsoft services and are not a universal permission for any application hosted in Azure. A multitenant App Service instance doesn't automatically gain access to a restricted Storage account merely because both resources are Azure services. Here the subnet service endpoint and VNet firewall allow rule already exist, so the missing connection is on the application's outbound networking side. Configure regional App Service VNet integration to the authorized `web-egress` subnet instead of widening Storage firewall exceptions or bypassing the deliberate subnet restriction.

C:

A Storage Private Endpoint with suitable private DNS is a valid design for reaching Blob Storage over a private IP, but that would introduce a new network architecture that the question expressly rules out. The account already exposes a deliberately restricted public service endpoint reachable from an approved subnet through a Microsoft.Storage service endpoint. Its missing piece is not private DNS; it's the App Service app's outbound VNet integration with that permitted subnet. Keep private endpoints for a case whose architecture requires private IP connectivity, and don't treat VNet integration as an inbound private endpoint for App Service.

Question 118

A storage account has public network access set to Disabled. A developer has Storage Blob Data Reader and the corporate NAT IP still appears on an allowlist, yet their request to the public Blob endpoint is denied. Security has not authorized any configuration changes. Which explanation identifies the effective network rule?

  1. The corporate NAT IP must be rediscovered because disabling public access automatically translates the company's public address
  2. Disabled public network access prevents the public endpoint IP/VNet firewall allowlists from granting connectivity; approved private endpoint traffic is the supported private path
  3. Adding a Microsoft.Storage service endpoint to the developer's subnet will override Disabled public network access at the account
  4. The Storage Blob Data Reader role should automatically bypass storage network rules, so the error proves the account is corrupt

Explanation

Correct Answer

B:

The publicNetworkAccess setting is the decisive control. When it is Disabled, the storage public endpoint does not accept requests merely because a corporate IP appears on a storage firewall allowlist or the caller has Blob Data Reader. That user role controls data-plane authorization after networking succeeds; it cannot bypass the storage account's network boundary. Microsoft documents that private endpoint connections are the supported access path in this mode. The question asks for the reason an allowed public egress identity still fails, not for implementing the private endpoint and private DNS pieces, which are a separate configuration task. Identify the setting before recommending any authorized remediation or data permission changes.

Incorrect Answers

A:

An unexpected NAT egress address can explain a denied request when a storage account permits selected public networks. This scenario supplies the crucial contrary fact: public network access is explicitly Disabled. Whether the corporate egress IP is accurate does not change that account-wide policy; an address in an otherwise valid IP firewall rule cannot reopen the disabled public endpoint. Rechecking NAT without identifying the public-network-access state would therefore miss the root cause. Restoring a supported private path is a separate authorized network-design task, and no change is authorized by this diagnostic question.

C:

Azure Storage service endpoints identify an approved VNet subnet when a storage account still permits selected traffic to its public service endpoint. They are not a Private Link connection and do not produce a dedicated private endpoint IP on the account. With the account's public network access Disabled, adding a subnet service endpoint does not override the account-wide restriction. That distinction is the precise diagnostic boundary tested here. If the team later approves private access, it must use a compatible private endpoint path and resolve the service name appropriately; a public service-endpoint allowlist alone is insufficient.

D:

A Storage Blob Data Reader assignment permits particular Blob read operations after the client has a permitted network path and valid authentication. Azure RBAC does not grant an exception to a storage account's Disabled public network access property. The denied request can therefore be caused by the public endpoint network setting even though the user's data role is correct. The account need not be corrupt, and assigning broader RBAC privileges would expand permission without solving connectivity. A sound diagnosis separates network access rules from data-plane authorization and identifies the disabled public endpoint as the immediate blocker.

Question 119

A subnet accesses a storage account over the Azure Storage public service endpoint. The account firewall must permit ONLY that subnet, and the design explicitly forbids private endpoints. What configuration completes the permitted network path?

  1. Add the subnet RFC1918 address as a public IP firewall rule and leave service endpoints disabled.
  2. Enable the Microsoft.Storage service endpoint on the subnet and allow the subnet in the storage account virtual-network rules.
  3. Disable the storage firewall and rely only on the subnet address.
  4. Create a private endpoint and remove the existing service-endpoint model.

Explanation

Correct Answer

B:

The service endpoint provides the supported subnet identity path to the service endpoint; the matching storage network rule grants the specified subnet access. Storage data authorization remains a separate requirement.

Incorrect Answers

A:

The public-IP rules are not the mechanism for identifying a permitted VNet subnet via a service endpoint.

C:

That broadens access beyond the requested subnet and violates the explicit firewall restriction.

D:

The question expressly forbids private endpoints; that is a different connectivity architecture.

Question 120

A critical Azure service needs storage access despite restrictive network rules. What should be examined before choosing broad exceptions?

  1. Check whether that trusted Azure service is explicitly supported by the storage firewall exception
  2. Grant the calling service a Blob Data Reader role and treat that role as equivalent to an authorized storage firewall exception.
  3. Enable a Microsoft.Storage service endpoint on an unrelated network subnet and assume that creates a trusted-service exception for the calling Azure service.
  4. Add the entire subscription to a generic firewall exception list without checking whether the requesting Azure service supports trusted-service bypass.

Explanation

Correct Answer

A:

The question concerns a service trying to access an Azure Storage account through restrictive firewall rules. A trusted Azure-services bypass is not blanket access for all Azure-hosted workloads: Microsoft documents which services and scenarios qualify, and the data-plane caller still needs authorization. Before allowing such an exception, identify the exact Azure service, its supported trusted-service operation, and the storage account firewall setting. If the service is ineligible, build a supported narrowly scoped private endpoint or VNet path instead; do not assume adding Blob Data Reader or a rule for an unrelated subnet changes the network authorization result. This is why checking eligibility for the specific service is the decisive first action.

Incorrect Answers

B:

A Blob Data Reader role authorizes a principal for particular data-plane reads, but it does not open a storage account firewall or classify the principal as a trusted Azure service. The request says a critical Azure service must get through restrictive network rules, and the administrator is considering a special firewall exception. Verify that this specific service and operation are actually listed as eligible for the trusted-services exception, then separately validate identity authorization. A broad data role alone leaves a blocked network route unchanged and increases privilege without fixing it.

C:

Service endpoints identify permitted subnets for storage firewall virtual-network rules; they do not classify every Azure service as eligible for the trusted-services bypass setting. Applying an endpoint on a subnet unrelated to the caller cannot authorize the caller's actual network path. The case is specifically about checking whether a critical Azure service qualifies for a trusted Azure services firewall exception before permitting broader access. Confirm that exact service and operation on the documented list, or design a verified private/network path; do not substitute a generic endpoint on another subnet for a supported exception.

D:

Trusted-services exceptions are scoped to documented Azure service scenarios rather than every workload in a subscription. Adding a broad conceptual subscription exception does not establish a supported network path for the calling service, and it undermines the restrictive firewall requirement. The first decision in this scenario is eligibility: identify the exact service identity and the storage operation and confirm the current trusted Azure services matrix. Only then consider a supported narrow network exception and the separate Blob DataActions required by the application.


Microsoft Azure Administrator (AZ-104) Practice Tests

Purchase Individually

AZ-104 Premium File

Premium File
AZ-104 Premium File
606 Q&A
$76.99$69.99

AZ-104 Training Video Course

Training Course
AZ-104 Training Video Course
132 Lectures
$27.49$24.99

AZ-104 Study Guide

Study Guide
AZ-104 Study Guide
458 PDF Pages
$27.49$24.99

Site Search:

 

VISA, MasterCard, AmericanExpress, UnionPay

SPECIAL OFFER: GET 10% OFF

ExamCollection Premium

ExamCollection Premium Files

Pass your Exam with ExamCollection's PREMIUM files!

  • ExamCollection Certified Safe Files
  • Guaranteed to have ACTUAL Exam Questions
  • Up-to-Date Exam Study Material - Verified by Experts
  • Instant Downloads
Enter Your Email Address to Receive Your 10% Off Discount Code
A Confirmation Link will be sent to this email address to verify your login
We value your privacy. We will not rent or sell your email address

SPECIAL OFFER: GET 10% OFF

Use Discount Code:

MIN10OFF

A confirmation link was sent to your e-mail.
Please check your mailbox for a message from support@examcollection.com and follow the directions.

Next

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.