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 23

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.

Question 221

An on-premises client uses 10.25.14.7 internally and reaches the internet through enterprise NAT. An administrator tries to add 10.25.14.7 as an Azure Storage IP firewall allow rule. Why is this incorrect?

  1. Private IPv4 addresses can be added as Storage Blob Data Reader role assignments.
  2. Switch the storage account redundancy from LRS to GRS before entering 10.25.14.7.
  3. Azure Storage requires every on-premises workstation to use a publicly routable NIC address.
  4. Storage IP rules expect eligible public IPv4 source addresses; use the actual NAT egress or a supported private endpoint connection.

Explanation

Correct Answer

D:

Azure Storage firewall IP rules cannot be used to authorize arbitrary RFC1918 private IPv4 addresses as if they were public client origins. The storage service normally sees the enterprise's translated public source when reached over the public endpoint. Configure an eligible public NAT egress rule if policy allows, or establish approved private connectivity and a private endpoint. Separately validate SAS or Microsoft Entra authorization; the private internal address alone does not satisfy the network filter.

Incorrect Answers

A:

Azure RBAC assignments target security principals such as users, groups and managed identities, not network interface IPv4 addresses. It cannot convert the internal client IP into an access grant. Storage authorization and network filtering must each be configured using their own supported identity and network mechanisms.

B:

Data redundancy changes how storage replicates its contents and does not make private IPv4 source addresses valid public firewall rules. The invalid rule reflects the mismatch between the internal RFC1918 address and Azure's public origin filtering. Check the actual NAT or private path instead.

C:

A client can remain on a private enterprise network and reach Azure through NAT or private connectivity. The limitation concerns the public storage firewall's source IP rule format and visibility, not a universal requirement to readdress workstations. Use supported egress or Private Link configuration rather than changing the client's local NIC.

Question 222

An Azure administrator enables public network connectivity to a storage account for an approved consumer, but security requires that blobs never become anonymously readable. Which distinction matters?

  1. Public network reachability and anonymous blob data access are separate settings; disable anonymous access and still authorize data requests.
  2. Assigning the Azure subscription Reader role disables anonymous blob access for all containers.
  3. Choosing ZRS automatically blocks anonymous blob reads.
  4. Turning on public network access automatically makes every blob publicly readable without credentials.

Explanation

Correct Answer

A:

Storage network accessibility controls whether clients can reach a service endpoint, while anonymous blob access settings determine whether unauthenticated content reads are permitted. Allowing network connections does not automatically grant anonymous read permission, but administrators should explicitly enforce the account's anonymous-access policy and use Microsoft Entra or scoped SAS for authorized access. Confirm container-level configuration and any account-wide anonymous access prohibition rather than relying solely on firewall settings.

Incorrect Answers

B:

Reader allows viewing Azure management metadata and does not enforce a storage account's anonymous blob access setting. A user's RBAC role is not a replacement for the data service's anonymous authorization controls. Configure the storage account and container policies directly and test unauthenticated requests.

C:

Zone-redundant storage replicates data across availability zones to improve durability and resiliency. It does not determine whether a blob container permits anonymous HTTP requests. Use dedicated anonymous-access restrictions to enforce that security requirement, independent of the account redundancy choice. Azure authorization and networking are independent of how the account replicates content.

D:

Opening the network route is not equivalent to changing container anonymous read permissions or account-level anonymous-access policy. Clients can reach the endpoint yet still be refused by authentication and authorization checks. Security should verify both layers independently and disable anonymous blob access as intended.

Question 223

An Azure VM in subnet data-a needs to reach a storage account configured to permit a designated VNet through the public service endpoint. There is no private endpoint. Which TWO changes establish that network path? Select TWO answers.

  1. Deploy an Azure DNS Private Resolver without changing the firewall.
  2. Assign subscription Owner to the VM's managed identity.
  3. Enable the Microsoft.Storage service endpoint on subnet data-a.
  4. Enable anonymous public blob access on the storage account.
  5. Add subnet data-a as an allowed virtual network in the storage account's firewall settings.

Explanation

Correct Answers

C:

A Microsoft.Storage service endpoint identifies traffic originating from the Azure subnet to the Azure Storage public service endpoint using the virtual-network service endpoint capability. This configuration is made on the source subnet, not by changing a VM's RBAC roles. It is part of allowing a selected Azure VNet to access the storage public endpoint. The account must separately include a matching virtual network rule to accept that subnet as an allowed source.

E:

