AZ-305 Design data storage solutions Practice Test 6 — 15 Questions

Question 1

Refer to the exhibit. A custom Azure RBAC role is defined as shown. A user assigned this role is unable to delete blobs in a container. What is the most likely reason?

Accepted Answer

The role does not include delete permission on blobs. The custom RBAC role definition shown in the exhibit includes 'Microsoft.Storage/storageAccounts/blobServices/containers/blobs/delete' under the 'Actions' section, but this permission is a control plane action, not a data plane action. To delete blobs, the role must include the corresponding data action 'Microsoft.Storage/storageAccounts/blobServices/containers/blobs/delete/action' under 'DataActions'. Without it, the user lacks the necessary data plane permission to perform blob deletion, even though the control plane permission is present.

Answer

The role is scoped to the storage account but not to the container

Answer

The role does not include read permission on blobs

Answer

The role does not include any dataActions

Question 2

Refer to the exhibit. An organization deploys this ARM template to create a storage account. They need to ensure that data is replicated synchronously across two Azure regions. Does this template meet the requirement?

Accepted Answer

No, GRS provides asynchronous replication. The template uses GRS (Geo-Redundant Storage), which replicates data asynchronously from the primary region to the secondary region. Because the replication is asynchronous, there is a potential for data loss if a regional disaster occurs before the secondary region is fully updated. The requirement specifies synchronous replication across two Azure regions, which is only provided by Azure Storage’s geo-zone-redundant storage (GZRS) with read-access (RA-GZRS) or by using Azure Files with synchronous replication via Azure File Sync or a third-party solution. Therefore, GRS does not meet the synchronous requirement.

Answer

No, the template uses RA-GRS

Answer

Yes, GRS provides synchronous replication

Answer

No, the template uses LRS

Question 3

Refer to the exhibit. A KQL query is run against Azure Storage logs. The result shows a high number of 404 errors for 'GetBlob' operations. What is the most likely cause?

Accepted Answer

The blobs being requested do not exist. A 404 (Not Found) error for 'GetBlob' operations in Azure Storage logs specifically indicates that the requested blob resource does not exist at the specified URI. This is distinct from authorization failures (which return 403) or throttling (which returns 503). The high number of 404 errors suggests the client is attempting to retrieve blobs that have been deleted, never created, or are referenced with an incorrect path.

Answer

The client does not have permission to access the blobs

Answer

The storage account is throttling requests

Answer

The client is using an incorrect authentication method

Question 4

You are designing a storage solution for a globally distributed application that requires low-latency read access from multiple regions. Which Azure storage solution should you recommend?

Accepted Answer

Azure Cosmos DB with multi-region writes and multiple read regions. Azure Cosmos DB with multi-region writes and multiple read regions is the correct choice because it provides turnkey global distribution with single-digit-millisecond latency for reads and writes from any Azure region. This solution directly addresses the requirement for low-latency read access from multiple regions, as Cosmos DB automatically replicates data to all configured regions and offers multiple consistency models to balance performance and data freshness.

Answer

Azure Blob Storage with read-access geo-redundant storage (RA-GRS)

Answer

Azure SQL Database with active geo-replication

Answer

Azure Files with Azure File Sync

Question 5

Your company runs a critical database on Azure SQL Managed Instance. You need to ensure zero data loss and automatic failover to a secondary region in the event of a regional outage. What should you configure?

Accepted Answer

Auto-failover groups for the Azure SQL Managed Instance. Auto-failover groups for Azure SQL Managed Instance (Option A) provide automatic failover to a secondary region, which directly meets the automatic failover requirement. While zero data loss is not guaranteed due to asynchronous replication, this is the only option that includes automatic failover across regions. Option D uses a manual failover policy, which does not provide automatic failover. Thus, Option A is the best match.

Answer

A single Azure SQL Managed Instance with zone-redundant configuration

Answer

Active geo-replication for the database

Answer

Failover groups with manual failover policy and automatic data synchronization

Question 6

Your company uses Azure SQL Database and needs to archive data older than 7 years for compliance. The archived data must be stored in the most cost-effective manner, must be immutable, and must be deleted exactly after 10 years. What should you use?

Accepted Answer

Azure Blob Storage with immutable storage and time-based retention policy. Azure Blob Storage with immutable storage and a time-based retention policy ensures that archived data cannot be modified or deleted until the specified retention period expires. This meets the compliance requirements for immutability and a 10-year deletion timeline, while blob storage tiers (e.g., cool or archive) can be used for cost-effective long-term storage.

Answer

Azure Archive Storage with lifecycle management to delete after 10 years

Answer

Azure SQL Database restore to a point in time with a retention period of 10 years

Answer

Azure SQL Database long-term retention (LTR) backups

Question 7

You need to store billions of small JSON files (average 50 KB) that are accessed infrequently but must be available within seconds when requested. Which Azure storage solution is most cost-effective?

Accepted Answer

Azure Blob Storage Cool tier. Azure Blob Storage Cool tier is the most cost-effective solution for storing billions of small JSON files (average 50 KB) that are infrequently accessed but require low-latency retrieval within seconds. The Cool tier offers low storage costs for data accessed less than once per month, while still providing sub-second access latency for individual blobs via HTTPS REST API, matching the 'available within seconds' requirement without the higher costs of Hot or premium tiers.

Answer

Azure SQL Database with a table storing JSON

Answer

Azure Files with SMB shares

Answer

Azure Cosmos DB with a container for each file

Question 8

Your company is migrating on-premises Oracle databases to Azure. The new solution must support a minimum of 99.99% availability SLA and allow for schema changes with minimal downtime. What should you recommend?

