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 73

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.

Question 721

An application must privately access both Blob and Azure Files endpoints on one Storage account. What Private Link resource design is needed?

  1. One Blob endpoint automatically also covers every File subresource and hostname.
  2. Only an Azure DNS CNAME change without any private-endpoint connections.
  3. A VM public IP attached to the storage account namespace.
  4. Separate appropriate Blob and File private endpoints with their required private DNS mappings.

Explanation

Correct Answer

D:

Both Storage Blob and File private access require the respective subresource private connection paths and name resolution.

Incorrect Answers

A:

Private endpoints use storage subresource group IDs; Blob and File are separate targets and DNS zones.

B:

A DNS name alone cannot create the required privately routed PaaS subresource connections.

C:

Storage service subresources are not NIC-like public VM IP assignments.

Question 722

Azure SQL Database logical server sqlhr has an Approved private endpoint and correct VNet-linked private DNS; `sqlhr.database.windows.net` resolves through its private DNS chain to the private IP. A developer then changes the connection string to the private endpoint IP or `sqlhr.privatelink.database.windows.net` to 'force' private access, and logins fail. What is the supported correction?

  1. Connect to the private endpoint IP address directly and disable the hostname checks in the client driver.
  2. Use `sqlhr.privatelink.database.windows.net` as the connection-string server name to bypass the public DNS chain.
  3. Enable public network access on sqlhr and stop using its approved private endpoint.
  4. Use `sqlhr.database.windows.net` as the connection-string server name and let its validated private DNS resolution direct traffic to the private endpoint.

Explanation

Correct Answer

D:

Clients use the original `<server>.database.windows.net` FQDN for Azure SQL Database even when its DNS chain resolves to an approved private endpoint IP. The SQL gateway uses that hostname to route the login, while the private DNS/routing path keeps network traffic private.

Incorrect Answers

A:

Azure SQL Database gateway routing requires the logical server's regular FQDN; connecting to a raw private IP fails by design and does not become a supported solution by disabling certificate validation.

B:

The `privatelink` name is part of the DNS alias/endpoint resolution, but the Azure SQL gateway expects the original logical-server FQDN in client connection strings. Direct login using the privatelink FQDN fails.

C:

The approved private endpoint and correct DNS are already working. Public access would violate the intended private-only design and is not needed to fix the wrong client hostname.

Question 723

A Private Link consumer creates a private endpoint connection to a service that requires the provider owner to approve connection requests. The status remains Pending. What must happen?

  1. Disable TLS certificate validation on the client and retry against a public IP.
  2. Make the consumer subscription display name match the provider resource group.
  3. Increase the client VM memory size until approval completes.
  4. The authorized service owner must approve the requested private endpoint connection before data flow is permitted.

Explanation

Correct Answer

D:

The provider must explicitly approve eligible manually approved connection requests.

Incorrect Answers

A:

TLS bypass does not change a pending private endpoint approval state and reduces security.

B:

Display names do not satisfy Private Link connection approval workflow.

C:

Client VM RAM is unrelated to provider-side private endpoint authorization.

Question 724

An Azure PaaS service now has an approved private endpoint, but security insists that public clients must NOT reach its existing public endpoint. What additional action is needed?

  1. Assume private endpoint creation always globally disables the public endpoint automatically.
  2. Enable service endpoint access from every internet subnet.
  3. Create a public wildcard DNS alias to encourage private access.
  4. Set the PaaS resource public network access/firewall restrictions appropriately, separately from the private endpoint.

Explanation

Correct Answer

D:

PaaS public network access settings enforce the intended exclusion while private endpoint remains usable.

Incorrect Answers

A:

Private Link does not necessarily disable public access; destination service controls must be configured.

B:

Service endpoint rules are subnet-based and do not meet a public-blocking requirement as described.

C:

Public DNS wildcard aliases do not prohibit outside clients at the service firewall.

Question 725

