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 76

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.

Question 751

A hub VNet contains two network virtual appliance (NVA) instances behind an INTERNAL Standard Load Balancer. The appliances handle many different TCP and UDP port flows. The team wants a single rule to balance all supported port flows without adding one rule per port. Which load-balancing rule should be configured?

  1. Create one public Standard Load Balancer rule on TCP 443 and expect it to cover all UDP ports automatically.
  2. Create an inbound NAT rule for one NVA instance and assume all clients will be balanced across both appliances.
  3. Configure a high-availability (HA) ports rule on the internal Standard Load Balancer, with protocol All and frontend/backend ports 0, using a supported backend/health configuration.
  4. Use an Azure Application Gateway path-based HTTP listener to distribute arbitrary UDP and other non-HTTP transport flows.

Explanation

Correct Answer

C:

Internal Standard Load Balancer HA ports uses protocol All and port 0 to distribute many TCP/UDP flows, with applicable HA ports restrictions and health probing.

Incorrect Answers

A:

A public TCP 443 rule balances the matching TCP port mapping only; it is not the internal all-ports/UDP NVA distribution capability.

B:

An inbound NAT rule can map inbound connections to one backend instance and does not create the required all-port multi-NVA flow balancing.

D:

Application Gateway is Layer 7 HTTP/HTTPS oriented and cannot replace an internal Standard Load Balancer HA ports rule for arbitrary UDP flows.

Question 752

An internet-facing TCP application runs on healthy Azure VMs in two availability zones. Its Standard public Load Balancer already has valid backend membership, a TCP load-balancing rule and a healthy probe, but the public frontend is pinned to zone 1. The public service hostname must remain available after a zone-1 outage; a managed DNS cutover to a new frontend IP is allowed. Which architecture change directly addresses the remaining single-zone exposure?

  1. Create or select a zone-redundant Standard public IP/frontend configuration and attach the zonally distributed healthy backend pool, migrating the existing rule as required.
  2. Replace the public frontend with an internal-only private IP so internet clients still connect to the same public address.
  3. Add a second TCP load-balancing rule but leave the public frontend assigned only to zone 1.
  4. Change the frontend application port from TCP to UDP without modifying the zonal frontend placement.

Explanation

Correct Answer

A:

A zone-redundant Standard public frontend uses infrastructure in multiple availability zones; with healthy backend VMs already spread across zones it preserves the public data path when zone 1 fails. Migrating from an existing zonal frontend requires a supported new frontend and corresponding rule/client cutover.

Incorrect Answers

B:

An internal-only frontend is reachable by private network clients, not the required internet users. Removing the public frontend also fails the requirement to maintain a public service endpoint.

C:

A second rule changes port-to-pool forwarding, but both rules would still depend on the same zone-1 public frontend. The scenario already confirms the necessary TCP forwarding rule and health probe.

D:

Changing TCP to UDP breaks an application that expects TCP and does not change the zone affinity of the public IP/frontend. Resilience is a frontend and healthy-backend placement problem.

Question 753

A NAT rule exposes a specific backend VM for maintenance while pool traffic remains balanced. Which change addresses the stated situation most precisely?

  1. Configure an eligible inbound NAT rule instead of load-balancing every maintenance connection.
  2. Evaluate Load Balancer transport behavior and application proxy options without forcing HTTP headers from L4.
  3. Configure UDP-specific load-balancing rule rather than TCP-only port rule.
  4. Associate a health probe with its load-balancing rule and check probe paths.

Explanation

Correct Answer

A:

An inbound NAT rule maps a selected frontend IP/port to a specific backend instance and port for maintenance. A load-balancing rule instead distributes flows across healthy pool members, which would not reliably select the one VM an operator needs.

Incorrect Answers

B:

Layer-4 transport limitations and HTTP proxy choices matter for inspecting URLs or terminating TLS; this maintenance requirement is about forwarding a specific frontend port to one backend VM. An inbound NAT rule handles that per-VM mapping separately from pool-wide load-balancing rules.