The storage account's selected-network firewall denies traffic from sources that are not explicitly authorized. Adding data-a to its virtual network rules provides the account-side permission for the service-endpoint-enabled subnet. This rule complements the subnet's Microsoft.Storage service endpoint configuration; neither role assignments nor private DNS alone substitute for the VNet rule. A valid credential or applicable data role is still required after network admission succeeds.

Incorrect Answers

A:

Azure DNS Private Resolver helps resolve DNS queries across hybrid or virtual-network environments, but it does not mark a subnet as permitted by the storage firewall's selected virtual network rules. The stated architecture uses the public storage endpoint with a service endpoint, not a private endpoint. Update the subnet and account-side rules instead.

B:

Owner grants broad resource-management and role-grant authority but does not add a virtual network rule or enable the subnet service endpoint. The task is to admit traffic from one selected Azure subnet to the storage public endpoint. Providing the VM more Azure permissions would not resolve the missing network configuration and violates least privilege.

D:

Anonymous access affects authorization for eligible blob content, not identification of a source subnet under selected-network firewall rules. It could expose data while the required virtual-network admission still fails. Configure the subnet's Microsoft.Storage service endpoint and add its VNet rule without relaxing container access protections.

Question 224

A storage Blob private endpoint was created successfully, but a VM in its linked VNet still resolves the normal blob hostname to a public IP. Data roles are correct. Which issue should be investigated first?

  1. Regenerate both account access keys to update the private endpoint name.
  2. Private DNS zone integration, the privatelink.blob.core.windows.net records, and VNet links used by the VM resolver.
  3. Disable all NSG rules on the VNet permanently.
  4. Replace Blob Data Reader with Blob Data Owner on the VM's identity.

Explanation

Correct Answer

B:

Private endpoints require clients to resolve the storage service hostname to the intended private endpoint IP through a suitable DNS path. Check that the relevant private DNS zone and A record exist, the source VNet or resolver can query the zone, and any custom DNS forwards Private Link queries correctly. Azure RBAC has no role in translating a hostname into a private address. Fix DNS and retest name resolution before changing data permissions.

Incorrect Answers

A:

Account keys sign storage requests and do not configure the DNS record used to reach a private endpoint. Rotating them could break existing applications without changing the public IP answer from the VM's resolver. Repair Private Link DNS integration instead of altering credentials.

C:

An NSG may affect traffic reachability after resolution, but it does not by itself supply the private DNS records required for Private Link hostname translation. Removing network filtering broadly would create security exposure. Diagnose the DNS zone and resolver linkage first, then check effective traffic rules if necessary.

D:

Data-plane role elevation cannot change DNS answers from the storage public endpoint to its private endpoint IP. The identity already has the required permissions and the observed failure is in hostname resolution. Broadening the role would add unnecessary data privilege while leaving the actual private-path problem untouched.

Question 225

Storage account stpay already has an approved Blob private endpoint reachable from vnet-private. An audit found that the application still resolves stpay.blob.core.windows.net to a public address, and the storage account’s public network access is Enabled. Security requires private DNS resolution and the public endpoint to reject all connections. Which TWO configuration fixes address these findings? Select TWO answers.

  1. Upgrade stpay from locally redundant storage to geo-redundant storage as a substitute for private networking.
  2. Link the client VNet to the correct Blob Private DNS zone and ensure its record maps stpay to the existing endpoint’s private IP.
  3. Grant subscription Owner to every application identity so public DNS returns a private IP.
  4. Enable anonymous Blob access on the account and rely on container visibility to reject public traffic.
  5. Disable public network access on stpay after confirming the private endpoint works.

Explanation

Correct Answers

B:

Private endpoints use service-specific DNS mappings; Blob storage expects the privatelink.blob.core.windows.net zone and corresponding endpoint private address. A proper record and VNet link make the normal stpay.blob.core.windows.net name resolve privately for eligible clients, which fixes the documented DNS finding without changing application URLs. The private endpoint is already present, so creating another endpoint is unnecessary; the missing part is correct client-side name resolution.

E:

Setting Public network access to Disabled causes the storage service’s public endpoint to reject client connections. Existing approved private endpoint traffic remains the intended path, provided the endpoint and required DNS are correctly configured. Perform the private resolution check before disabling public access so legitimate application calls continue over the private IP. This is distinct from repairing DNS: both the source of the address and the allowed network endpoint must satisfy the audit.

Incorrect Answers

A:

Storage redundancy determines how data replicas are kept across fault domains or regions. It does not switch the network endpoint to a private IP, repair DNS, or stop connections to the public storage endpoint. The audit identifies two networking misconfigurations that must be fixed independently of the account’s redundancy choice.

