Microsoft AZ-305 Relational Database Scalability Practice Test

 

Topic 09 focuses on Relational Database Scalability, Performance, and Protection for the Microsoft Certified: Azure Solutions Architect Expert certification and the AZ-305 exam, using Microsoft Azure solution-architecture scenarios. For broader exam preparation, review the Microsoft Azure Solutions Architect Expert AZ-305 Exam Dumps page. Each question includes a concise explanation of the correct answer and the technical reason the other choices are incorrect.

Question 1

To meet long-term database backup retention or compliance requirements, which Azure design option should be selected?

  1. PostgreSQL Flexible Server zone-redundant high availability
  2. SQL Server Always On availability groups on Azure VMs
  3. Azure SQL read scale-out
  4. Azure SQL long-term retention (LTR)

Correct Answer: D

 

Correct Answer

Answer D is correct because Azure SQL long-term retention (LTR) is designed to meet long-term database backup retention or compliance requirements. Azure SQL long-term retention (LTR) stores selected full backups for extended retention periods beyond standard point-in-time restore windows.

Incorrect Answers

Answer A is incorrect because PostgreSQL Flexible Server zone-redundant high availability can be useful in Azure architectures, but its primary role is to protect managed PostgreSQL against zone-level failures; it is not the best match for the stated priority.

Answer B is incorrect because SQL Server Always On availability groups on Azure VMs can be useful in Azure architectures, but its primary role is to retain SQL Server-native HA control for virtual-machine-based deployments; it is not the best match for the stated priority.

Answer C is incorrect because Azure SQL read scale-out can be useful in Azure architectures, but its primary role is to offload read-heavy queries from the primary database; it is not the best match for the stated priority.

 

Question 2

When considering PostgreSQL read replica, which requirement supports that choice?

  1. To simplify multi-database regional failover and connection redirection.
  2. To retain SQL Server-native HA control for virtual-machine-based deployments.
  3. To offload read workloads from a PostgreSQL primary server.
  4. To recover a managed SQL database to an earlier point after logical corruption or deletion.

Correct Answer: C

 

Correct Answer

Answer C is correct because PostgreSQL read replica creates asynchronous replicas for read scaling and supported disaster-recovery scenarios.

Incorrect Answers

Answer A is incorrect because that outcome is more directly associated with Azure SQL failover group, not PostgreSQL read replica.

Answer B is incorrect because that outcome is more directly associated with SQL Server Always On availability groups on Azure VMs, not PostgreSQL read replica.

Answer D is incorrect because that outcome is more directly associated with Azure SQL automatic backups, not PostgreSQL read replica.

 

Question 3

An enterprise architect needs to simplify multi-database regional failover and connection redirection. Which Azure service or capability is the best fit?

  1. Azure SQL zone redundancy
  2. Azure SQL long-term retention (LTR)
  3. Azure SQL failover group
  4. Azure SQL elastic pool scaling

Correct Answer: C

 

Correct Answer

Answer C is correct because Azure SQL failover group manages geo-replication and listener endpoints for groups of databases with policy-based or manual failover. It directly meets the requirement to simplify multi-database regional failover and connection redirection.

Incorrect Answers

Answer A is incorrect because Azure SQL zone redundancy is used to protect a database from a datacenter or zone failure within one region; that does not directly satisfy the requirement in this scenario.

Answer B is incorrect because Azure SQL long-term retention (LTR) is used to meet long-term database backup retention or compliance requirements; that does not directly satisfy the requirement in this scenario.

Answer D is incorrect because Azure SQL elastic pool scaling is used to scale a group of databases with variable resource consumption; that does not directly satisfy the requirement in this scenario.

 

Question 4

To protect managed PostgreSQL against zone-level failures, which Azure design option should be selected?

  1. PostgreSQL Flexible Server zone-redundant high availability
  2. Azure SQL active geo-replication
  3. Azure SQL zone redundancy
  4. PostgreSQL read replica

