McAfee-Secured Website

Exam Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

Microsoft AZ-104 Bundle $44.99

100% Microsoft AZ-104 Guaranteed Success With Testking Training Materials

Get Real AZ-104 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual AZ-104 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • AZ-104 Video Course

    AZ-104 Video Course

    132 Video Lectures

    AZ-104 Video Course is developed by Microsoft Professionals to help you pass the AZ-104 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Azure Administrator exam.
  • Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Developed by industry experts, this 458-page guide spells out in painstaking detail all of the information you need to ace AZ-104 exam.

Microsoft Azure Administrator (AZ-104) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
  • AZ-104 Video Course

    Video Course

    132 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 22

Question 210

A security reviewer rejects Azure Bastion because private VMs have no public IP addresses. The operator plans to assign each VM a public IP solely for Bastion access. What is the correct approach?

  1. Attach a public IP to the Bastion-connected VM but restrict inbound RDP to the Bastion host IP.
  2. Create a VM inbound NAT rule with the Bastion host public IP as destination and require the target VM to have its own public IP.
  3. Keep the VM private and use the supported Bastion connection through its configured host and dedicated subnet.
  4. Attach a public IP to every VM because Bastion requires direct internet RDP reachability.

Explanation

Correct Answer

C:

Bastion connects to target VMs using private networking and managed access. The private VM does not need an individual public IP.

Incorrect Answers

A:

Bastion is intended to reach a private VM address; a public IP on the target VM is unnecessary even if restricted.

B:

Bastion uses its managed connection path to private VM network addresses. One-to-one public NAT on each VM is not required.

D:

Adding public IPs unnecessarily expands exposure and defeats a primary Bastion design advantage.

Question 211

A backend pool behind a Standard Azure Load Balancer experiences intermittent outbound connection failures when many concurrent sessions use the same frontend. Application health remains fine. Which capacity issue should the administrator investigate?

  1. Increase the outbound connection idle timeout without checking SNAT allocation, and longer-lived translations create more free ports.
  2. Examine outbound SNAT port allocation and consider supported explicit outbound rules or NAT Gateway design.
  3. Add additional inbound health probes to expand the outbound SNAT port pool.
  4. Change Load Balancer distribution mode to source-IP affinity and all outbound SNAT port limits disappear.

Explanation

Correct Answer

B:

Shared outbound SNAT port capacity can be exhausted under high connection churn. A deliberate outbound architecture and observability can prevent failures.

Incorrect Answers

A:

Longer idle timeouts may keep SNAT ports occupied. The operator should inspect allocation and choose a suitable outbound scaling design.

C:

Health probes determine backend readiness, not how many outbound source ports are allocated for SNAT.

D:

Inbound session affinity changes backend selection, not the outbound SNAT port allocation budget.

Question 212

An existing Standard internal Azure Load Balancer has a private frontend address allocated dynamically from its configured subnet. The client application requires the same private service IP across ordinary frontend updates and backend VM replacements. Which specific frontend setting should be selected?

  1. Change the internal load balancer frontend assignment to Static and configure an available private IP from the selected frontend subnet.
  2. Keep dynamic frontend allocation and pin the current backend VM NIC IPs, because backend address stability guarantees the frontend IP never changes.
  3. Use a public Standard Load Balancer frontend instead, because only public frontends can have static IP allocation.
  4. Increase private DNS record TTL for the existing dynamic frontend, because longer caching reserves its allocated Azure private address.

Explanation

Correct Answer

A:

Azure internal Load Balancer frontends support Static or Dynamic private IP assignment. Static explicitly maintains the chosen frontend address, independent of backend VM replacement.

Incorrect Answers

B:

Backend NIC allocation and frontend IP allocation are separate settings. A dynamically assigned ILB private frontend can change even with stable backends.

C:

Internal load-balancer private frontends also support static allocation. A public frontend would violate the internal-only service requirement.

D:

Private DNS caching affects name resolution, not the Azure IP address allocation method of the load balancer frontend.

Question 213