C:

A UDP rule handles UDP packet flows, not the TCP protocol or health-probe fault at issue.

D:

Associating a compatible health probe measures backend health; it does not define the required forwarding port/protocol rule by itself.

Question 754

A network team is deploying an internal Azure Load Balancer. The backend pool, health probes and listener ports have already been designed and validated. Clients in a peered virtual network must reach the frontend over private networking; no public IP is allowed. Which TWO additional design and connectivity actions meet the requirement? Select TWO answers.

  1. Ensure the VNet peering permits the client path and that effective routing and NSGs allow private traffic to reach the healthy backend instances.
  2. Create a public Standard Load Balancer frontend to let the peered clients connect through a public internet address.
  3. Assign a public IPv4 frontend to the new load balancer and route traffic from the peered VNet through the public internet.
  4. Change the already validated listener-to-backend port mappings without changing the frontend network exposure or peering path.
  5. Configure the Load Balancer with a private internal frontend IP address from its virtual network subnet.

Explanation

Correct Answers

A:

The client network is peered rather than local to the load balancer’s VNet. Private frontend addressing will not help if the source routes, effective peering connectivity, or network security rules block the connection to healthy backends. Check both sides of the peerings where required, verify effective routes and NSG rules, and confirm the private path is usable from the client subnet. This is the necessary connectivity action paired with provisioning an internal private frontend; neither item alone provides the entire required solution.

E:

An internal Azure Load Balancer frontend uses a private IP address allocated from the attached virtual network subnet; it is the correct exposure model when clients should use private networking instead of the internet. Configure the internal frontend and retain the already validated backend pool and health probe design. This action supplies the private service destination, while separately checking the peered network routes and NSGs provides reachability from the remote client VNet. Both design steps are necessary; a public frontend would violate the explicit network requirement.

Incorrect Answers

B:

A public Standard Load Balancer is suitable for internet-facing workloads, but the requirement forbids a public IP and calls for access across a private peered VNet. A public frontend changes the service exposure model and is not the selected internal endpoint. Use an internal frontend address from the Azure virtual network, with private connectivity and security rules configured for the client.

C:

Routing peered workloads through a public IPv4 frontend would expose a public entry point that the scenario explicitly prohibits. VNet peering is designed to support private address reachability between eligible virtual networks, subject to routing and network security configuration. A public frontend also does not substitute for verifying the permitted private client path to the backends.

D:

The load-balancer listener and backend port mappings were already designed and validated. Changing those mappings does not establish a private frontend IP or enable any missing reachability across the peered networks, so it addresses a different layer. The stated need is private frontend selection together with appropriate peer-routing and NSG paths, not a redundant port-rule change.

Question 755

A web service must send requests for `/images/*` to one backend pool and `/api/*` to another. The existing Azure Load Balancer sends TCP connections but cannot discriminate by HTTP URL path. Which replacement component directly implements the rule?

  1. Evaluate Load Balancer transport behavior and application proxy options without forcing HTTP headers from L4.
  2. Choose Application Gateway or another L7 proxy instead of expecting L4 Load Balancer content routing.
  3. Use suitable Standard Load Balancer zone-resilient frontend and zonal backend placement.
  4. Use an internal Load Balancer with private frontend IP.

Explanation

Correct Answer

B:

Azure Application Gateway operates at Layer 7 and supports HTTP path-based routing rules, unlike Azure Load Balancer, which only sees TCP/UDP flow details. Configuring the `/images/*` and `/api/*` path map at Application Gateway implements the requested per-path backend selection.

Incorrect Answers

A:

Inspecting Load Balancer limitations confirms it is Layer 4, but a diagnostic review alone does not add a path-aware routing engine. The app still needs a component that reads HTTP paths and selects different backend targets.

C:

