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 72

Question 710

An engineer enabled the Microsoft.Storage service endpoint on subnet app-subnet and added that subnet to a storage firewall allowlist. The storage endpoint still resolves to an Azure public service IP. Security now requires clients to connect through a private IP address allocated inside the VNet. Which design change meets that stricter network requirement?

  1. Create an appropriate Storage private endpoint and private DNS mapping; service endpoints alone do not assign a private IP to the PaaS endpoint.
  2. Keep only the existing service endpoint and update a subnet NSG with the Storage service tag, which forces public DNS to return a private address.
  3. Assign a public IPv4 address to the VNet subnet so the storage account endpoint will automatically become a private-IP listener.
  4. Change storage redundancy to geo-zone-redundant storage and assume the storage FQDN then resolves to the VNet gateway address.

Explanation

Correct Answer

A:

Azure service endpoints extend VNet identity to supported Azure PaaS services while the service endpoint retains public service IP addressing. A private endpoint is the mechanism that presents an approved service subresource at a private IP on a NIC in the selected VNet. The administrator should create that connection, configure relevant private DNS resolution, and validate the allowed route before closing unwanted public access paths. Service endpoint firewall rules alone do not satisfy the new private-address requirement.

Incorrect Answers

B:

NSGs and service tags can influence allowed traffic, but they cannot transform a storage service public endpoint into a VNet private IP. The service endpoint remains a supported network identity/routing approach using service public addresses. Private Link and private DNS are required for a private endpoint design.

C:

Allocating a public IP address to another resource does not cause an Azure Storage service FQDN to resolve to a private IP. Storage is a platform service with its own endpoint. A private endpoint must be created and approved for the relevant Storage service subresource.

D:

Storage redundancy protects data across infrastructure locations; it does not determine whether clients address a private endpoint or a public Storage service IP. GZRS can be appropriate for availability, but it cannot reconfigure a VNet DNS response into a private network interface.

Question 711

Azure Storage account `stfinance` belongs to tenant A and uses Enabled from selected networks. An approved external team operates subnet `sn-partner` in tenant B; the subnet already has a supported Microsoft.Storage service endpoint and both tenant administrators have authorized the cross-tenant VNet rule. The tenant-A storage administrator cannot find sn-partner in the Azure portal virtual-network picker. Which supported approach permits this subnet without relaxing the storage firewall to All networks?

  1. Leave the account unchanged and give tenant-B users Azure Reader; a Reader role automatically creates network allow rules after sign-in.
  2. Turn off selected-network restrictions and distribute an account SAS to every tenant-B application; the account SAS alone will enforce source subnet admission.
  3. Use Azure PowerShell or Azure CLI to add the permitted subnet resource ID as a virtual network rule for stfinance, with the requisite cross-tenant subnet authorization, and keep selected-network access enabled.
  4. Create a public IP firewall rule for the tenant-B subnet private CIDR instead of a virtual-network rule; private source addresses are the correct client IP ranges for service-endpoint rules.

Explanation

Correct Answer

C:

Microsoft documents that a storage account selected-networks virtual-network rule may refer to a subnet in another Microsoft Entra tenant, but the Azure portal picker does not display other-tenant subnets. With approved cross-tenant access and suitable subnet permissions, use Azure CLI or PowerShell to specify the exact subnet ID and retain the service endpoint and storage network restriction.

Incorrect Answers

A:

Azure Reader is a control-plane viewing role and does not add a storage account virtual-network rule. A subnet already using a Microsoft.Storage service endpoint still requires the destination storage resource to permit that subnet on its network allowlist.

B:

An account SAS provides signed access to eligible Storage operations, not an Azure Storage network firewall boundary. Disabling selected networks would expose the storage endpoint to other networks even if an individual SAS is constrained, contrary to the stated private-subnet-only policy.

D:

Storage service endpoint requests are evaluated using the approved subnet identity, with private source network routing; a rule constructed from the subnet’s private RFC1918 CIDR is not the supported cross-tenant VNet firewall rule. Use a virtual-network rule against the subnet resource ID.

Question 712