Correct Answer: A

 

Correct Answer

Answer A is correct because PostgreSQL Flexible Server zone-redundant high availability is designed to protect managed PostgreSQL against zone-level failures. PostgreSQL Flexible Server zone-redundant high availability maintains a synchronized standby in another Availability Zone in supported regions.

Incorrect Answers

Answer B is incorrect because Azure SQL active geo-replication can be useful in Azure architectures, but its primary role is to provide database-level geographic redundancy with readable secondaries; it is not the best match for the stated priority.

Answer C is incorrect because Azure SQL zone redundancy can be useful in Azure architectures, but its primary role is to protect a database from a datacenter or zone failure within one region; it is not the best match for the stated priority.

Answer D is incorrect because PostgreSQL read replica can be useful in Azure architectures, but its primary role is to offload read workloads from a PostgreSQL primary server; it is not the best match for the stated priority.

 

Question 5

When considering Azure SQL active geo-replication, which requirement supports that choice?

  1. To simplify multi-database regional failover and connection redirection.
  2. To provide database-level geographic redundancy with readable secondaries.
  3. To recover a managed SQL database to an earlier point after logical corruption or deletion.
  4. To offload read-heavy queries from the primary database.

Correct Answer: B

 

Correct Answer

Answer B is correct because Azure SQL active geo-replication creates readable secondary databases in other regions for supported Azure SQL Database scenarios and enables controlled failover.

Incorrect Answers

Answer A is incorrect because that outcome is more directly associated with Azure SQL failover group, not Azure SQL active geo-replication.

Answer C is incorrect because that outcome is more directly associated with Azure SQL automatic backups, not Azure SQL active geo-replication.

Answer D is incorrect because that outcome is more directly associated with Azure SQL read scale-out, not Azure SQL active geo-replication.

 

Question 6

When considering Azure SQL automatic backups, which requirement supports that choice?

  1. To offload read workloads from a PostgreSQL primary server.
  2. To scale a group of databases with variable resource consumption.
  3. To recover a managed SQL database to an earlier point after logical corruption or deletion.
  4. To meet long-term database backup retention or compliance requirements.

Correct Answer: C

 

Correct Answer

Answer C is correct because Azure SQL automatic backups provide built-in point-in-time restore capability within the configured retention window.

Incorrect Answers

Answer A is incorrect because that outcome is more directly associated with PostgreSQL read replica, not Azure SQL automatic backups.

Answer B is incorrect because that outcome is more directly associated with Azure SQL elastic pool scaling, not Azure SQL automatic backups.

Answer D is incorrect because that outcome is more directly associated with Azure SQL long-term retention (LTR), not Azure SQL automatic backups.

 

Question 7

Which Azure capability provide built-in point-in-time restore capability within the configured retention window?

  1. PostgreSQL read replica
  2. Azure SQL long-term retention (LTR)
  3. Azure SQL automatic backups
  4. Azure SQL elastic pool scaling

Correct Answer: C

 

Correct Answer

Answer C is correct because Azure SQL automatic backups matches the described capability and is intended to recover a managed SQL database to an earlier point after logical corruption or deletion.

Incorrect Answers

Answer A is incorrect because PostgreSQL read replica is intended to offload read workloads from a PostgreSQL primary server, which is a different architectural function.

Answer B is incorrect because Azure SQL long-term retention (LTR) is intended to meet long-term database backup retention or compliance requirements, which is a different architectural function.

Answer D is incorrect because Azure SQL elastic pool scaling is intended to scale a group of databases with variable resource consumption, which is a different architectural function.

 

Question 8

Which Azure capability creates asynchronous replicas for read scaling and supported disaster-recovery scenarios?

  1. Azure SQL automatic backups
  2. SQL Server Always On availability groups on Azure VMs
  3. PostgreSQL read replica
  4. Azure SQL failover group

Correct Answer: C

 