Accepted Answer

Azure SQL Database Business Critical tier with zone redundancy. Azure SQL Database Business Critical tier with zone redundancy provides a 99.995% SLA, exceeding the 99.99% requirement, and supports online schema changes with minimal downtime via features like online index operations and schema modification with minimal blocking. Zone redundancy replicates data across three Azure Availability Zones within a region, ensuring high availability and automatic failover without data loss.

Answer

Azure SQL Managed Instance Business Critical tier

Answer

Azure Cosmos DB for PostgreSQL

Answer

Azure Virtual Machines running Oracle Database with Availability Zones

Question 9

You are designing a data storage solution for a healthcare application that stores patient records. The solution must meet compliance requirements that data in the US must be stored in US regions, and data in the EU must be stored in EU regions. Additionally, the solution must support global queries with low latency. What should you use?

Accepted Answer

Azure Cosmos DB with multi-region writes and conflict resolution policy based on region. Azure Cosmos DB with multi-region writes is the correct choice because it provides active-active replication across multiple regions, enabling low-latency global queries by allowing writes and reads from any region. The conflict resolution policy based on region ensures that data sovereignty requirements are met by prioritizing writes from the region where the data originates (e.g., US writes win in US regions, EU writes win in EU regions), which aligns with the compliance requirement that data must stay within its respective geographic boundary.

Answer

Azure Blob Storage with RA-GRS storage accounts in each region

Answer

Azure SQL Database with active geo-replication and a failover policy

Answer

Azure SQL Managed Instance with failover groups

Question 10

You have an Azure SQL Database that stores sales data. You need to ensure that the database can recover to any point in time within the last 35 days. What should you configure?

Accepted Answer

Configure the point-in-time restore (PITR) retention period to 35 days. Point-in-time restore (PITR) for Azure SQL Database allows you to restore a database to any point within the configured retention period. The default retention is 7 days, but you can increase it up to 35 days. By setting the PITR retention period to 35 days, you meet the requirement to recover to any point in time within the last 35 days.

Answer

Configure long-term retention (LTR) backups with a retention of 35 days

Answer

Create a secondary database in the same region

Answer

Enable geo-replication with a readable secondary

Question 11

Your company uses Azure Cosmos DB for a globally distributed application. You need to ensure that writes in one region are not lost if that region fails. Which consistency level should you use to guarantee that writes are durable?

Accepted Answer

Strong consistency. Strong consistency ensures that write operations are synchronously replicated to a quorum of replicas across all configured regions before acknowledging the write. This guarantees that if a region fails, all acknowledged writes are durable and available in other regions, preventing data loss. In contrast, bounded staleness, eventual, and consistent prefix consistency allow some lag in replication, which could result in loss of recently acknowledged writes if the primary region fails before those writes are fully replicated.

Answer

Eventual consistency

Answer

Bounded staleness consistency

Answer

Consistent prefix consistency

Question 12

You are designing a data lake solution using Azure Data Lake Storage Gen2. The solution must support file-level security for sensitive data and must integrate with Azure Purview for data cataloging. What should you use for file-level security?

Accepted Answer

Access control lists (ACLs). Access control lists (ACLs) are the correct choice for file-level security in Azure Data Lake Storage Gen2 because they provide POSIX-compliant permissions that can be set on individual files and directories. This granularity allows you to enforce security for sensitive data at the file level, which is required by the scenario. ACLs also integrate seamlessly with Azure Purview for data cataloging, as Purview can scan and classify data while respecting the underlying ACL-based security boundaries.

Answer

Azure Key Vault with customer-managed keys

Answer

Azure Defender for Storage

Answer

Azure RBAC roles

Question 13

Which TWO of the following are benefits of using Azure Cosmos DB for a globally distributed application?

Accepted Answer

Multiple well-defined consistency levels. Azure Cosmos DB offers multiple well-defined consistency levels (Strong, Bounded Staleness, Session, Consistent Prefix, Eventual) that allow developers to balance data consistency, availability, and latency according to application requirements. This flexibility is a key benefit for globally distributed applications because different operations may tolerate different levels of staleness while still meeting SLAs.

Answer

Full support for SQL Server features like stored procedures

Answer

Automatic failover to a secondary region without manual intervention

Answer

Support for only the SQL API

Question 14

Which THREE of the following are considerations when designing a storage solution for a high-availability application on Azure?

Accepted Answer

Recovery Point Objective (RPO) and Recovery Time Objective (RTO). RPO and RTO are fundamental design considerations for any high-availability application. RPO defines the maximum acceptable data loss (measured in time), which directly influences the choice of backup frequency and replication type (e.g., synchronous vs. asynchronous). RTO defines the maximum acceptable downtime, which dictates the failover mechanism and infrastructure redundancy (e.g., active-passive vs. active-active). Both metrics must be explicitly defined before selecting a storage redundancy tier or disaster recovery strategy.

Answer

Data encryption at rest using Azure Storage Service Encryption

Answer

Data striping with RAID 0 for performance

Question 15

Which TWO of the following Azure storage services support hosting static websites?

Accepted Answer

Azure Storage Account (general-purpose v2). Azure Storage Account (general-purpose v2) supports hosting static websites by enabling the 'Static website' feature, which configures a container named '$web' to serve static content (HTML, CSS, JS) directly via a public endpoint. This feature is built into the storage account's blob service and provides automatic routing for index and error documents, making it a cost-effective solution for static site hosting.

Answer

Azure Cosmos DB

Answer

Azure NetApp Files

Answer

Azure Files