C:

Subscription Owner is a control-plane authorization role, not a DNS or virtual-network routing configuration. Assigning it broadly would unnecessarily increase privilege and would not change the public address returned for stpay.blob.core.windows.net. Authorization and network endpoint selection are separate concerns; use private DNS and storage network settings for this scenario.

D:

Anonymous Blob access affects whether some Blob data can be requested without credentials, not whether the public network endpoint accepts traffic. Enabling anonymous access would worsen security and still leave the public endpoint reachable. Security explicitly requires rejecting public connections, which is controlled through the account’s public network access configuration.

Question 226

A customer receives a valid read-only SAS for a restricted storage account. The customer gets HTTP 403 when connecting from a home internet connection that is not in the account firewall allowlist. What should the administrator do?

  1. Regenerate the SAS with both write and delete permissions added.
  2. Keep the SAS permissions scoped and provide an approved network route or narrow firewall allowance for the customer.
  3. Switch the blob access tier from Cool to Hot.
  4. Assign subscription Owner to the SAS recipient.

Explanation

Correct Answer

B:

A SAS delegates data operations and validity conditions, but an Azure Storage firewall can deny the request even when its signature and permissions are valid. Check the caller's actual source network, storage account selected-network rules and required service endpoint or Private Link path. If business policy permits, authorize the specific customer egress or approved private connection. Do not increase SAS privileges to overcome a network restriction; the denial occurs at a different enforcement layer.

Incorrect Answers

A:

The customer is attempting a read, and the existing SAS already has suitable read permission. Granting write and delete would increase destructive data capabilities while the storage firewall continues to deny the unapproved source network. Resolve the network allowlist or connectivity boundary instead of expanding SAS operations.

C:

Blob access tier affects storage economics and access latency/cost, not the storage account's source IP firewall decision. A home internet connection outside the allowlist remains denied regardless of whether the object is stored as Hot or Cool. Investigate network restrictions, not the blob tier.

D:

A SAS is a signed delegated token and does not require the recipient to be an Azure subscription Owner. Granting subscription ownership would expose unrelated Azure resources and still is not a direct substitute for a storage account network allow rule. Keep scoped SAS and correct connectivity.

Question 227

A company has configured a private endpoint for a storage account's Blob service. A separate application must mount Azure Files over a private endpoint, but its DNS still returns a public file endpoint. Which TWO actions are required? Select TWO answers.

  1. Grant every file user Storage Blob Data Owner.
  2. Replace the Azure Files share with a public Blob container without changing DNS.
  3. Create or approve a private endpoint for the storage account's File subresource.
  4. Configure the private DNS record and VNet linkage for privatelink.file.core.windows.net.
  5. Assume the Blob endpoint's private DNS record automatically aliases all storage service endpoints.

Explanation

Correct Answers

C:

Azure Storage private endpoints are created for specific storage service subresources such as Blob or File. An existing Blob private endpoint does not automatically provide private endpoint connectivity for Azure Files. Provision a File private endpoint on a reachable network segment with the correct network policies and routing. This separate endpoint supplies the private IP destination for file service requests rather than reusing the Blob endpoint.

D:

File service clients need their storage account file hostname to resolve to the File private endpoint's private address. The Blob private DNS zone serves a different endpoint namespace and cannot substitute for the file service zone. Link the appropriate private zone to the workload network or configure equivalent custom DNS forwarding and verify the File A record. This makes the correct private IP reachable through normal hostname resolution.

Incorrect Answers

A:

Storage Blob Data Owner is a Blob service role, not a network or Azure Files private endpoint configuration. It would unnecessarily extend data permissions and still leave the file hostname resolving to a public address. Fix the File endpoint and its private DNS first, then verify separate share-access authorization.

B:

Blob and Azure Files provide different access protocols and semantics; substituting an object container would not preserve the application's SMB file-share requirement. It also would not create a private endpoint for the File service. Provision the required File subresource endpoint and DNS resolution instead.

E:

Azure Storage service hostnames and private-link DNS zones are service-specific. A blob private DNS record does not automatically resolve the file.core.windows.net hostname to an appropriate File private endpoint. The file application requires a File private endpoint and matching private DNS configuration, not an assumption about cross-service aliasing.

Question 228

Storage firewall rules permit requests from subnet sn-one, but a new workload is deployed in another VNet's subnet sn-two. The workload has correct blob RBAC but storage requests are network denied. Which change best addresses the cause?

  1. Give sn-two's workload subscription Owner rights.
  2. Provide an approved network path for sn-two and explicitly allow its eligible subnet/service endpoint or private endpoint connection.
  3. Disable storage auditing to reduce the denied-request counter.
  4. Copy the sn-one subnet address prefix into the workload's RBAC assignment name.