Correct Answer

Answer C is correct because PostgreSQL read replica matches the described capability and is intended to offload read workloads from a PostgreSQL primary server.

Incorrect Answers

Answer A is incorrect because Azure SQL automatic backups is intended to recover a managed SQL database to an earlier point after logical corruption or deletion, which is a different architectural function.

Answer B is incorrect because SQL Server Always On availability groups on Azure VMs is intended to retain SQL Server-native HA control for virtual-machine-based deployments, which is a different architectural function.

Answer D is incorrect because Azure SQL failover group is intended to simplify multi-database regional failover and connection redirection, which is a different architectural function.

 

Question 9

An organization wants to retain SQL Server-native HA control for virtual-machine-based deployments. Which design choice most directly meets the requirement?

  1. Azure SQL zone redundancy
  2. SQL Server Always On availability groups on Azure VMs
  3. Azure SQL active geo-replication
  4. Azure SQL long-term retention (LTR)

Correct Answer: B

 

Correct Answer

Answer B is correct because SQL Server Always On availability groups on Azure VMs provide SQL Server replica-based high availability or disaster recovery when running SQL Server on IaaS. It directly meets the requirement to retain SQL Server-native HA control for virtual-machine-based deployments.

Incorrect Answers

Answer A is incorrect because Azure SQL zone redundancy is used to protect a database from a datacenter or zone failure within one region; that does not directly satisfy the requirement in this scenario.

Answer C is incorrect because Azure SQL active geo-replication is used to provide database-level geographic redundancy with readable secondaries; that does not directly satisfy the requirement in this scenario.

Answer D is incorrect because Azure SQL long-term retention (LTR) is used to meet long-term database backup retention or compliance requirements; that does not directly satisfy the requirement in this scenario.

 

Question 10

To scale a group of databases with variable resource consumption, which Azure design option should be selected?

  1. Azure SQL elastic pool scaling
  2. PostgreSQL Flexible Server zone-redundant high availability
  3. Azure SQL failover group
  4. SQL Server Always On availability groups on Azure VMs

Correct Answer: A

 

Correct Answer

Answer A is correct because Azure SQL elastic pool scaling is designed to scale a group of databases with variable resource consumption. Azure SQL elastic pool scaling allocates shared performance resources across databases and can be resized as aggregate demand changes.

Incorrect Answers

Answer B is incorrect because PostgreSQL Flexible Server zone-redundant high availability can be useful in Azure architectures, but its primary role is to protect managed PostgreSQL against zone-level failures; it is not the best match for the stated priority.

Answer C is incorrect because Azure SQL failover group can be useful in Azure architectures, but its primary role is to simplify multi-database regional failover and connection redirection; it is not the best match for the stated priority.

Answer D is incorrect because SQL Server Always On availability groups on Azure VMs can be useful in Azure architectures, but its primary role is to retain SQL Server-native HA control for virtual-machine-based deployments; it is not the best match for the stated priority.

 

Question 11

Which Azure capability creates readable secondary databases in other regions for supported Azure SQL Database scenarios and enables controlled failover?

  1. Azure SQL failover group
  2. Azure SQL read scale-out
  3. Azure SQL active geo-replication
  4. Azure SQL automatic backups

Correct Answer: C

 

Correct Answer

Answer C is correct because Azure SQL active geo-replication matches the described capability and is intended to provide database-level geographic redundancy with readable secondaries.

Incorrect Answers

Answer A is incorrect because Azure SQL failover group is intended to simplify multi-database regional failover and connection redirection, which is a different architectural function.

Answer B is incorrect because Azure SQL read scale-out is intended to offload read-heavy queries from the primary database, which is a different architectural function.

Answer D is incorrect because Azure SQL automatic backups is intended to recover a managed SQL database to an earlier point after logical corruption or deletion, which is a different architectural function.

 

Question 12

