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 75

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.

Question 741

A public DNS zone should include TXT ownership verification for a custom app domain. Which Azure configuration or procedure is the best fit?

  1. Create a CNAME at a supported non-apex hostname.
  2. Add the requested TXT record at the correct zone name without overwriting A/CNAME records.
  3. Link correct privatelink DNS zone with A record pointing to the endpoint private IP.
  4. Create an Azure DNS public A record in the authoritative hosted zone.

Explanation

Correct Answer

B:

A DNS TXT record at the verification name proves domain ownership to the requesting service without replacing A or CNAME records used for address resolution. Publish the service-provided value at the exact requested label and validate propagation.

Incorrect Answers

A:

A CNAME directs a subdomain to another DNS name. It does not satisfy the ownership challenge that specifically requires a TXT record at the designated validation name; both record types can coexist at different permitted names.

C:

A privatelink DNS A record resolves an Azure private endpoint within linked virtual networks. The requested domain-ownership proof is a TXT record in the public authoritative DNS zone, not a private endpoint mapping.

D:

Create an Azure DNS public A record in the authoritative hosted zone is pertinent when a public domain should resolve application.example.com to a public Azure IP. This case instead states a public DNS zone should include TXT ownership verification for a custom app domain. That alternate change addresses a different operational condition and does not directly achieve the needed resolution: add the requested TXT record at the correct zone name without overwriting A/CNAME records.

Question 742

A Blob private endpoint is approved and the VNet is linked to `privatelink.blob.core.windows.net`, but the private DNS zone lacks an A record for account `stdata1`. A VM consequently resolves the normal account hostname to the public endpoint. What specific DNS repair is needed?

  1. Assign an extra Storage Blob Data Reader role; data RBAC creates DNS records automatically.
  2. Create only a public Azure DNS A record pointing to the public Storage Blob IP.
  3. Increase the DNS resolver TTL so the public answer stays cached longer.
  4. Create or correct the account-specific A record/private DNS zone-group integration mapping `stdata1` to its Blob private endpoint IP.

Explanation

Correct Answer

D:

Private endpoint DNS integration or an A record in the linked privatelink zone maps the normal service hostname through the private CNAME to the private IP.

Incorrect Answers

A:

Storage data roles authorize reads after resolution, but cannot supply the missing private-zone A record.

B:

A public A record does not direct VNet clients to the private endpoint IP address required by the scenario.

C:

Increasing cache TTL would retain an incorrect public mapping instead of repairing the missing private record.

Question 743

Azure DNS hosts a public zone `contoso.example` with `inventory.contoso.example` pointing to the public app endpoint `198.51.100.25`. Inside `vnet-finance`, VMs using Azure-provided DNS must resolve that SAME full hostname to a private application VM at `10.30.2.4`. Internet clients must keep receiving the public address. The Azure VNet has no custom DNS server or forwarding ruleset. Which Azure DNS design meets both views without changing the public record?

  1. Create a separate Azure Private DNS zone `contoso.example`, add `inventory` A = `10.30.2.4`, and link that private zone to `vnet-finance` while retaining the existing public zone.
  2. Replace the `inventory` A record in the public `contoso.example` zone with `10.30.2.4`; public and VNet clients will automatically receive different values.
  3. Create the same-named Azure Private DNS zone and A record but leave it unlinked to `vnet-finance`, because Azure-provided DNS searches all private zones in a subscription.
  4. Create an Azure DNS Private Resolver outbound forwarding rule for `contoso.example.` pointing to the public authoritative DNS servers; the public server will return the private IP for Azure clients automatically.

Explanation

Correct Answer

A:

Azure Public DNS and Azure Private DNS can host zones with the same name for split-horizon answers. A linked private zone supplies the internal A record to Azure-provided DNS for `vnet-finance`, while the independent public zone continues answering internet resolvers with `198.51.100.25`.

Incorrect Answers

B:

Changing the sole public authoritative A record would change the public answer to the private address and fail the external availability requirement. A public zone does not switch records based on the client's location merely because the address is private.

C:

An Azure Private DNS zone is not implicitly available to every virtual network in a subscription. Without the appropriate virtual-network link or configured resolution path, `vnet-finance` will not see its private record and will continue resolving via other sources.

D:

Forwarding the internal query to the unchanged public authoritative server returns the public address, not the privately required `10.30.2.4`. An outbound forwarding rule does not itself create a distinct private DNS zone answer; that answer must be hosted and reachable through the intended internal resolution path.

Question 744