Two VNets are peered; one hosts an Azure SQL private endpoint and the other contains an application client. The client resolves SQL to its public IP. What should be fixed?

  1. Add a public IP to the client VM to reach the private endpoint.
  2. Configure private DNS zone linking/resolver forwarding and verify routes/NSGs so the client resolves SQL to the endpoint private IP.
  3. Regenerate SQL admin passwords rather than checking DNS.
  4. Set the VNet peering status to Disconnected to isolate DNS.

Explanation

Correct Answer

B:

Peering supplies routing; DNS configuration must also resolve the service FQDN to the private endpoint address.

Incorrect Answers

A:

Client public IP assignment is unnecessary for peered private endpoint connectivity.

C:

SQL identity authentication is separate from whether the name resolves to a private address.

D:

Disconnecting the peering removes the desired private routing path.

Question 726

An organization has working ExpressRoute private IP routes into an Azure hub VNet. Azure Blob storage has an approved private endpoint, and the privatelink.blob.core.windows.net private DNS zone is linked to the hub. Azure VMs resolve the Blob name privately, but on-premises DNS still returns its public address. The team deploys an Azure DNS Private Resolver inbound endpoint in the reachable hub. Which on-premises DNS change fixes the split resolution without changing the storage endpoint or ExpressRoute routing?

  1. Configure the on-premises conditional forwarder to send Blob queries directly to Azure-provided DNS at 168.63.129.16 across ExpressRoute.
  2. Point the on-premises conditional forwarder at the Private Resolver outbound endpoint, which accepts inbound queries from the data center.
  3. Create a static A record on on-premises DNS with the storage account public IP to ensure a consistent response.
  4. Forward the Blob public DNS suffix queries to the Azure DNS Private Resolver inbound endpoint, which resolves through the linked private zone.

Explanation

Correct Answer

D:

Conditional forwarding of the Blob service suffix to the reachable Azure DNS Private Resolver inbound endpoint causes Azure to resolve through its linked private DNS zone. ExpressRoute routing and the private endpoint already exist, so changing the resolver path directly addresses the sole remaining fault.

Incorrect Answers

A:

Azure-provided DNS at 168.63.129.16 is not directly reachable as an on-premises resolver across ExpressRoute. A reachable Azure DNS Private Resolver inbound endpoint or an Azure-hosted forwarder is needed to answer linked private-zone queries.

B:

The inbound endpoint receives DNS queries from on-premises networks; an outbound endpoint is used for Azure-originated forwarding to other DNS systems. Using the outbound endpoint as a data-center inbound resolver targets the wrong interface.

C:

A public IP A record preserves the erroneous public resolution and does not use the private endpoint. It would also create a brittle manual record unrelated to the verified private DNS zone.

Question 727

A dedicated Azure subnet hosts a private endpoint and has an attached NSG plus a custom UDR intended to route endpoint traffic through an NVA. However, the subnet still has private endpoint network policies Disabled, so the team cannot enforce the planned NSG and UDR controls on that endpoint. The VNet prefix is 10.50.0.0/16 and the custom UDR prefix is 10.50.4.0/24. What subnet change is required before evaluating the resulting effective security and route behavior?

  1. Leave private endpoint network policies Disabled because attaching an NSG and route table automatically enforces both on every private endpoint.
  2. Enable only outbound access to the PaaS public service endpoint while retaining the existing private endpoint subnet policy Disabled.
  3. Enable network policies only for the client VM subnet; private endpoint subnet policy settings are never applied to private endpoint traffic.
  4. Enable private endpoint network policies for NSGs and route tables on the dedicated endpoint subnet, then verify effective security and route handling.

Explanation

Correct Answer

D:

Private endpoint subnet network policies can be enabled for NSGs, UDRs or both. Enabling both permits supported enforcement against private endpoint traffic; the operator must still validate policy effects and route-prefix precedence, including the endpoint /32 default route.

Incorrect Answers

A:

Private endpoint network policies are disabled by default; attaching an NSG or route table does not by itself make those policies affect the private endpoint. The subnet must explicitly opt in to the required enforcement types.

B:

Using a public service endpoint does not apply the desired NSG/UDR behavior to the private endpoint network interface. It also changes the access model without fixing the explicitly disabled subnet policy.

C:

Client subnet NSG or UDR settings can govern that client’s traffic but cannot substitute for enabling policies on the subnet containing the private endpoint when enforcement there is required.

Question 728

A recently approved Blob private endpoint has a correct `privatelink.blob.core.windows.net` DNS zone link, but one application VM still resolves the Blob name to a stale public IP. What should be investigated?

  1. Rotate the storage account keys without checking name resolution.
  2. Change Storage Blob archive tier to Hot.
  3. Verify the public CNAME-to-privatelink resolution chain and the client resolver/cache path, then flush expired cached data as appropriate.
  4. Open TCP 3389 to the internet on the client VM.

Explanation

Correct Answer

C:

A client may have cached an old address or use the wrong recursive resolver despite correct zone links; validate CNAME and resolver behavior.

Incorrect Answers

A:

Storage authentication tokens do not change the IP returned by a DNS query.

B:

Blob tier changes do not influence client hostname resolution.

D:

Public RDP exposure does not correct Blob private DNS caching.

Question 729

A VM can reach a PaaS private endpoint by IP, but the application’s TLS check fails when it uses that raw IP as the HTTPS URL. What is the proper client connection form?

  1. Disable TLS certificate verification for every request permanently.
  2. Add the private IP to a public DNS TXT record rather than using a hostname.
  3. Create an anonymous service account to suppress certificate warnings.
  4. Use the service’s expected FQDN that resolves to the private endpoint IP and validates against the service certificate.

Explanation

Correct Answer

D:

Private Link maintains the service FQDN; privately resolving that name preserves the TLS hostname validation contract.

Incorrect Answers

A:

Disabling certificate verification defeats server identity checks and is not a safe private endpoint solution.

B:

TXT records do not alter the hostname presented for TLS certificate verification.

C:

Authentication accounts do not make a certificate valid for an unrelated IP address.

Question 730

Storage account `stbilling` has an approved Blob private endpoint in VNet `vnet-billing`. The `privatelink.blob.core.windows.net` private zone is already linked to the client VNet. After the endpoint was replaced, its new private IP is 10.17.4.9, but a previously hand-maintained A record for `stbilling` still points to the deleted endpoint at 10.17.4.6. DNS clients reliably receive that obsolete record; cache expiry is not the cause. The team wants future endpoint replacements to update DNS records without manual IP edits. Which change directly addresses the record-lifecycle problem?

  1. Enable VM auto-registration on the private DNS virtual network link; that mechanism automatically tracks Storage Blob private endpoint A records.
  2. Enable a `Microsoft.Storage` service endpoint on the application subnet; it will replace the stale private DNS A record whenever a Blob private endpoint changes.
  3. Associate the active Blob private endpoint with a private DNS zone group bound to the correct private zone, reconcile the conflicting manual A record, and validate the resulting managed record and standard Blob hostname.
  4. Enable public network access from all networks on `stbilling`, then rely on the old private DNS A record without updating it.

Explanation

Correct Answer

C:

A private DNS zone group ties a private endpoint to the correct private DNS zone and manages its endpoint A records when endpoint configuration changes. After reconciling the obsolete hand-authored entry, clients can resolve the normal Blob service hostname through the linked private zone to the current private IP, including after supported endpoint lifecycle changes.

Incorrect Answers

A:

Private DNS zone VNet-link auto-registration is designed for supported VM hostnames, not to maintain service-specific Blob Private Link records. It would not replace the manually authored `stbilling` A record that is pointing to the deleted endpoint.

B:

A service endpoint changes the private VNet route identity used when reaching a public service endpoint; it does not manage `privatelink.blob.core.windows.net` A records for a private endpoint. The obsolete private IP would remain in DNS.

D:

Enabling universal public network access weakens the required private access boundary and does not correct a DNS response pointing to 10.17.4.6. A stale A record remains incorrect regardless of the storage firewall configuration.