When considering Azure SQL long-term retention (LTR), which requirement supports that choice?

  1. To protect managed PostgreSQL against zone-level failures.
  2. To meet long-term database backup retention or compliance requirements.
  3. To offload read-heavy queries from the primary database.
  4. To retain SQL Server-native HA control for virtual-machine-based deployments.

Correct Answer: B

 

Correct Answer

Answer B is correct because Azure SQL long-term retention (LTR) stores selected full backups for extended retention periods beyond standard point-in-time restore windows.

Incorrect Answers

Answer A is incorrect because that outcome is more directly associated with PostgreSQL Flexible Server zone-redundant high availability, not Azure SQL long-term retention (LTR).

Answer C is incorrect because that outcome is more directly associated with Azure SQL read scale-out, not Azure SQL long-term retention (LTR).

Answer D is incorrect because that outcome is more directly associated with SQL Server Always On availability groups on Azure VMs, not Azure SQL long-term retention (LTR).

 

Question 13

Which Azure capability maintains a synchronized standby in another Availability Zone in supported regions?

  1. Azure SQL active geo-replication
  2. PostgreSQL Flexible Server zone-redundant high availability
  3. Azure SQL zone redundancy
  4. PostgreSQL read replica

Correct Answer: B

 

Correct Answer

Answer B is correct because PostgreSQL Flexible Server zone-redundant high availability matches the described capability and is intended to protect managed PostgreSQL against zone-level failures.

Incorrect Answers

Answer A is incorrect because Azure SQL active geo-replication is intended to provide database-level geographic redundancy with readable secondaries, which is a different architectural function.

Answer C is incorrect because Azure SQL zone redundancy is intended to protect a database from a datacenter or zone failure within one region, which is a different architectural function.

Answer D is incorrect because PostgreSQL read replica is intended to offload read workloads from a PostgreSQL primary server, which is a different architectural function.

 

Question 14

For Azure SQL long-term retention (LTR), which statement is accurate?

  1. Stores selected full backups for extended retention periods beyond standard point-in-time restore windows.
  2. Provide SQL Server replica-based high availability or disaster recovery when running SQL Server on IaaS.
  3. Routes read-only workloads to a readable secondary replica in supported tiers.
  4. Maintains a synchronized standby in another Availability Zone in supported regions.

Correct Answer: A

 

Correct Answer

Answer A is correct because Azure SQL long-term retention (LTR) stores selected full backups for extended retention periods beyond standard point-in-time restore windows.

Incorrect Answers

Answer B is incorrect because that description belongs to SQL Server Always On availability groups on Azure VMs, whose purpose is to retain SQL Server-native HA control for virtual-machine-based deployments.

Answer C is incorrect because that description belongs to Azure SQL read scale-out, whose purpose is to offload read-heavy queries from the primary database.

Answer D is incorrect because that description belongs to PostgreSQL Flexible Server zone-redundant high availability, whose purpose is to protect managed PostgreSQL against zone-level failures.

 

Question 15

Several databases already share an elastic pool, but aggregate resource demand now exceeds the current allocation. Which requirement justifies resizing the pool?

  1. To protect managed PostgreSQL against zone-level failures.
  2. To simplify multi-database regional failover and connection redirection.
  3. To retain SQL Server-native HA control for virtual-machine-based deployments.
  4. To scale a group of databases with variable resource consumption.

Correct Answer: D

 

Correct Answer

Answer D is correct because Azure SQL elastic pool scaling allocates shared performance resources across databases and can be resized as aggregate demand changes.

Incorrect Answers

Answer A is incorrect because that outcome is more directly associated with PostgreSQL Flexible Server zone-redundant high availability, not Azure SQL elastic pool scaling.

Answer B is incorrect because that outcome is more directly associated with Azure SQL failover group, not Azure SQL elastic pool scaling.

Answer C is incorrect because that outcome is more directly associated with SQL Server Always On availability groups on Azure VMs, not Azure SQL elastic pool scaling.

 

