McAfee-Secured Website

Exam Bundle

Exam Code: AZ-900

Exam Name Microsoft Azure Fundamentals

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified Azure Fundamentals

Microsoft AZ-900 Bundle $25.00

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

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

  • Questions & Answers

    AZ-900 Questions & Answers

    482 Questions & Answers

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

  • AZ-900 Video Course

    AZ-900 Video Course

    85 Video Lectures

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

    Description

    This course will improve your knowledge and skills required to pass Microsoft Azure Fundamentals exam.

Microsoft Azure Fundamentals (AZ-900) 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: $164.98
Bundle Price: $139.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    482 Questions

    $124.99
  • AZ-900 Video Course

    Video Course

    85 Video Lectures

    $39.99

Microsoft AZ-900 Practice Test 13

Question 120

A web app is slow because the database has a serial lock, and a team proposes adding thousands of web replicas. Which observed behavior proves the intended design?

  1. Request latency remains high.
  2. All replicas wait on the same lock.
  3. Lock contention decreases and application response meets the target after a measured fix.
  4. Queries remain blocked despite improved charts.

Explanation

Correct Answer

C:

The observed result demonstrates the case requirement: scaling the wrong tier does not repair a shared serial database dependency.

Incorrect Answers

A:

This observation falls short because log tier selection is unrelated to database transaction locking; the case requires lock contention decreases and application response meets the target after a measured fix.

B:

This observation falls short because shared database serialization remains the limiting resource; the case requires lock contention decreases and application response meets the target after a measured fix.

D:

This observation falls short because visibility alone does not fix contention; the case requires lock contention decreases and application response meets the target after a measured fix.

Question 121

A zone-redundant application still relies on one DNS service configuration unavailable during a planned outage. What should the team choose?

  1. Remove shared single points of failure in dependent services.
  2. Count web replicas while ignoring DNS dependency health.
  3. Increase disk replicas without testing endpoint resolution.
  4. Document availability only from portal deployment success.

Explanation

Correct Answer

A:

Application availability depends on dependencies, not just redundant compute instances.

Incorrect Answers

B:

Compute redundancy cannot fix an unavailable resolver.

C:

Data durability does not assure network name resolution.

D:

Successful creation does not test end-to-end service continuity.

Question 122

A zone-redundant application still relies on one DNS service configuration unavailable during a planned outage. Which expected outcome differentiates a successful configuration?

  1. Users cannot reach healthy web instances.
  2. Real customer connections fail.
  3. Failover tests show name resolution and application access continue through a zonal incident.
  4. Connections fail on hostname lookup.

Explanation

Correct Answer

C:

The observed result demonstrates the case requirement: application availability depends on dependencies, not just redundant compute instances.

Incorrect Answers

A:

This observation falls short because compute redundancy cannot fix an unavailable resolver; the case requires failover tests show name resolution and application access continue through a zonal incident.

B:

This observation falls short because successful creation does not test end-to-end service continuity; the case requires failover tests show name resolution and application access continue through a zonal incident.

D:

This observation falls short because data durability does not assure network name resolution; the case requires failover tests show name resolution and application access continue through a zonal incident.

Question 123

A data engineering team needs to preserve file bytes against storage-node failures but its web service may still have downtime. Which option addresses the scenario without violating its constraints?

  1. Treat VM CPU allocation as a file-integrity mechanism.
  2. Distinguish storage durability design from separate application high availability design.
  3. Delete all backups because the service SLA appears high.
  4. Call multiple file copies proof that the web application never fails.

Explanation

Correct Answer

B:

Durability and availability are related but different service qualities.

Incorrect Answers

A:

Compute size does not protect object durability.

C:

An availability commitment does not prevent all logical data loss.

D:

Data survival does not guarantee application processes remain healthy.

Question 124

A data engineering team needs to preserve file bytes against storage-node failures but its web service may still have downtime. Which observation validates that this was correctly addressed?

  1. The API becomes unavailable despite intact files.
  2. Deleted files cannot be restored.
  3. Storage loss persists after resizing.
  4. Files survive a simulated storage-node fault while application uptime is measured independently.

Explanation

Correct Answer

D:

The observed result demonstrates the case requirement: durability and availability are related but different service qualities.

Incorrect Answers

A:

This observation falls short because data survival does not guarantee application processes remain healthy; the case requires files survive a simulated storage-node fault while application uptime is measured independently.

B:

This observation falls short because an availability commitment does not prevent all logical data loss; the case requires files survive a simulated storage-node fault while application uptime is measured independently.

