AZ-305 Practice Test 45 — 15 Questions

Question 1

A company runs an Azure SQL Database with active geo-replication configured to a secondary region. The primary region experiences a complete outage. The company needs to promote the secondary database to become the new primary with minimal data loss. Which action should they take?

Accepted Answer

Forced failover. Forced failover is the correct action because it immediately promotes the secondary database to primary without waiting for synchronization, which is necessary during a complete primary region outage. This option minimizes data loss by accepting any unsynchronized data at the secondary, prioritizing availability over consistency. In contrast, planned failover requires synchronous data transfer and fails if the primary is unreachable.

Answer

Planned failover

Answer

Enable geo-replication

Answer

Failover

Question 2

A company runs critical Azure virtual machines (VMs) in the West US region. They need a disaster recovery solution that replicates VMs to East US. The recovery point objective (RPO) must be 15 minutes and the recovery time objective (RTO) must be 2 hours. The VMs use managed disks and the application requires consistent state across multiple VMs. They want to test failover without impacting production. Which Azure service should they use?

Accepted Answer

Azure Site Recovery with app-consistent replication. Azure Site Recovery with app-consistent replication (Option C) is correct because it meets the RPO of 15 minutes and RTO of 2 hours while ensuring consistent state across multiple VMs. App-consistent replication uses Volume Shadow Copy Service (VSS) to quiesce applications and flush memory writes to disk, guaranteeing that the recovered VMs are in a crash-consistent state at the application level. This is essential for multi-VM applications that require transaction consistency, and Azure Site Recovery supports planned and unplanned failover testing without impacting production via isolated test failover networks.

Answer

Azure Backup with backup policies set to 15-minute frequency

Answer

Azure Site Recovery with crash-consistent replication

Answer

Azure Backup with application-consistent snapshot

Question 3

A company runs critical Azure VMs. They want to protect against accidental deletion or corruption of data by implementing a retention policy for Azure Backup. They need to keep daily backups for 30 days, weekly backups for 12 weeks, and monthly backups for 12 months. Which Azure Backup feature should they configure?

Accepted Answer

Backup policy with long-term retention. A backup policy with long-term retention (LTR) in Azure Backup allows you to define granular retention rules for daily, weekly, monthly, and yearly backup points. This directly meets the requirement to keep daily backups for 30 days, weekly for 12 weeks, and monthly for 12 months by configuring the retention duration for each frequency in the backup policy.

Answer

Immutable vault

Answer

Backup tiering

Answer

Soft delete

Question 4

A company wants to back up on-premises SQL Server databases to Azure and be able to restore them to an on-premises server in case of a disaster. The backup must be encrypted and retained for 7 years for compliance. Which Azure service should they use?

Accepted Answer

Azure Backup with the MARS agent.. Azure Backup with the MARS agent is the correct choice because it is specifically designed to back up on-premises SQL Server databases directly to Azure, supports encryption at rest using a passphrase, and allows long-term retention (up to 99 years) to meet the 7-year compliance requirement. The MARS agent performs file- and application-consistent backups and can restore data to an on-premises server, fulfilling the disaster recovery scenario.

Answer

Azure Site Recovery.

Answer

Azure Database Migration Service.

Answer

Azure Storage with incremental snapshots.

Question 5

A company deploys a critical multi-tier application on Azure VMs. The application includes a database tier that must be recovered to the same point in time as the application tier after a disaster. They use Azure Site Recovery (ASR) for disaster recovery to a secondary region. They also need to run a custom script after failover to update connection strings. Which ASR feature should they use?

Accepted Answer

Recovery plans with pre-actions and post-actions. Recovery plans in Azure Site Recovery allow you to define pre-actions and post-actions, which can run custom scripts (e.g., PowerShell) after failover to update connection strings. This ensures the application tier can connect to the recovered database tier, meeting the requirement for a custom script execution after failover. The other options do not provide the ability to run custom scripts as part of the failover sequence.

Answer

Replication policies with application-consistent snapshots

Answer

Multi-VM consistency groups