Question 16

For Azure SQL read scale-out, which statement is accurate?

  1. Routes read-only workloads to a readable secondary replica in supported tiers.
  2. Creates asynchronous replicas for read scaling and supported disaster-recovery scenarios.
  3. Creates readable secondary databases in other regions for supported Azure SQL Database scenarios and enables controlled failover.
  4. Allocates shared performance resources across databases and can be resized as aggregate demand changes.

Correct Answer: A

 

Correct Answer

Answer A is correct because Azure SQL read scale-out routes read-only workloads to a readable secondary replica in supported tiers.

Incorrect Answers

Answer B is incorrect because that description belongs to PostgreSQL read replica, whose purpose is to offload read workloads from a PostgreSQL primary server.

Answer C is incorrect because that description belongs to Azure SQL active geo-replication, whose purpose is to provide database-level geographic redundancy with readable secondaries.

Answer D is incorrect because that description belongs to Azure SQL elastic pool scaling, whose purpose is to scale a group of databases with variable resource consumption.

 

Question 17

To offload read-heavy queries from the primary database, which Azure design option should be selected?

  1. Azure SQL elastic pool scaling
  2. Azure SQL active geo-replication
  3. PostgreSQL read replica
  4. Azure SQL read scale-out

Correct Answer: D

 

Correct Answer

Answer D is correct because Azure SQL read scale-out routes read-only workloads to a readable secondary replica in supported tiers. It directly meets the requirement to offload read-heavy queries from the primary database.

Incorrect Answers

Answer A is incorrect because Azure SQL elastic pool scaling is used to scale a group of databases with variable resource consumption; that does not directly satisfy the requirement in this scenario.

Answer B is incorrect because Azure SQL active geo-replication is used to provide database-level geographic redundancy with readable secondaries; that does not directly satisfy the requirement in this scenario.

Answer C is incorrect because PostgreSQL read replica is used to offload read workloads from a PostgreSQL primary server; that does not directly satisfy the requirement in this scenario.

 

Question 18

When considering PostgreSQL Flexible Server zone-redundant high availability, which requirement supports that choice?

  1. To offload read workloads from a PostgreSQL primary server.
  2. To provide database-level geographic redundancy with readable secondaries.
  3. To protect a database from a datacenter or zone failure within one region.
  4. To protect managed PostgreSQL against zone-level failures.

Correct Answer: D

 

Correct Answer

Answer D is correct because PostgreSQL Flexible Server zone-redundant high availability maintains a synchronized standby in another Availability Zone in supported regions.

Incorrect Answers

Answer A is incorrect because that outcome is more directly associated with PostgreSQL read replica, not PostgreSQL Flexible Server zone-redundant high availability.

Answer B is incorrect because that outcome is more directly associated with Azure SQL active geo-replication, not PostgreSQL Flexible Server zone-redundant high availability.

Answer C is incorrect because that outcome is more directly associated with Azure SQL zone redundancy, not PostgreSQL Flexible Server zone-redundant high availability.

 

Question 19

To provide database-level geographic redundancy with readable secondaries, which Azure design option should be selected?

  1. Azure SQL automatic backups
  2. Azure SQL active geo-replication
  3. Azure SQL read scale-out
  4. Azure SQL failover group

Correct Answer: B

 

Correct Answer

Answer B is correct because Azure SQL active geo-replication is designed to provide database-level geographic redundancy with readable secondaries. Azure SQL active geo-replication creates readable secondary databases in other regions for supported Azure SQL Database scenarios and enables controlled failover.

Incorrect Answers

Answer A is incorrect because Azure SQL automatic backups can be useful in Azure architectures, but its primary role is to recover a managed SQL database to an earlier point after logical corruption or deletion; it is not the best match for the stated priority.

Answer C is incorrect because Azure SQL read scale-out can be useful in Azure architectures, but its primary role is to offload read-heavy queries from the primary database; it is not the best match for the stated priority.