A Standard Load Balancer uses a TCP probe on port 80 while the new backend only listens on port 8443. Backend VMs are healthy, but the probe marks them down. What should be changed?

  1. Change only the Load Balancer frontend listening port to 8443 while keeping the health probe on port 80.
  2. Set the health probe to a reachable supported service port or endpoint that accurately reflects backend readiness.
  3. Increase the Load Balancer probe interval while continuing to probe the inactive backend TCP port 80.
  4. Change the TCP probe protocol to HTTP but continue targeting a port on which no application process is listening.

Explanation

Correct Answer

B:

Health probes must reach a configured listener on the backend. Testing a closed port produces an unhealthy result even if another application port works.

Incorrect Answers

A:

Frontend port mapping controls client-flow translation but does not repair a health probe that still tests an inactive backend listener on port 80.

C:

Increasing probe frequency or interval cannot make an application listen on a closed port; target the live readiness endpoint.

D:

Changing probe protocol alone does not help if the probe still targets a closed or nonresponsive backend endpoint.

Question 214

A VM in an Azure VNet uses a custom DNS server hosted on-premises. The VM can reach that server, but records in a linked Azure private DNS zone do not resolve. The on-premises DNS server cannot reach Azure-provided DNS at 168.63.129.16 directly. What is the supported corrective approach?

  1. Create public DNS records for the private endpoint FQDN and leave the on-premises resolver without a private forwarding path.
  2. Configure appropriate conditional forwarding toward an Azure DNS Private Resolver inbound endpoint or an Azure-hosted forwarder able to query Azure DNS.
  3. Remove the private DNS VNet link so the custom resolver can discover the private records without forwarding.
  4. Point the on-premises DNS server directly to 168.63.129.16 across VPN, and rely on that Azure-provided address being reachable outside the Azure VNet.

Explanation

Correct Answer

B:

The forwarding target must be reachable from the custom/on-premises resolver; an Azure Private Resolver inbound endpoint or VNet forwarder can resolve linked private zones.

Incorrect Answers

A:

Public DNS records do not implement correct private-name resolution through the linked Azure private zone and may expose internal addresses.

C:

Removing the link weakens Azure private-zone resolution instead of making the authoritative zone reachable to the on-premises resolver.

D:

Azure-provided DNS at 168.63.129.16 is accessible only through appropriate Azure network context; a Private Resolver inbound endpoint or Azure forwarder is needed for on-premises queries.

Question 215

An engineer creates a backend pool and health probe but no load balancing rule. Clients connect to the intended frontend and get no response. Which remaining control-plane object is needed?

  1. Configure only an inbound NAT rule to one VM and it distributes every frontend connection to the backend pool.
  2. Create a load-balancing rule mapping the frontend port and protocol to the backend port and probe.
  3. Assign the health probe directly to the frontend IP without creating the required frontend-to-backend rule.
  4. Add a second backend pool but leave the existing frontend unbound to any rule.

Explanation

Correct Answer

B:

A load-balancing rule binds the frontend listener to backend pool selection and health probe. A pool and probe alone do not define a service mapping.

Incorrect Answers

A:

An inbound NAT rule targets an individual backend for port forwarding; it is not the pool load-balancing rule the scenario lacks.

C:

A health probe assesses backend readiness but does not establish a load-balancing traffic mapping.

D:

More backend pools do not route frontend connections. A load-balancing rule is the missing object.

Question 216

A company deploys Azure Monitor Agent to a fleet of Windows VMs but finds no requested performance counter data in its workspace. What separate configuration should be checked?

  1. Associate an appropriate data collection rule specifying the counters and destination with the target VMs.
  2. Create an Azure Monitor metric alert on VM percentage CPU and it automatically collects Windows guest performance counters.
  3. Configure only VM-level platform diagnostic settings without an Azure Monitor Agent data collection rule.
  4. Change Azure Monitor Agent extension status to Succeeded but leave it without a relevant data collection rule association.

Explanation

Correct Answer

A:

Azure Monitor Agent follows data collection rules for supported guest telemetry. The rule association and destination determine which counters are actually ingested.

Incorrect Answers

B:

An alert evaluates available metrics but does not configure the Azure Monitor Agent to send the requested guest performance data.

C:

Platform resource logs differ from agent-collected Windows guest counters. Data collection rules control guest collection.