Answer

Azure Backup with cross-region restore

Question 6

A startup is building a new mobile app backend. They need a fully managed relational database service with built-in high availability, automatic backups, and built-in intelligence to optimize performance. They want to minimize administrative overhead for tasks like patching and scaling. Which Azure service should they use?

Accepted Answer

Azure SQL Database. Azure SQL Database is a fully managed Platform-as-a-Service (PaaS) relational database that includes built-in high availability (99.99% SLA), automatic backups with point-in-time restore, and built-in intelligence features like automatic tuning, adaptive query processing, and intelligent insights. This minimizes administrative overhead for patching, scaling, and performance optimization, making it ideal for a startup that wants to focus on app development rather than database management.

Answer

SQL Server on Azure Virtual Machines

Answer

Azure Database for MySQL

Answer

Azure Cosmos DB

Question 7

A company wants to store raw data from IoT devices, social media feeds, and transactional databases for analytics. They need a storage solution that supports a hierarchical namespace for organizing data into directories and allows fine-grained access control at the directory and file level. They also need to query the data using Azure Synapse Analytics in-place. Which Azure storage solution should they use?

Accepted Answer

B. Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it provides a hierarchical namespace that organizes data into directories and subdirectories, supports POSIX-like fine-grained access control at the directory and file level via ACLs, and can be queried in-place by Azure Synapse Analytics using its built-in serverless SQL pool or dedicated SQL pool. This combination of hierarchical namespace, granular security, and direct analytics integration makes it ideal for the described raw data storage and analytics scenario.

Answer

A

Answer

C

Answer

D

Question 8

A global e-commerce company uses Azure Cosmos DB to store its product catalog. The catalog is read-heavy, with users worldwide expecting consistent reads with a 99th percentile latency under 10 ms. Writes to the catalog are performed by a central admin team in one region. The company needs to minimize write latency and cost while ensuring that users always see the same data within a single session. Which Cosmos DB configuration should the company choose?

Accepted Answer