Answer D is incorrect because Azure SQL failover group can be useful in Azure architectures, but its primary role is to simplify multi-database regional failover and connection redirection; it is not the best match for the stated priority.

 

Question 20

To protect a database from a datacenter or zone failure within one region, which Azure design option should be selected?

  1. Azure SQL automatic backups
  2. Azure SQL zone redundancy
  3. PostgreSQL Flexible Server zone-redundant high availability
  4. Azure SQL read scale-out

Correct Answer: B

 

Correct Answer

Answer B is correct because Azure SQL zone redundancy is designed to protect a database from a datacenter or zone failure within one region. Azure SQL zone redundancy places replicas across Availability Zones in supported service tiers and regions.

Incorrect Answers

Answer A is incorrect because Azure SQL automatic backups can be useful in Azure architectures, but its primary role is to recover a managed SQL database to an earlier point after logical corruption or deletion; it is not the best match for the stated priority.

Answer C is incorrect because PostgreSQL Flexible Server zone-redundant high availability can be useful in Azure architectures, but its primary role is to protect managed PostgreSQL against zone-level failures; it is not the best match for the stated priority.

Answer D is incorrect because Azure SQL read scale-out can be useful in Azure architectures, but its primary role is to offload read-heavy queries from the primary database; it is not the best match for the stated priority.

 

Question 21

A transaction-heavy Azure SQL workload is slowed by reporting queries. Which outcome best explains why an architect would use Azure SQL read scale-out?

  1. To offload read workloads from a PostgreSQL primary server.
  2. To provide database-level geographic redundancy with readable secondaries.
  3. To scale a group of databases with variable resource consumption.
  4. To offload read-heavy queries from the primary database.

Correct Answer: D

 

Correct Answer

Answer D is correct because Azure SQL read scale-out routes read-only workloads to a readable secondary replica in supported tiers.

Incorrect Answers

Answer A is incorrect because that outcome is more directly associated with PostgreSQL read replica, not Azure SQL read scale-out.

Answer B is incorrect because that outcome is more directly associated with Azure SQL active geo-replication, not Azure SQL read scale-out.

Answer C is incorrect because that outcome is more directly associated with Azure SQL elastic pool scaling, not Azure SQL read scale-out.

 

Question 22

For PostgreSQL read replica, which statement is accurate?

  1. Creates asynchronous replicas for read scaling and supported disaster-recovery scenarios.
  2. Manages geo-replication and listener endpoints for groups of databases with policy-based or manual failover.
  3. Provide SQL Server replica-based high availability or disaster recovery when running SQL Server on IaaS.
  4. Provide built-in point-in-time restore capability within the configured retention window.

Correct Answer: A

 

Correct Answer

Answer A is correct because PostgreSQL read replica creates asynchronous replicas for read scaling and supported disaster-recovery scenarios.

Incorrect Answers

Answer B is incorrect because that description belongs to Azure SQL failover group, whose purpose is to simplify multi-database regional failover and connection redirection.

Answer C is incorrect because that description belongs to SQL Server Always On availability groups on Azure VMs, whose purpose is to retain SQL Server-native HA control for virtual-machine-based deployments.

Answer D is incorrect because that description belongs to Azure SQL automatic backups, whose purpose is to recover a managed SQL database to an earlier point after logical corruption or deletion.

 

Question 23

To recover a managed SQL database to an earlier point after logical corruption or deletion, which Azure design option should be selected?

  1. PostgreSQL read replica
  2. Azure SQL automatic backups
  3. Azure SQL elastic pool scaling
  4. Azure SQL long-term retention (LTR)

Correct Answer: B

 

Correct Answer

Answer B is correct because Azure SQL automatic backups is designed to recover a managed SQL database to an earlier point after logical corruption or deletion. Azure SQL automatic backups provide built-in point-in-time restore capability within the configured retention window.