A spoke VNet uses Azure-provided DNS and is linked to an existing Azure DNS Private Resolver forwarding ruleset. All rules are enabled and the required outbound endpoint and destination DNS servers are healthy. The ruleset contains three rules: `corp.local.` to DNS server 10.90.0.10, `finance.corp.local.` to 10.91.0.20, and wildcard `.` to 10.92.0.30. A VM queries `payroll.finance.corp.local`. Which forwarding destination will Azure select according to rule matching?

  1. 10.90.0.10, because a parent namespace rule always overrides a more specific domain rule.
  2. 10.92.0.30, because the wildcard dot rule has priority over every explicit suffix.
  3. 10.91.0.20, because `finance.corp.local.` is the longest matching enabled suffix for the requested DNS name.
  4. The resolver inbound endpoint IP, because an inbound endpoint supersedes outbound forwarding rules for every linked VNet query.

Explanation

Correct Answer

C:

Microsoft documents that a forwarding ruleset evaluates matching DNS suffixes and chooses the longest match. `payroll.finance.corp.local` matches all three rules, and `finance.corp.local.` is the most specific, so the outbound forwarding target is 10.91.0.20.

Incorrect Answers

A:

The parent suffix `corp.local.` does match the query, but Azure DNS Private Resolver selects the longest matching domain suffix when several rules match. The more specific finance.corp.local rule takes precedence over its parent namespace.

B:

The dot rule is a catch-all and may match otherwise uncovered names, but it is less specific than either explicit suffix. It does not override the longest matching finance.corp.local rule for this query.

D:

An inbound endpoint accepts queries directed toward Azure DNS from external networks. It does not replace the active outbound ruleset selection for an Azure VM querying through a linked ruleset.

Question 745

A company hosts its public DNS zone example.net in Azure DNS. The certificate governance policy states that only its approved public certificate authority may issue TLS certificates for example.net and its covered hosts. Administrators must express that issuance authorization in public DNS without replacing existing A, NS, SOA or TXT records. What Azure DNS record configuration is designed for this purpose?

  1. An MX record identifying the permitted certificate authority as the zone mail exchanger.
  2. A public A record with its IPv4 address set to the certificate authority name, replacing the website address.
  3. A CAA record set with an issue property naming the approved certificate authority (and issuewild as applicable for wildcard issuance).
  4. An NS record deleting all existing authoritative nameservers and delegating the whole DNS zone to the certificate authority.

Explanation

Correct Answer

C:

Azure DNS supports Certification Authority Authorization (CAA) records. The issue tag identifies certificate authorities authorized for ordinary certificate issuance; issuewild can govern wildcard issuance. These records coexist with normal A/TXT/NS/SOA record sets and express CA issuance restrictions rather than address resolution.

Incorrect Answers

A:

MX records designate mail exchangers and priorities for receiving email, not authorized TLS certificate issuers. Changing MX entries cannot implement a CAA issuance policy.

B:

An A record maps a hostname to an IPv4 address. It does not express an allowlist of certificate authorities, and replacing an application address would disrupt resolution instead of setting certificate issuance policy.

D:

NS records control DNS delegation. Replacing authoritative nameservers with a CA does not create a CAA policy and would break the current zone hosting arrangement.

Question 746

A VM has a valid private DNS zone link but cannot reach the resolved server. Which Azure configuration or procedure is the best fit?

  1. Configure Azure DNS Private Resolver inbound endpoint or supported conditional forwarding from hybrid DNS.
  2. Troubleshoot network routes/NSGs after confirming DNS resolution is correct.
  3. Use a recursive resolver separately; Azure DNS hosted zones are authoritative.
  4. Create an Azure DNS public A record in the authoritative hosted zone.

Explanation

Correct Answer

B:

Successful private DNS resolution proves the hostname mapping, not connectivity to the resolved address. Check effective routes, NSG/firewall policy and the destination listener to explain why TCP packets still cannot reach that private IP.

Incorrect Answers

A:

A Private Resolver inbound endpoint or hybrid forwarding handles on-premises DNS queries; it does not create public A records or missing private endpoint records.

C:

An authoritative Azure DNS zone and a recursive resolver play different roles in name resolution. The case already has a valid private DNS zone link and returns the intended address, so choosing another DNS server won't fix packets failing to reach that address. Diagnose effective routes, security rules, and endpoint service reachability.

D:

A public Azure DNS A record supplies a public IP mapping, not a private endpoint's internal DNS answer or hybrid recursive forwarding.

Question 747

A region has three Azure VMs behind a new public HTTPS service. TLS remains terminated on the VMs; the team only needs TCP flow distribution to healthy instances, without URL-path inspection. Which complete Azure front-end design is appropriate?

  1. Create only an internal Load Balancer using a private frontend address.
  2. Create an internal Load Balancer and adjust VNet peering, without any public frontend.
  3. Create a public Standard Load Balancer with Standard public-IP frontend, backend pool, TCP 443 rule, and compatible health probe.
  4. Change the existing backend VMs to listen on TCP 443 without deploying a public frontend or backend pool.

