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 74

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.

Question 731

A developer enabled a VNet service endpoint but the architecture specifically requires a private IP to a single Azure Storage account via Azure Private Link. What should be deployed instead?

  1. Keep only the service endpoint and assume it assigns a private IP to each storage account.
  2. Associate a VM public IP with the storage account firewall.
  3. Add a public DNS record pointing to the storage service’s public IP.
  4. Create an approved Storage private endpoint and configure private name resolution and resource public-access policy.

Explanation

Correct Answer

D:

Private endpoint allocates a VNet private IP for the specific Storage subresource while DNS routes clients to it.

Incorrect Answers

A:

Service endpoints send traffic to a PaaS public endpoint and do not create per-account private IPs.

B:

A VM public IP is not a Storage PaaS Private Link endpoint.

C:

Public DNS does not create the required private-IP connection.

Question 732

The public authoritative Azure DNS zone `example.com` must resolve `api.example.com` to an Azure Standard public IPv4 address. Which record is required?

  1. Create an A record for `api` in the `example.com` public DNS zone pointing to the assigned IPv4.
  2. Link the public DNS zone to an Azure VM subnet for automatic routing.
  3. Create an NSG service tag named api.example.com.
  4. Add an Azure Blob SAS with the service domain as its scope.

Explanation

Correct Answer

A:

An A record maps a host label to its IPv4 address in the authoritative public zone.

Incorrect Answers

B:

Virtual network links are for private DNS zones, not to create a public A record.

C:

NSG service tags do not serve as authoritative DNS resource records.

D:

Storage SAS grants data access, not DNS hostname mapping.

Question 733

A company created the Azure DNS public zone `example.net` but internet resolvers still query the old DNS host. What registrar change is necessary?

  1. Change an Azure VM disk’s caching setting to the desired authoritative server.
  2. Update the parent-domain registrar NS delegation to the Azure DNS zone’s assigned name servers.
  3. Set a private DNS VNet link and assume the public DNS hierarchy delegates automatically.
  4. Create a storage account public IP with the same suffix.

Explanation

Correct Answer

B:

Public recursive resolvers follow parent-zone NS delegation; the registrar must reference Azure DNS authoritative servers.

Incorrect Answers

A:

Disk caching does not delegate authority for a public DNS domain.

C:

Private VNet links do not update the public DNS root/registry delegation.

D:

Storage accounts do not administer public-domain NS delegation.

Question 734

A nonapex hostname `www.example.com` must resolve as an alias to `site.azurewebsites.net` rather than to a raw IP address. Which record type fits?

  1. A numeric A record containing the Azure Websites hostname as text.
  2. A reverse PTR record on a private NIC.
  3. An MX record for the web application hostname.
  4. A CNAME at the `www` record name pointing to the canonical app hostname.

Explanation

Correct Answer

D:

CNAME aliases a supported nonapex hostname to another canonical DNS name.

Incorrect Answers

A:

A records require IPv4 address values rather than another DNS hostname.

B:

PTR records support reverse lookup, not forward HTTP hostname aliasing.

C:

MX records specify mail exchangers, not general web aliases.

Question 735

An engineering team runs api.internal.contoso.example on a private VM inside vnet-dev. It needs an internally maintained DNS name that only linked Azure VNets can resolve, without publishing records on the public Internet. Which TWO DNS resources or links are required? Select TWO answers.

  1. Publish api.internal.contoso.example as an A record in a public Azure DNS zone.
  2. Peer vnet-dev with an unrelated VNet but leave all DNS resources unchanged.
  3. Link vnet-dev to the intended Azure Private DNS zone so its resolvers can use that zone.
  4. Create privatelink.database.windows.net for this ordinary VM host name even though it is not an Azure SQL private endpoint.
  5. Create an Azure Private DNS zone for internal.contoso.example and add the VM’s intended record.

Explanation

Correct Answers

C:

A VNet link makes records in the private DNS zone resolvable by Azure-provided DNS from the consuming VNet. Without the link, creating a zone and adding api.internal.contoso.example will not normally make its record available to vnet-dev clients. The team should enable the correct link and test resolution from an instance using the expected resolver path; custom DNS servers may also need explicit forwarding.