Incorrect Answers

Answer A is incorrect because PostgreSQL read replica can be useful in Azure architectures, but its primary role is to offload read workloads from a PostgreSQL primary server; it is not the best match for the stated priority.

Answer C is incorrect because Azure SQL elastic pool scaling can be useful in Azure architectures, but its primary role is to scale a group of databases with variable resource consumption; it is not the best match for the stated priority.

Answer D is incorrect because Azure SQL long-term retention (LTR) can be useful in Azure architectures, but its primary role is to meet long-term database backup retention or compliance requirements; it is not the best match for the stated priority.

 

Question 24

Which Azure capability manages geo-replication and listener endpoints for groups of databases with policy-based or manual failover?

  1. Azure SQL failover group
  2. Azure SQL zone redundancy
  3. Azure SQL elastic pool scaling
  4. Azure SQL long-term retention (LTR)

Correct Answer: A

 

Correct Answer

Answer A is correct because Azure SQL failover group matches the described capability and is intended to simplify multi-database regional failover and connection redirection.

Incorrect Answers

Answer B is incorrect because Azure SQL zone redundancy is intended to protect a database from a datacenter or zone failure within one region, which is a different architectural function.

Answer C is incorrect because Azure SQL elastic pool scaling is intended to scale a group of databases with variable resource consumption, which is a different architectural function.

Answer D is incorrect because Azure SQL long-term retention (LTR) is intended to meet long-term database backup retention or compliance requirements, which is a different architectural function.

 

Question 25

An existing Azure SQL elastic pool reaches its aggregate capacity as tenant demand grows. Which statement describes how pool scaling addresses that situation?

  1. Allocates shared performance resources across databases and can be resized as aggregate demand changes.
  2. Manages geo-replication and listener endpoints for groups of databases with policy-based or manual failover.
  3. Provide SQL Server replica-based high availability or disaster recovery when running SQL Server on IaaS.
  4. Maintains a synchronized standby in another Availability Zone in supported regions.

Correct Answer: A

 

Correct Answer

Answer A is correct because Azure SQL elastic pool scaling allocates shared performance resources across databases and can be resized as aggregate demand changes.

Incorrect Answers

Answer B is incorrect because that description belongs to Azure SQL failover group, whose purpose is to simplify multi-database regional failover and connection redirection.

Answer C is incorrect because that description belongs to SQL Server Always On availability groups on Azure VMs, whose purpose is to retain SQL Server-native HA control for virtual-machine-based deployments.

Answer D is incorrect because that description belongs to PostgreSQL Flexible Server zone-redundant high availability, whose purpose is to protect managed PostgreSQL against zone-level failures.

 

Question 26

To offload read workloads from a PostgreSQL primary server, which Azure design option should be selected?

  1. PostgreSQL read replica
  2. Azure SQL automatic backups
  3. SQL Server Always On availability groups on Azure VMs
  4. Azure SQL failover group

Correct Answer: A

 

Correct Answer

Answer A is correct because PostgreSQL read replica creates asynchronous replicas for read scaling and supported disaster-recovery scenarios. It directly meets the requirement to offload read workloads from a PostgreSQL primary server.

Incorrect Answers

Answer B is incorrect because Azure SQL automatic backups is used to recover a managed SQL database to an earlier point after logical corruption or deletion; that does not directly satisfy the requirement in this scenario.

Answer C is incorrect because SQL Server Always On availability groups on Azure VMs is used to retain SQL Server-native HA control for virtual-machine-based deployments; that does not directly satisfy the requirement in this scenario.

Answer D is incorrect because Azure SQL failover group is used to simplify multi-database regional failover and connection redirection; that does not directly satisfy the requirement in this scenario.

 

Question 27

A managed Azure SQL database needs protection against a single-zone failure without depending solely on a different region. Which resilience option addresses this requirement?

  1. PostgreSQL Flexible Server zone-redundant high availability
  2. Azure SQL zone redundancy
  3. Azure SQL automatic backups
  4. Azure SQL read scale-out