Making the Load Balancer frontend zone-resilient affects availability, not its protocol layer. A zone-resilient Layer-4 balancer still cannot inspect URL paths or steer requests based on HTTP request content.

D:

Using an internal frontend changes whether clients reach the service privately, but does not change Azure Load Balancer into an HTTP reverse proxy. Private TCP forwarding still lacks the specified URL-path rule.

Question 756

Backend VMs behind a Standard public Azure Load Balancer have no instance public IPs, use a private subnet, and cannot initiate internet connections. They require supported explicit outbound SNAT for software updates. Which change provides it?

  1. Configure an eligible inbound NAT rule instead of load-balancing every maintenance connection.
  2. Configure frontend/backend ports in a supported rule with correct probe.
  3. Configure explicit NAT Gateway or supported outbound rule rather than assuming implicit SNAT.
  4. Add eligible NIC IP configurations to the intended backend pool.

Explanation

Correct Answer

C:

Associate an Azure NAT Gateway with the backend subnet for outbound-only SNAT, or configure a supported Standard Load Balancer outbound rule with its public frontend IP and allocated SNAT ports. These are explicit egress mechanisms and avoid reliance on default outbound access.

Incorrect Answers

A:

An inbound NAT rule forwards a chosen frontend port to a backend instance, typically for administrator access. It does not create the required general-purpose outbound SNAT from all backend VMs to the internet.

B:

Correct inbound listener/backend port mapping and health probes determines incoming distribution and backend eligibility. Neither choice supplies the egress public-IP translation that this private subnet lacks.

D:

Backend-pool membership is needed for inbound distribution, but adding NIC IP configurations alone does not allocate outbound SNAT paths. The VMs can be valid pool members and still lack an explicitly configured outbound internet method.

Question 757

A Standard Azure Load Balancer already has a working frontend TCP/443 rule and three VM backends. Its rule is attached to `probe-admin`, which merely tests whether TCP/22 is open; all three VMs pass. A separate validated HTTP probe `probe-app` checks each backend on port 8080 at `/ready` and receives 200 from VM-A and VM-B but 503 from failing VM-C. Operations needs the existing frontend rule to stop distributing new application connections to VM-C. What should the administrator change?

  1. Change the existing TCP/443 application rule to UDP/443, leaving probe-admin associated.
  2. Associate the already validated probe-app with the existing TCP/443 load-balancing rule, replacing probe-admin as that rule’s health signal.
  3. Create an unrelated second frontend/load-balancing rule, leaving the current TCP/443 rule attached to probe-admin.
  4. Add an inbound NAT rule for SSH to VM-C and assume this prevents new application connections to the unhealthy backend.

Explanation

Correct Answer

B:

Each Standard Load Balancer rule uses its associated health probe to select healthy backend instances for new flows. The already tested probe-app accurately reports HTTP 200 for healthy application instances and 503 for VM-C, unlike the SSH-port probe-admin. Associate probe-app with the existing TCP/443 rule so VM-C is no longer eligible for new load-balanced connections.

Incorrect Answers

A:

UDP is a different transport protocol and would not make the existing TCP client rule respect the application readiness responses. The existing application flow must stay TCP, and its health signal must be application-aware.

C:

Another unrelated frontend rule does not alter the probe attached to the original live TCP/443 rule. Traffic arriving on the existing frontend keeps being distributed using probe-admin and may still reach VM-C.

D:

Inbound NAT rules map maintenance access to a particular backend; they do not choose pool members for the application load-balancing rule or change its health-probe association. SSH accessibility is not proof of application readiness.

Question 758

An internal Standard Load Balancer is being added to subnet sn-web at 10.8.12.0/28. Azure reports that no usable private IP address remains for the frontend after existing NIC and reserved allocations. Backend membership and health probes are otherwise valid. Which change addresses the deployment failure?

  1. Free a usable private address in the subnet or perform a supported subnet expansion before assigning the internal frontend IP.
  2. Switch the internal load balancer to a public IPv4 frontend and keep describing it as private.
  3. Change the backend listener port from 443 to 8443 without revisiting the subnet capacity.
  4. Add additional NIC IP configurations to the backend pool so Azure can borrow one for the frontend.