Explanation

Correct Answer

B:

Storage VNet rules are applied to eligible source subnets, not automatically to every subnet belonging to the same company or subscription. The new workload originates from sn-two, which is outside the existing allowed network rule. Configure the supported service-endpoint/network rule for that subnet or establish an appropriate Private Link route, consistent with security policy. The identity's existing Blob RBAC does not override the storage firewall, so changing it is not the first remedy.

Incorrect Answers

A:

Subscription Owner is an ARM administrative role; it does not automatically add a new VNet subnet to the storage account's firewall allowed networks. It would create unnecessary resource and role-management access while leaving the network denial in place. Fix the source network route and firewall rule instead.

C:

Turning off logs can hide useful diagnostic evidence but cannot make an unpermitted subnet able to reach the account. The denial persists because the network rule does not cover the workload's actual source. Preserve monitoring and correct the approved source subnet configuration.

D:

Azure RBAC grants reference principals, roles and scopes; assigning a display name that contains a subnet prefix does not make storage firewall rules match packets. The account evaluates actual network origin and selected-network settings. Add an eligible sn-two network route and allowance rather than editing labels.

Question 229

An upload agent must write exactly one target blob into Azure Storage during a twenty-minute window. The client has no other data operations and security forbids permanent credentials. Which access method is appropriate?

  1. Give the upload agent the account's primary access key with a promise not to reuse it.
  2. Enable anonymous write access on the container for twenty minutes.
  3. Assign Storage Blob Data Owner to the agent at subscription scope indefinitely.
  4. Generate a blob-scoped SAS that grants only the needed create/write operation and expires after the short window.

Explanation

Correct Answer

D:

A Shared Access Signature can delegate narrowly specified operations on a storage resource for a limited validity period. Issue a token scoped to the intended blob, with only its necessary write or create permissions and a short expiry, preferably using Microsoft Entra-backed user delegation when supported and suitable. Distribute the URL securely and retain normal storage network restrictions. A scoped token avoids exposing a full storage account key for a one-time upload.

Incorrect Answers

A:

A storage account key is a powerful shared secret that can authorize broad operations and is not limited to the stated blob or twenty-minute window. A promise does not enforce least privilege or expiration. Use an appropriate narrowly scoped SAS rather than handing the recipient the account's master credential.

B:

Anonymous blob container settings are not a supported substitute for a secure one-time authenticated write operation. Exposing an unauthenticated upload surface would be unnecessary and dangerous, and the requirement is for explicitly delegated access. Issue a signed token with narrow permissions and expiry rather than opening anonymous writes.

C:

Subscription-scoped Blob Data Owner provides extensive ongoing data privileges, including operations beyond writing a single blob. It violates both scope and lifetime requirements and may allow access to unrelated storage accounts. A short-lived blob-scoped SAS supplies the needed delegated capability without persistent broad RBAC.

Question 230

A partner must list documents in one Blob container and download selected blobs for the next two days. The partner cannot edit or delete data. What delegation should be issued?

  1. Storage Blob Data Contributor over the entire subscription for one year.
  2. A SAS allowing only write permission because downloading counts as a storage write.
  3. A shared account key that the partner can use to browse every container.
  4. A container-scoped SAS granting read and list for only the approved validity period.

Explanation

Correct Answer

D:

To enumerate blobs in a container, the delegated operation needs list permission, while downloading blob contents requires read permission. A SAS can constrain both operations to the selected container and expire after the authorized period. Avoid write, delete and account-wide resource types because the partner should not modify data or inspect unrelated datasets. If the storage firewall restricts external clients, provide an approved network path as a separate prerequisite.

Incorrect Answers

A:

A broad contributor role permits writes and deletes and may extend to other accounts in the subscription. It is inconsistent with temporary read-only partner access. Use SAS read/list permissions at the specific container scope for the intended two-day period. The authorized task is confined to a single container.

B:

Downloading a blob is a read operation, and listing container members requires list permission. A token with write only would fail those requested operations while granting an unneeded mutation capability. Generate a container-scoped read/list SAS rather than trying to compensate with broader access.

C:

Account keys confer broad authority over supported storage services and are inappropriate for limited partner access to one container. The partner's activities and lifetime can be enforced by a scoped SAS, avoiding long-lived credentials that are difficult to contain if leaked.