A managed Azure PaaS resource supports Azure Private Link, but its service type has no virtual network service endpoint. An application VM must reach only that approved resource by a VNet private IP, with public ingress disabled and normal service authentication retained. Which connectivity pattern satisfies all three requirements?

  1. Create an approved private endpoint for the specific PaaS resource, configure its private DNS resolution, and retain resource-side access controls.
  2. Enable the Microsoft.Storage service endpoint on the application subnet, although the target PaaS service is not Storage and exposes no service-endpoint type.
  3. Create an NSG outbound Allow with the VirtualNetwork service tag and assume that rule creates a private endpoint NIC for the PaaS service.
  4. Enable an Azure Firewall application rule to the PaaS public hostname while leaving the PaaS service public endpoint accessible.

Explanation

Correct Answer

A:

Private Link maps an eligible individual PaaS resource to a private IP in the VNet; correct private name resolution sends the ordinary service FQDN to that address. Authentication and PaaS-side access controls still apply, so private routing is not treated as permission.

Incorrect Answers

B:

Service endpoints are supported only for defined Azure service providers and leave a PaaS public destination IP in use. Enabling Microsoft.Storage cannot provide the private-IP interface of an unrelated service without a supported endpoint type.

C:

An NSG controls packet admission to existing network addresses; a service tag does not allocate a private endpoint NIC or replace Private Link. The resource still needs a private endpoint plus DNS and access policy.

D:

Azure Firewall can filter application traffic, but a public service URL behind a public endpoint does not meet the stated private-IP-only destination with public ingress disabled. It also does not instantiate a Private Link connection.

Question 713

A subnet has a 0.0.0.0/0 UDR through an NVA. A network engineer enables a Storage service endpoint and notices Storage-bound traffic takes a more specific service route. What should be checked?

  1. Validate the endpoint-added effective routes and storage network firewall policy before assuming all traffic still traverses the NVA.
  2. Remove the storage account encryption keys because service endpoints disable key requirements.
  3. Change only the DNS CNAME and assume endpoint routing is unchanged.
  4. Treat 0.0.0.0/0 as more specific than every Azure service prefix.

Explanation

Correct Answer

A:

Service endpoint routes can be more specific than a forced-tunnel default route; the effective route and destination policy must be verified.

Incorrect Answers

B:

Service endpoints are network controls and do not eliminate storage authentication.

C:

DNS aliases cannot determine the winning longest-prefix route for Azure Storage destinations.

D:

A default /0 is less specific than a matching Azure service endpoint prefix.

Question 714

An application on premises, connected to an Azure VNet over ExpressRoute private peering, must reach a Storage account without using its public endpoint. What connection design fits?

  1. Use a Storage service endpoint on the on-premises subnet, which is directly supported.
  2. Deploy an eligible Storage private endpoint in Azure and route private traffic from on premises with the necessary DNS forwarding.
  3. Enable a service endpoint on a public IP resource attached to on-prem routers.
  4. Create a public Blob container and deny all authenticated users.

Explanation

Correct Answer

B:

A private endpoint exposes an Azure VNet private IP accessible through supported hybrid routing with correct DNS.

Incorrect Answers

A:

VNet service endpoints are scoped to supported Azure VNet subnets, not arbitrary on-premises networks.

C:

An on-prem router public IP cannot be delegated as an Azure VNet service endpoint subnet.

D:

Anonymous public Blob access conflicts with the private-only resource requirement.

Question 715

An application subnet in East US needs service-endpoint-based access to an Azure Storage account in West Europe. The VNet and storage account are in nonpaired regions; policy requires keeping the storage public service-endpoint model, not deploying a private endpoint. The target storage firewall already allows the source subnet, and the application has valid data authorization. Which supported subnet endpoint change enables the required cross-region service-endpoint scope?

  1. Replace the regional Microsoft.Storage endpoint with Microsoft.Storage.Global on the subnet and retain the approved storage virtual network rule.
  2. Keep only Microsoft.Storage because that regional endpoint automatically covers every Azure region worldwide.
  3. Add Microsoft.Sql to the subnet so the Storage account treats the SQL endpoint as equivalent to Microsoft.Storage.Global.
  4. Enable Microsoft.Storage and Microsoft.Storage.Global concurrently on the same subnet to combine regional and global routes.

