Free AZ-305 Exam Braindumps
Designing Microsoft Azure Infrastructure Solutions Questions 50–54 (page: 34)

Updated On: 16-Nov-2026
View Related Case Study

You are designing an app that will use Azure Cosmos DB to collate sales from multiple countries.
You need to recommend an API for the app. The solution must meet the following requirements:
-Support SQL queries.
-Support geo-replication.
-Store and access data relationally.
Which API should you recommend?

  1. Apache Cassandra
  2. PostgreSQL
  3. MongoDB
  4. NoSQL

Answer(s): B

Explanation:

If you’re looking for a managed open source relational database with high performance and geo-replication, Azure Cosmos DB for PostgreSQL is the recommended choice.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/choose-api



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You are designing a data analytics solution that will use Azure Synapse and Azure Data Lake Storage Gen2.
You need to recommend Azure Synapse pools to meet the following requirements:
-Ingest data from Data Lake Storage into hash-distributed tables.
-Implement, query, and update data in Delta Lake.
What should you recommend for each requirement? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: A dedicated SQL pool
Ingest data from Data Lake Storage into hash distributed tables.
Guidance for designing distributed tables using dedicated SQL pool in Azure Synapse Analytics
You can design hash-distributed and round-robin distributed tables in dedicated SQL pools.
Box 2: A serverless SQL pool
Implement query, and update data in Delta Lake.
You can query Delta Lake files using serverless SQL pool in Azure Synapse Analytics
You can write a query using serverless Synapse SQL pool to read Delta Lake files. Delta Lake is an open-source storage layer that brings ACID (atomicity, consistency, isolation, and durability) transactions to Apache Spark and big data workloads.
The serverless SQL pool in Synapse workspace enables you to read the data stored in Delta Lake format, and serve it to reporting tools. A serverless SQL pool can read Delta Lake files that are created using Apache Spark, Azure Databricks, or any other producer of the Delta Lake format.


Reference:

https://learn.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-distr ibute https://learn.microsoft.com/en-us/azure/synapse-analytics/sql/query-delta-lake-format



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription.
You plan to deploy a high-throughput transactional workload that will use PostgreSQL.
You need to recommend a managed solution for storing relational data. The solution must meet the following requirements:
-Support the horizontal scaling of transactional writes by using row-based sharding.
-Minimize administrative effort.
What should you include in the recommendation? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Azure Database for PostgreSQL Flexible Server
For horizontal scaling of transactional writes in Azure PostgreSQL using row-based sharding, you should utilize Azure Database for PostgreSQL Flexible Server with Elastic Clusters. This feature leverages the Citus extension for PostgreSQL, enabling you to shard your data across multiple nodes and manage them as a single, distributed database.
Flexible Server:
It offers a flexible and powerful managed PostgreSQL service.
Elastic Clusters:
This feature, powered by Citus, allows horizontal scaling of your PostgreSQL database.
Row-based Sharding:
With row-based sharding, you define a distribution key, and the Citus extension automatically distributes rows based on this key across the nodes in the cluster.
Citus Extension:
Citus is an open-source extension for PostgreSQL that enables distributed database capabilities, including sharding.
Box 2: Distributed tables
Azure Database for PostgreSQL Flexible Server uses distributed tables for scaling through the use of an Elastic cluster, powered by the Citus extension. This allows for scaling out by adding more nodes to the cluster and distributing data across them, rather than just increasing the compute power of a single node.
Distributed Tables:
With an elastic cluster, you can define distributed tables where data is spread across multiple nodes.
Scalability:
By adding more nodes to the cluster, you can scale the database horizontally, increasing both capacity and performance.
Transparent Scaling:
The scaling process is managed transparently by the Citus extension, meaning the application doesn't need to be aware of the distributed nature of the database.
Vertical vs. Horizontal Scaling:
While vertical scaling (increasing compute and memory on a single node) is still possible, the elastic cluster allows for true horizontal scaling, distributing the workload across multiple nodes.
Incorrect:
* Logical replication
* Near-zero downtime scaling


Reference:

https://techcommunity.microsoft.com/blog/adforpostgresql/postgres-horizontal-scaling-with-elastic-clusters-on-azure-database-for-postgres/4303508



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an on-premises database that you plan to migrate to Azure.
You need to design the database architecture to meet the following requirements:
-Support scaling up and down.
-Support geo-redundant backups.
-Support a database of up to 75 TB.
-Be optimized for online transaction processing (OLTP).
What should you include in the design? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Azure SQL Database
Azure SQL Database:
Database size always depends on the underlying service tiers (e.g. Basic, Business Critical, Hyperscale). It supports databases of up to 100 TB with Hyperscale service tier model.
Active geo-replication is a feature that lets you to create a continuously synchronized readable secondary database for a primary database. The readable secondary database may be in the same Azure region as the primary, or, more commonly, in a different region. This kind of readable secondary databases are also known as geo-secondaries, or geo-replicas.
Azure SQL Database and SQL Managed Instance enable you to dynamically add more resources to your database with minimal downtime.
Box 2: Hyperscale
Incorrect Answers:
-SQL Server on Azure VM: geo-replication not supported.
-Azure Synapse Analytics is not optimized for online transaction processing (OLTP).
-Azure SQL Managed Instance max database size is up to currently available instance size (depending on the number of vCores).
Max instance storage size (reserved) - 2 TB for 4 vCores
- 8 TB for 8 vCores
- 16 TB for other sizes


Reference:

https://docs.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-overview https://medium.com/awesome-azure/azure-difference-between-azure-sql-database-and-sql-server-on-vm-com parison-azure-sql-vs-sql-server-vm-cf02578a1188



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription that contains multiple Azure SQL databases and multiple instances of SQL Server on Azure Virtual Machines.
You need to scan all the Azure SQL resources in the subscription by using Microsoft Purview. The solution must minimize administrative effort and maximize security.
What should you use? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




To scan the Azure SQL databases, use - Azure integration runtime
Azure SQL databases are a fully managed service within Azure. The Azure integration runtime is natively integrated with Azure and offers the easiest and most secure way to scan Azure SQL databases. It handles the data movement and scanning within the Azure environment without the need for extra configuration or on-premises components.
To scan the SQL Server on Azure Virtual Machines instances, use - Self-hosted integration runtime SQL Server on Azure Virtual Machines (VMs) requires access through the underlying infrastructure, which is not fully managed like Azure SQL Database. The self-hosted integration runtime is deployed on the virtual machine or a network that can access the VM, allowing it to scan SQL Server instances running there. It is necessary because these VMs might not be accessible directly through Azure services, and the self-hosted integration runtime can bridge that gap.



Viewing page 34 of 78
Viewing questions 166 - 170 out of 382 questions


Post your Comments and Discuss Microsoft AZ-305 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!