E:

Azure Private DNS zones store private host records and are not resolved by public Internet DNS. Creating internal.contoso.example and its intended VM A record establishes the authoritative private namespace. However, zone creation by itself does not attach it to a client network; the separately selected VNet link is necessary for default VNet DNS resolution. This design meets the requirement without adding public DNS records for the internal host.

Incorrect Answers

A:

Public Azure DNS zones publish records for public DNS resolution, while the request forbids exposing this internal host name on the Internet. Creating a public record might make the service discoverable externally even if network access is later restricted. Azure Private DNS zones are designed for this private naming requirement and resolve only for appropriately linked networks.

B:

VNet peering provides network connectivity between virtual networks; it does not create or expose private DNS records on its own. A workload can be reachable by private IP while its intended name remains unresolvable. This case requires a private DNS zone and a VNet link, not merely connectivity to an unrelated network.

D:

The privatelink.database.windows.net zone is associated with Azure SQL Database private endpoint name resolution, not with an arbitrary internal API VM. Using it for a name under internal.contoso.example would not create the desired DNS authority for that suffix. Create a private zone with the actual application namespace instead of reusing an unrelated service-specific Private Link zone.

Question 736

An Azure DNS Private Resolver has an inbound endpoint in hub VNet `vnet-hub`. A private zone is linked to that hub. A spoke forwarding ruleset has a rule for `privatelink.blob.core.windows.net` that sends queries to the hub's inbound endpoint, and the spoke uses the ruleset successfully. An engineer also links this SAME forwarding ruleset to `vnet-hub`; queries from the hub then begin timing out. Which correction avoids the documented DNS forwarding loop without breaking spoke resolution?

  1. Delete the private DNS zone and publish its A records in public Azure DNS so the resolver cannot recurse on a private suffix.
  2. Remove the forwarding ruleset VNet link from `vnet-hub` while retaining the spoke's ruleset link, the hub's private-zone link and the forwarding rule to the inbound endpoint.
  3. Replace the hub resolver's inbound endpoint with an outbound endpoint IP, because outbound endpoints receive inbound name-resolution queries from all linked VNets.
  4. Add a second identical rule for the same suffix to the same inbound endpoint and lower its priority so the loop is resolved by rule ordering.

Explanation

Correct Answer

B:

Microsoft warns not to link a forwarding ruleset to the VNet containing the inbound endpoint when a forwarding rule points back to that inbound endpoint, because DNS queries may loop. Removing the HUB ruleset link preserves its zone link and the spoke's forwarding path without self-forwarding.

Incorrect Answers

A:

A linked private DNS zone is the intended source of the Blob private A record and must not be made public to mask a routing error. Deleting it would break secure name resolution for private consumers rather than removing the recursive ruleset link.

C:

An Azure DNS Private Resolver inbound endpoint has a reachable IP for incoming queries. Outbound endpoints forward queries to target resolvers through rulesets and are not substitutes for incoming DNS query VIPs. Swapping endpoint types does not correct the link loop.

D:

A duplicate matching suffix rule doesn't change that the hub points queries to its own inbound endpoint. Loop prevention requires correcting the ruleset-to-VNet relationship, not another rule aimed at the same destination.

Question 737

A private Azure DNS zone should automatically create and maintain compatible records for Azure VMs in one linked VNet. Which setting is required?

  1. Create an Azure DNS public zone of the same name and delete the private zone.
  2. Increase the VNet subnet size even though no IP capacity issue exists.
  3. Enable auto-registration on the eligible private DNS zone virtual network link.
  4. Enable anonymous Storage Blob access for the VM DNS hosts.

Explanation

Correct Answer

C:

Auto-registration on a supported private DNS VNet link controls the automatic VM record behavior.

Incorrect Answers

A:

A public zone does not provide the requested private VM record registration.

B:

Subnet sizing does not instruct Azure private DNS to register VM hostname records.

D:

Anonymous Blob authorization is unrelated to DNS record creation.

Question 738