Explanation

Correct Answer

A:

Microsoft.Storage.Global provides cross-region service endpoint connectivity to Azure Storage accounts in any region. The subnet may have either Microsoft.Storage or Microsoft.Storage.Global, not both, and the resource-side network allow rule and data authorization remain necessary.

Incorrect Answers

B:

Microsoft.Storage is the regional endpoint type and does not promise service-endpoint support for arbitrary nonpaired remote regions. The stated cross-region reach requires the supported global endpoint type.

C:

Microsoft.Sql is a different service endpoint provider used for supported SQL destinations. It does not create Storage service-endpoint connectivity or substitute for Microsoft.Storage.Global.

D:

Azure does not permit Microsoft.Storage and Microsoft.Storage.Global to be configured together on one subnet. The regional endpoint must be removed when switching to the global endpoint type.

Question 716

A Storage account firewall allows a specific VNet subnet by a virtual network rule, but a VM in that subnet gets network denied on the Storage public endpoint path. What must be checked?

  1. Reset the storage SAS permissions before checking any routing or firewall settings.
  2. Disable VNet service endpoint support because all selected-network rules require public anonymous access.
  3. Inspect the subnet’s Storage service endpoint configuration and the storage network-rule scope for the intended service.
  4. Grant VM Contributor on the subscription and bypass storage firewall rules.

Explanation

Correct Answer

C:

When using service-endpoint-based Storage VNet allow rules, the source subnet must have the supported endpoint and corresponding destination rule.

Incorrect Answers

A:

Valid SAS permissions cannot override a storage network rule rejecting the client subnet.

B:

Storage selected-network rules do not require anonymous Blob access.

D:

Azure management-plane Contributor rights do not bypass Storage account data-plane networking restrictions.

Question 717

Storage account `stsecure` uses public network access Enabled from selected networks and permits subnet `app` through its Microsoft.Storage service endpoint. An audit discovers the account also has the AzureServices trusted-service network exception enabled, which allows eligible authenticated Azure services from outside approved VNet subnets. Compliance now requires network admission only from the explicitly allowed subnet, with no trusted-service bypass or other firewall exceptions. What should the administrator change?

  1. Delete the app subnet’s Microsoft.Storage service endpoint so the storage account no longer accepts any trusted Azure services.
  2. Grant the app workload a new Storage Blob Data Reader role, expecting that role to cancel the trusted-service firewall exception.
  3. Change the storage account public network scope to All networks, leaving its existing trusted-service exception in place.
  4. Remove the AzureServices trusted-service network exception (and confirm no other bypass exceptions), keeping the selected-network rule for app.

Explanation

Correct Answer

D:

Trusted service exceptions are separate from the allowlisted virtual network rules. Removing the AzureServices bypass in the storage network settings, while keeping the approved subnet and checking other exceptions, satisfies the strict network admission boundary without changing data permissions.

Incorrect Answers

A:

The source service endpoint is how the approved application subnet reaches Storage in this design; removing it would disrupt legitimate clients and would not remove a separate account-level trusted-service firewall exception.

B:

Blob data roles control authenticated data operations and do not disable storage networkRuleSet bypass values. Additional data RBAC cannot tighten the trusted-service network admission exception.

C:

All networks removes the selected-network boundary entirely. It broadens access to any client with permitted authorization rather than restricting network admission to the single approved subnet.

Question 718

Azure Storage account `stshared` allows service-endpoint traffic from subnets `team-a` and `team-b` through two explicit virtual network firewall rules. Access from team-a must be revoked for every VM there, but team-b must remain connected. The security review specifically requires updating the destination account network policy, not merely changing client routes or identities. Which change meets that scope?

  1. Remove the Microsoft.Storage service endpoint from both team-a and team-b subnets and keep both storage firewall rules.
  2. Create an NSG outbound Deny for the regional Storage service tag on team-a and leave the storage account virtual network rule in place.
  3. Remove a Storage Blob Data Reader grant from one team-a VM identity, leaving other team-a identities and the network rule unchanged.
  4. Delete only team-a’s virtual-network allow rule from the storage account firewall, preserving team-b’s rule.