Explanation

Correct Answer

A:

Internal Load Balancer frontends use private addresses allocated from the associated virtual network subnet. A subnet with no available address cannot supply another frontend address; existing backend settings do not change that limit. Reclaiming an unused address or safely expanding the subnet while respecting occupied addresses and Azure reservations resolves the actual allocation constraint. The administrator should then configure a valid private frontend IP and verify routing to the backend, without exposing the service publicly.

Incorrect Answers

B:

A public frontend has different exposure and resource requirements from an internal private frontend. Substituting a public IP violates the stipulated private network design rather than increasing capacity inside sn-web. It may also introduce an unwanted Internet ingress path for a workload intended to remain private.

C:

Changing a load-balancing rule’s ports alters how traffic is forwarded after a frontend is allocated. It does not create additional usable private IP addresses in sn-web. The deployment failure occurs before the port mapping can solve any connection problem, so the proposed action is unrelated.

D:

NIC IP configurations are backend targets, not an alternate inventory of frontend addresses that Azure can borrow without allocating an address to the load balancer. Adding more backend IP configurations may further consume subnet addresses and worsen the capacity shortage. Repair the frontend allocation space instead.

Question 759

An internet-facing multiplayer game sends UDP packets on port 27015 to several healthy Azure VM servers. A newly configured TCP-only Azure Load Balancer rule does not distribute these UDP datagrams. What is the direct fix?

  1. Add an HTTP health probe to the unchanged TCP-only load-balancing rule.
  2. Configure a UDP load-balancing rule on port 27015 that targets the appropriate backend pool.
  3. Make the public Load Balancer frontend zone-resilient but leave its protocol set to TCP.
  4. Create another TCP-only frontend-to-backend rule on port 27015, without selecting UDP.

Explanation

Correct Answer

B:

Standard Azure Load Balancer supports UDP as well as TCP. Setting the frontend and backend rule protocol to UDP on the game port enables packet distribution to the selected pool, while a suitable health probe controls backend eligibility independently.

Incorrect Answers

A:

An HTTP probe can determine backend application health, but it does not convert a TCP-only forwarding rule into one that accepts UDP datagrams. The failure is a protocol mismatch in the load-balancing rule.

C:

Zone redundancy can improve frontend resilience across zones, but does not change the protocol field of an existing TCP-only rule. UDP game packets still will not match it.

D:

A second TCP rule on the correct numeric port still matches TCP flows, not UDP datagrams. The transport protocol must be UDP; matching only the port number is insufficient.

Question 760

An Azure Standard Load Balancer distributes TCP traffic directly to VM backends. The application wants the original client source IP, but a developer proposes that Load Balancer generate an HTTP `X-Forwarded-For` header. What is accurate?

  1. Standard Load Balancer always terminates HTTP requests and creates X-Forwarded-For headers before forwarding.
  2. Use a storage account SAS to insert original source headers into TCP packets.
  3. The Layer 4 Load Balancer normally preserves client source IP in backend flows but does not operate as an HTTP reverse proxy that adds X-Forwarded-For.
  4. A health probe can be configured to rewrite each application HTTP request header.

Explanation

Correct Answer

C:

Layer 4 forwarding preserves client-address behavior appropriate to the flow; X-Forwarded-For requires an HTTP-aware proxy such as Application Gateway.

Incorrect Answers

A:

An Azure Load Balancer forwards transport flows at Layer 4, not by parsing every HTTP request as a reverse proxy.

B:

A SAS token is an Azure Storage authorization mechanism, not an HTTP request-header transformation feature.

D:

Health probes test backend health and do not add forwarding headers to live client traffic.