Correct Answer: B

 

Correct Answer

Answer B is correct because Azure SQL zone redundancy places replicas across Availability Zones in supported service tiers and regions. It directly meets the requirement to protect a database from a datacenter or zone failure within one region.

Incorrect Answers

Answer A is incorrect because PostgreSQL Flexible Server zone-redundant high availability is used to protect managed PostgreSQL against zone-level failures; that does not directly satisfy the requirement in this scenario.

Answer C is incorrect because Azure SQL automatic backups is used to recover a managed SQL database to an earlier point after logical corruption or deletion; that does not directly satisfy the requirement in this scenario.

Answer D is incorrect because Azure SQL read scale-out is used to offload read-heavy queries from the primary database; that does not directly satisfy the requirement in this scenario.

 

Question 28

An application change corrupts database records, and the team needs to restore a managed SQL database to a point before the change. Which built-in protection supplies the restore history?

  1. Azure SQL elastic pool scaling
  2. PostgreSQL read replica
  3. Azure SQL long-term retention (LTR)
  4. Azure SQL automatic backups

Correct Answer: D

 

Correct Answer

Answer D is correct because Azure SQL automatic backups provide built-in point-in-time restore capability within the configured retention window. It directly meets the requirement to recover a managed SQL database to an earlier point after logical corruption or deletion.

Incorrect Answers

Answer A is incorrect because Azure SQL elastic pool scaling is used to scale a group of databases with variable resource consumption; that does not directly satisfy the requirement in this scenario.

Answer B is incorrect because PostgreSQL read replica is used to offload read workloads from a PostgreSQL primary server; that does not directly satisfy the requirement in this scenario.

Answer C is incorrect because Azure SQL long-term retention (LTR) is used to meet long-term database backup retention or compliance requirements; that does not directly satisfy the requirement in this scenario.

 

Question 29

Which Azure capability routes read-only workloads to a readable secondary replica in supported tiers?

  1. Azure SQL active geo-replication
  2. Azure SQL elastic pool scaling
  3. PostgreSQL read replica
  4. Azure SQL read scale-out

Correct Answer: D

 

Correct Answer

Answer D is correct because Azure SQL read scale-out matches the described capability and is intended to offload read-heavy queries from the primary database.

Incorrect Answers

Answer A is incorrect because Azure SQL active geo-replication is intended to provide database-level geographic redundancy with readable secondaries, which is a different architectural function.

Answer B is incorrect because Azure SQL elastic pool scaling is intended to scale a group of databases with variable resource consumption, which is a different architectural function.

Answer C is incorrect because PostgreSQL read replica is intended to offload read workloads from a PostgreSQL primary server, which is a different architectural function.

 

Question 30

A managed PostgreSQL workload must survive the loss of an availability zone within its region. Which high-availability option should be selected?

  1. Azure SQL zone redundancy
  2. PostgreSQL read replica
  3. PostgreSQL Flexible Server zone-redundant high availability
  4. Azure SQL active geo-replication

Correct Answer: C

 

Correct Answer

Answer C is correct because PostgreSQL Flexible Server zone-redundant high availability maintains a synchronized standby in another Availability Zone in supported regions. It directly meets the requirement to protect managed PostgreSQL against zone-level failures.

Incorrect Answers

Answer A is incorrect because Azure SQL zone redundancy is used to protect a database from a datacenter or zone failure within one region; that does not directly satisfy the requirement in this scenario.

Answer B is incorrect because PostgreSQL read replica is used to offload read workloads from a PostgreSQL primary server; that does not directly satisfy the requirement in this scenario.

Answer D is incorrect because Azure SQL active geo-replication is used to provide database-level geographic redundancy with readable secondaries; that does not directly satisfy the requirement in this scenario.

 

img