Explanation

Correct Answer

D:

Removing team-a’s explicit VNet subnet rule from the storage account revokes that source subnet’s selected-network permit while retaining team-b’s independent rule. The subnet endpoint can remain enabled for other permitted Storage destinations.

Incorrect Answers

A:

Disabling both source subnet endpoints would interrupt the approved team-b network, violating the narrow-revocation requirement. It also leaves the destination firewall allow rules unchanged.

B:

An NSG egress Deny at the source is a different, broader network filter and does not update the destination account’s approved subnet list as explicitly required. It can also block other Storage access unrelated to stshared.

C:

Azure Blob RBAC can revoke one identity’s data permissions but does not remove the subnet network source permission, and other team-a identities could still use the allowed path. This cannot revoke the subnet’s authorization at the destination network policy.

Question 719

A VNet subnet hosts one service using Azure Storage and another using Azure SQL, and both resources use supported selected-subnet firewall rules. What should the administrator configure?

  1. Enable only the Microsoft.Storage endpoint and assume it authorizes Microsoft.Sql.
  2. Create a private endpoint to an unrelated Key Vault resource as the single network control.
  3. Use a public IP on every workload VM and leave both PaaS firewalls open.
  4. Configure each supported service endpoint type and the corresponding Storage/SQL destination-side network rules.

Explanation

Correct Answer

D:

Each target service has its own supported endpoint and firewall configuration to permit the approved subnet.

Incorrect Answers

A:

Microsoft.Storage does not automatically include Azure SQL service endpoint identity.

B:

A Key Vault endpoint does not grant the subnet access to Storage and SQL resources.

C:

Public VM addresses and All networks access violate the selected-subnet requirement.

Question 720

A new Azure SQL Database private endpoint has been requested but its connection remains Pending approval. Meanwhile, VM clients in vnet-payroll continue to resolve sql-payroll.database.windows.net to a public address because their VNet has no link to the private endpoint DNS zone. Which TWO independent configurations must be completed? Select TWO answers.

  1. Approve the pending private endpoint connection for the intended Azure SQL logical server.
  2. Change SQL client connection strings from the server FQDN to the private endpoint IP address.
  3. Enable Microsoft.Sql service endpoints instead of completing the private endpoint connection.
  4. Link vnet-payroll to the privatelink.database.windows.net private DNS zone with the correct endpoint record.
  5. Enable the logical server option to allow public Azure service access and skip private DNS integration.

Explanation

Correct Answers

A:

A pending private endpoint connection is not an approved private path to the SQL resource. An authorized owner must confirm that the request targets the right SQL server and approve it so the connection reaches the approved state. This resolves the connectivity authorization half of the problem. Approval alone cannot make VM DNS use the endpoint’s private IP; the client VNet must also see the associated private DNS records.

D:

Azure SQL Database private endpoints use the private zone privatelink.database.windows.net. Linking the client VNet and ensuring its A record targets the endpoint IP allows the normal sql-payroll.database.windows.net lookup to resolve privately through the expected CNAME chain. This fixes the separate DNS defect identified in the stem. DNS alone cannot approve a Pending private endpoint, so the matching endpoint approval remains necessary before reliable application connections.

Incorrect Answers

B:

For Azure SQL Database, connection strings should continue to use the normal logical-server FQDN, not the raw private endpoint address. SQL Gateway routing and certificate validation depend on the proper name. Direct-IP connection attempts can fail even when the private endpoint is healthy. Correct the name resolution and endpoint approval while leaving clients on the supported server DNS name.

C:

Service endpoints use a different routing and firewall mechanism and do not approve an outstanding Private Link connection. The requirement explicitly calls for the new SQL private endpoint, and its Pending state remains unresolved by switching to a public service-endpoint path. This choice also leaves the reported private-zone DNS failure in place.

E:

Allowing public Azure services can create an additional public ingress route rather than repair the private connection. It neither approves the Pending endpoint request nor provides the private DNS mapping required for VNet clients. The business requirement is specifically to use the private endpoint; exposing public connectivity as a workaround contradicts the intended network boundary.