Single-master write region with Session consistency and multiple read regions. Option C is correct because Session consistency provides the required 'read your own writes' guarantee within a single session, which ensures users always see the same data during their session without the latency and cost penalties of Strong consistency. Single-master writes minimize write latency by directing all writes to one region (the central admin team's region), while multiple read regions allow global users to read from the nearest region with sub-10 ms latency. This configuration balances cost, performance, and consistency needs for a read-heavy catalog with centralized writes.

Answer

Single-master write region with Strong consistency and multiple read regions

Answer

Multi-master write with Eventual consistency and all regions enabled for writes

Answer

Multi-master write with Strong consistency and two regions

Question 9

A company runs a large-scale write-intensive application that requires a horizontally scalable relational database. They need to distribute data across multiple nodes to handle high write throughput while supporting SQL queries, including joins and transactions. The solution must be fully managed and provide elastic scaling. Which Azure database service should they choose?

Accepted Answer

Azure Database for PostgreSQL Hyperscale (Citus). Azure Database for PostgreSQL Hyperscale (Citus) is the correct choice because it provides horizontal scaling (sharding) across multiple worker nodes using the Citus extension, which distributes data and parallelizes SQL queries. It supports full SQL, including joins and transactions, while offering elastic scaling for write-intensive workloads. This makes it ideal for large-scale relational databases that need high write throughput and horizontal scalability.

Answer

Azure SQL Database Hyperscale

Answer

Azure Cosmos DB

Answer

Azure SQL Managed Instance

Question 10

A company is building a global real-time collaboration platform. The application data is stored as JSON documents and needs to be available for low-latency reads and writes from multiple geographic regions. The application must support multi-region writes so that users can update data from any region with automatic conflict resolution. The company wants a fully managed database service with a guaranteed SLA for availability and throughput. Which Azure data service should they choose?

Accepted Answer

Azure Cosmos DB with SQL API and multiple write regions. Azure Cosmos DB with SQL API and multiple write regions is the correct choice because it is a fully managed, globally distributed NoSQL database that natively supports multi-region writes with automatic conflict resolution. It provides low-latency reads and writes from any region, a guaranteed SLA for availability (99.999% for multi-region writes) and throughput, and is optimized for JSON document storage, making it ideal for a real-time collaboration platform.

Answer

Azure SQL Database with active geo-replication

Answer

Azure Table Storage

Answer

Azure Cache for Redis

Question 11

A company is migrating a MongoDB-compatible application to Azure. The application requires low-latency reads and writes globally. It needs to support multi-region writes so that updates can be made from any region with automatic conflict resolution. The data is JSON documents that can vary in schema. The company wants a fully managed database service with native support for MongoDB APIs. Which Azure data service should they choose?

Accepted Answer

Azure Cosmos DB with the API for MongoDB. Azure Cosmos DB with the API for MongoDB is the correct choice because it provides a fully managed, globally distributed database service that natively supports the MongoDB wire protocol. It offers multi-region writes with automatic conflict resolution using last-writer-wins (LWW) or custom conflict resolution policies, ensuring low-latency reads and writes globally. Its schema-agnostic nature handles JSON documents with varying schemas, meeting all stated requirements.

Answer

Azure SQL Database

Answer

Azure Database for MongoDB

Answer

Azure Cache for Redis

Question 12

A company needs a fully managed NoSQL database for a JSON document-oriented application that requires low latency (single-digit milliseconds) for reads and writes at any scale. The application will run globally and needs multi-region writes with automatic failover. Which Azure data store should they use?

Accepted Answer

Azure Cosmos DB. Azure Cosmos DB is the correct choice because it is a fully managed NoSQL database that natively supports JSON documents, offers single-digit millisecond latency for reads and writes at any scale, and provides multi-region writes with automatic failover through its multi-master replication capability. Its global distribution model allows you to configure multiple write regions, ensuring high availability and low latency worldwide.

Answer

Azure Table Storage

Answer

Azure SQL Database

Answer

Azure Cache for Redis

Question 13

A company runs a high-performance computing (HPC) workload that requires low-latency access to large files (hundreds of GB) from thousands of Azure VMs concurrently. The files must be accessible via the NFS protocol and the solution must be a fully managed, POSIX-compliant file system that can scale throughput linearly with capacity. Which Azure storage solution should they choose?

Accepted Answer

Azure NetApp Files. Azure NetApp Files is the correct choice because it provides a fully managed, POSIX-compliant NFS file system that can scale throughput linearly with capacity. It is designed for HPC workloads requiring low-latency access to large files from thousands of concurrent VMs, offering sub-millisecond latency and high throughput that increases as you add capacity.

Answer

Azure Files (premium tier)

Answer

Azure Blob Storage with NFS 3.0 support

Answer

Azure HPC Cache

Question 14

A company runs a custom analytics application that reads data using the NFS 3.0 protocol. The data consists of large files organized in a directory structure. The application also requires POSIX-like access control lists (ACLs) for fine-grained permissions. The solution must be fully managed and support high throughput for parallel reads. Which Azure data service should they use?

Accepted Answer

Azure Data Lake Storage Gen2. Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it combines a hierarchical namespace with POSIX-like ACLs and supports the NFS 3.0 protocol for high-throughput parallel reads. It is fully managed and designed for big data analytics workloads that require fine-grained permissions and directory structure management.

Answer

Azure Blob Storage

Answer

Azure Files

Answer

Azure NetApp Files

Question 15

A data platform must support analytical queries over petabytes of files in a data lake, while preserving hierarchical namespaces and fine-grained ACLs. Which storage service should you design around?

Accepted Answer

Azure Data Lake Storage Gen2.. Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it combines a hierarchical namespace with POSIX-like ACLs, enabling fine-grained access control at the file and directory level while supporting petabyte-scale analytical workloads. It is built on Azure Blob Storage, providing high-throughput and parallel processing for big data analytics engines like Azure Synapse, Spark, and Hadoop.

Answer

Azure Files premium shares.

Answer

Azure Table Storage.

Answer

Azure Queue Storage.