D:

Successful agent installation does not define which performance counters to collect or where to deliver them.

Question 217

An investigator must identify who deleted an Azure VM resource at 14:30 yesterday. Which native log source primarily records the management operation?

  1. Inspect Azure Monitor VM guest performance metrics around 14:30 and infer which Azure principal issued the deletion.
  2. Inspect only the VM guest Windows Event Log after the VM has been deleted.
  3. Check the Azure Activity Log for subscription control-plane delete events and related caller metadata.
  4. Query network NSG flow logs and they record every ARM delete call.

Explanation

Correct Answer

C:

Activity Log captures Azure control-plane operations such as resource deletion and can identify the initiating identity. Its retention/export configuration matters.

Incorrect Answers

A:

VM performance metrics show workload activity, not the identity or Azure Resource Manager operation that deleted the VM resource.

B:

A deleted guest's local event log may be unavailable and does not reliably record the ARM management call.

D:

Packet flow telemetry cannot replace the Azure management activity record.

Question 218

During a scheduled maintenance window, paging stops because an Azure Monitor alert processing rule suppresses actions. The operations team assumes alert conditions are no longer evaluated. What should be clarified?

  1. Disable the Azure Monitor action group during the maintenance window and use its disabled state to stop the metric rule from evaluating.
  2. Action suppression can prevent configured notifications while alert rule evaluation and alert records continue under the applicable rule.
  3. Configure alert action suppression as the recovery step that automatically repairs the resource state underlying the alert.
  4. Attach a scheduled processing rule to the monitored alert and use its activation to delete the alert definition and its query permanently.

Explanation

Correct Answer

B:

Alert processing rules control handling of actions rather than underlying resource health. Operators should distinguish alert state from notification delivery.

Incorrect Answers

A:

Notification routing and alert-rule evaluation are distinct. Disabling an action group does not turn off the rule's conditions or the observed underlying telemetry.

C:

Action suppression affects notification handling, not resource remediation. The original failure must be investigated and resolved independently.

D:

A processing rule changes how actions are applied to matching alerts; it does not delete the alert rule or disable its evaluation logic.

Question 219

An analyst has Reader on a resource but cannot query a workspace containing its exported diagnostics. What should be evaluated without granting broad subscription Owner?

  1. Check the Log Analytics workspace data access model and the appropriate scoped log-query permissions.
  2. Grant only Monitoring Metrics Publisher on the workspace and telemetry ingestion rights authorize all Log Analytics queries.
  3. Disable the resource diagnostic settings and the already-ingested workspace data will become available to unauthorized users.
  4. Grant Contributor on the source VM without checking the workspace query permission model.

Explanation

Correct Answer

A:

Workspace query authorization can differ from the source resource's Reader rights depending on the workspace access control model. Grant the minimum necessary data-query scope.

Incorrect Answers

B:

Metrics publishing rights do not supply the workspace log-query permissions needed by the analyst. Evaluate the query access model and scope.

C:

Stopping ingestion does not appropriately change workspace access. It also removes new telemetry needed for operations.

D:

VM control-plane write permissions are not necessarily equivalent to the workspace-specific query authorization required.

Question 220

A storage metric shows elevated errors, but the team wants to distinguish authorization failures from server errors where the metric supports a ResponseType dimension. What should the alert designer use?

  1. Split or filter the supported metric dimensions in an Azure Monitor metric alert to isolate the response category.
  2. Set a resource tag ResponseType=AuthorizationFailure and all Azure metric time series are partitioned by this tag.
  3. Create one alert on total Transactions without splitting the metric by ResponseType.
  4. Filter the metrics chart by resource group name rather than the supported response-category dimension.

Explanation

Correct Answer

A:

Metric dimensions let rules evaluate supported series by attributes. Valid dimension names and availability must be confirmed for the metric.

Incorrect Answers

B:

Resource tags are metadata and are not automatically the metric’s supported ResponseType dimension.

C:

Aggregate transactions do not isolate authorization errors from server failures when the metric supports a relevant dimension.

D:

Resource scope alone does not separate authorization and server response types within the same storage account metric.