Azure VMs in spoke VNet `vnet-app` use Azure-provided DNS, and an IPsec VPN already provides verified private connectivity to on-premises DNS servers at `10.90.0.10` and `10.90.0.11`. These VMs resolve Azure private endpoint names, but fail to resolve the on-premises-only suffix `corp.example`. An Azure DNS Private Resolver outbound endpoint and a forwarding ruleset are deployed in a reachable hub. The ruleset can be linked to `vnet-app`, but it has NO forwarding rule for `corp.example`. What configuration provides the missing Azure-to-on-premises DNS path?

  1. Add a DNS forwarding rule for `corp.example.` targeting the reachable on-premises DNS server IPs through the resolver outbound endpoint, and link the forwarding ruleset to `vnet-app`.
  2. Add an on-premises conditional forwarder that sends `corp.example` queries to an Azure DNS Private Resolver inbound endpoint, reversing the direction required by the Azure VM clients.
  3. Create a public DNS CNAME record for every private on-premises hostname, publishing the internal namespace externally instead of using the existing VPN.
  4. Replace the resolver outbound endpoint with a storage private endpoint, assuming a Blob private endpoint forwards DNS queries to corporate DNS servers.

Explanation

Correct Answer

A:

Azure DNS Private Resolver outbound endpoints and forwarding rulesets support forwarding queries originating in linked Azure VNets to custom DNS servers. A matching suffix rule points `corp.example.` to the on-premises resolvers over existing VPN connectivity, while the spoke link makes the rule applicable to its Azure-provided DNS clients.

Incorrect Answers

B:

An inbound endpoint accepts queries sent toward Azure, typically from on-premises resolvers to linked Azure private zones. Here the failing clients are Azure VMs asking for a corporate-only on-premises zone. An on-premises forwarder aimed into Azure would not establish the missing outbound forwarding rule.

C:

Publishing internal records as public CNAMEs leaks the private namespace and does not direct Azure-provided DNS clients through the approved VPN to the authoritative corporate DNS servers. The case already has a supported private forwarding mechanism.

D:

Azure Storage private endpoints are data-service network interfaces, not DNS forwarders for arbitrary on-premises names. They neither replace DNS Private Resolver outbound endpoints nor match the corporate suffix to custom DNS server IPs.

Question 739

An operator created a public Azure DNS zone and expects that zone itself to recursively resolve unrelated internet domains for client VMs. Which distinction is correct?

  1. An authoritative hosted DNS zone provides records for its owned domain; recursive DNS resolution requires a separate resolver.
  2. Authoritative Azure DNS zones automatically act as unrestricted caching recursive resolvers for all internet names.
  3. A service endpoint on every VM NIC creates recursive DNS services from hosted zones.
  4. Setting an NSG priority to 100 allows a zone to answer every unrelated DNS name.

Explanation

Correct Answer

A:

Public Azure DNS zones answer authoritative queries for their delegated namespaces, not arbitrary recursive queries.

Incorrect Answers

B:

Hosting zone records does not provision a general client recursive DNS resolver service.

C:

Azure service endpoints do not turn authoritative DNS zones into recursive resolvers.

D:

NSG priority permits or denies packets; it does not add recursive DNS logic.

Question 740

After an Azure DNS public A record changes, one client continues using the old IPv4 while authoritative queries show the new value. What explains the delay?

  1. Deleting the Azure public IP associated with the old record is always necessary for TTL expiration.
  2. Giving the client subscription Owner will instantly clear recursive DNS caches.
  3. Renaming the resource group changes all recursive DNS answers immediately.
  4. The recursive resolver/client may serve the old cached record until its TTL expires; verify TTL and authoritative response.

Explanation

Correct Answer

D:

DNS TTL governs the caching lifetime of existing answers, and clients can remain stale until their cache refreshes.

Incorrect Answers

A:

An old public IP is unrelated to whether the resolver cache retains a prior DNS answer until its TTL.

B:

Azure RBAC does not purge DNS cache state in recursive resolvers.

C:

Resource-group names are not a signal to internet DNS caches to refresh early.