C:

This observation falls short because compute size does not protect object durability; the case requires files survive a simulated storage-node fault while application uptime is measured independently.

Question 125

A team moves a custom app from self-managed Azure VMs to managed web hosting to lower guest maintenance work. Which action should the administrator take?

  1. Use managed PaaS runtime features while retaining application ownership.
  2. Stop updating customer application dependencies.
  3. Remove monitoring because runtime maintenance is managed.
  4. Keep patching managed host kernels as if they were customer VMs.

Explanation

Correct Answer

A:

PaaS manageability reduces infrastructure maintenance scope for developers.

Incorrect Answers

B:

PaaS patching does not replace code maintenance.

C:

Application health still requires visibility.

D:

The runtime host is provider-managed.

Question 126

A team moves a custom app from self-managed Azure VMs to managed web hosting to lower guest maintenance work. Which result confirms that the requirement is met?

  1. Known vulnerable libraries remain in deployments.
  2. Developers have no privileged host access.
  3. App failures go undetected.
  4. Provider runtime updates require less customer guest OS patching, with app releases still controlled.

Explanation

Correct Answer

D:

The observed result demonstrates the case requirement: paaS manageability reduces infrastructure maintenance scope for developers.

Incorrect Answers

A:

This observation falls short because paaS patching does not replace code maintenance; the case requires provider runtime updates require less customer guest OS patching, with app releases still controlled.

B:

This observation falls short because the runtime host is provider-managed; the case requires provider runtime updates require less customer guest OS patching, with app releases still controlled.

C:

This observation falls short because application health still requires visibility; the case requires provider runtime updates require less customer guest OS patching, with app releases still controlled.

Question 127

A network service must respond to surges but its autoscale trigger is based on an unrelated metric. What should the team select for the stated goal?

  1. Base scale decisions on load signals relevant to saturation and customer latency.
  2. Disable request metrics to simplify the rule.
  3. Use an arbitrary constant that is never reached.
  4. Trigger scale on resource group name changes.

Explanation

Correct Answer

A:

An effective autoscale rule needs an appropriate performance signal.

Incorrect Answers

B:

The controller then lacks suitable feedback.

C:

A useless threshold prevents elasticity.

D:

Names do not indicate workload pressure.

Question 128

A network service must respond to surges but its autoscale trigger is based on an unrelated metric. Which observed behavior proves the intended design?

  1. Traffic increases without capacity response.
  2. Queueing grows with no scale event.
  3. Scale events correlate with actual demand and service performance improves.
  4. Instances never respond to busy periods.

Explanation

Correct Answer

C:

The observed result demonstrates the case requirement: an effective autoscale rule needs an appropriate performance signal.

Incorrect Answers

A:

This observation falls short because the controller then lacks suitable feedback; the case requires scale events correlate with actual demand and service performance improves.

B:

This observation falls short because a useless threshold prevents elasticity; the case requires scale events correlate with actual demand and service performance improves.

D:

This observation falls short because names do not indicate workload pressure; the case requires scale events correlate with actual demand and service performance improves.

Question 129

A finance application uses scaled-out web servers but has just one database instance with no recovery plan. What should the team choose?

  1. Add more independent web replicas only.
  2. Add appropriate database resilience and test the full dependency chain.
  3. Archive application logs as the main availability plan.
  4. Increase the frontend's public IP quota.

Explanation

Correct Answer

B:

A resilient frontend cannot conceal a critical single backend dependency.

Incorrect Answers

A:

The single database still stops the entire application.

C:

Log retention does not replace database recovery.

D:

IP availability is not database failover.

Question 130

A finance application uses scaled-out web servers but has just one database instance with no recovery plan. Which expected outcome differentiates a successful configuration?

  1. The application loses access to records.
  2. Database failure tests preserve or restore transactions within agreed objectives.
  3. Web pages return errors when data access fails.
  4. Transactions fail after database loss.

Explanation

Correct Answer

B:

The observed result demonstrates the case requirement: a resilient frontend cannot conceal a critical single backend dependency.

Incorrect Answers

A:

This observation falls short because iP availability is not database failover; the case requires database failure tests preserve or restore transactions within agreed objectives.

C:

This observation falls short because the single database still stops the entire application; the case requires database failure tests preserve or restore transactions within agreed objectives.

D:

This observation falls short because log retention does not replace database recovery; the case requires database failure tests preserve or restore transactions within agreed objectives.