Explanation

Correct Answer

C:

Standard public Azure Load Balancer performs Layer-4 TCP distribution to healthy backend instances using a public Standard IP frontend, backend pool, load-balancing rule, and probe. The VMs retain TLS termination because Load Balancer does not offload TLS or inspect HTTP paths.

Incorrect Answers

A:

An internal Load Balancer exposes only a private frontend address to reachable private networks. It cannot provide the requested public entry point to internet clients even though it can distribute private TCP connections.

B:

Peering allows routing between private VNets and can help private clients reach an internal frontend, but it does not publish an internet-facing HTTPS entry point. The required destination is public, not a new private peering path.

D:

Listening on TCP 443 is necessary at each backend but does not supply the public frontend IP or transport distribution rule. Clients still lack the public load-balanced endpoint requested by the scenario.

Question 748

A line-of-business TCP application must be load-balanced between Azure VMs and used only by private clients on connected VNets. Security prohibits a public frontend IP. Which load-balancing model meets that boundary?

  1. Create public Standard Load Balancer frontend, backend pool, rule and probe.
  2. Use an internal Load Balancer with private frontend IP.
  3. Use suitable Standard Load Balancer zone-resilient frontend and zonal backend placement.
  4. Choose Application Gateway or another L7 proxy instead of expecting L4 Load Balancer content routing.

Explanation

Correct Answer

B:

An internal Azure Load Balancer assigns a private frontend address in a VNet/subnet and distributes transport flows among healthy backend VMs. Private clients with an allowed network route and NSG access can reach it without any public load-balancer frontend.

Incorrect Answers

A:

A public Standard Load Balancer provisions an internet-routable frontend address, directly conflicting with the requirement to keep this service private. The application does not require an external entrance.

C:

Zone-resilient configuration can improve infrastructure availability but does not, by itself, decide whether the frontend is public or private. The decisive requirement is private-only exposure, not a specified placement across availability zones.

D:

Application Gateway provides Layer-7 HTTP(S) functions such as host/path routing or TLS termination. This workload explicitly requires TCP-level private distribution without application-layer routing, so an internal Load Balancer is the more direct fit.

Question 749

A backend pool needs to include several VMs via NIC association. What is the most appropriate next administrative decision?

  1. Add valid load-balancing rule mapping frontend port/protocol to backend pool and probe.
  2. Add eligible NIC IP configurations to the intended backend pool.
  3. Configure explicit NAT Gateway or supported outbound rule rather than assuming implicit SNAT.
  4. Create public Standard Load Balancer frontend, backend pool, rule and probe.

Explanation

Correct Answer

B:

An Azure Load Balancer sends distributed traffic to the NIC/IP configurations or VMSS instances registered in its backend pool. Associate each eligible VM NIC IP configuration with the correct pool and ensure the pool belongs to the intended rule. Merely creating a frontend or NAT Gateway does not add these backends.

Incorrect Answers

A:

A load-balancing rule connects a frontend protocol/port to a backend pool with a probe; it does not create the correct public/private frontend by itself.

C:

NAT Gateway and Load Balancer outbound rules govern backend-initiated internet egress and SNAT. They do not add VM NIC IP configurations to an inbound load-balancing backend pool. For distribution to several VMs, associate the eligible NIC IP configurations with the specific backend pool referenced by the forwarding rule.

D:

A public Standard Load Balancer provides internet-facing inbound distribution; it is unnecessary when the requirement is only internal private access or a probe fix.

Question 750

An Azure Standard public Load Balancer has a valid frontend IP, healthy VMs in its backend pool, and a configured TCP probe. No load-balancing rule exists, so client TCP 443 connections never reach the VMs on TCP 8443. What must be added?

  1. Create a TCP load-balancing rule mapping frontend port 443 to backend port 8443 and associate the existing backend pool and health probe.
  2. Only add a second health probe and continue without any frontend-to-backend rule.
  3. Give every backend VM subscription Owner, which automatically publishes TCP ports.
  4. Attach an Azure Files share to the load balancer to enable listener mapping.

Explanation

Correct Answer

A:

The frontend, backend pool and health probe do not distribute traffic until a load-balancing rule links the TCP frontend and backend ports.

Incorrect Answers

B:

Additional probes cannot create the missing packet-forwarding rule between the frontend and service listener.

C:

Azure RBAC affects resource management and does not automatically create Load Balancer data-plane port mappings.

D:

Azure Files shares cannot replace a Standard Load Balancer rule and are unrelated to TCP 443-to-8443 forwarding.