Describe an analytics workload on Azure →mediumMultiple ChoiceObjective-mapped

DP-900 Describe an analytics workload on Azure Practice Question

Exhibit

{
  "type": "Microsoft.Synapse/workspaces/sqlDatabases",
  "apiVersion": "2021-06-01",
  "properties": {
    "collation": "SQL_Latin1_General_CP1_CI_AS",
    "maxSizeBytes": 268435456000,
    "storageAccountType": "GRS"
  }
}

Refer to the exhibit. You are reviewing an ARM template that deploys a SQL database in Azure Synapse. The template sets the storageAccountType to GRS. What is a valid concern regarding cost and performance?

⚠ Common exam trap

It's easy for candidates to assume GRS only affects disaster recovery and ignore its impact on ongoing storage costs and read latency, leading them to dismiss cost and performance as valid concerns.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

GRS will increase storage costs and may cause higher latency

Geo-redundant storage (GRS) replicates your data to a secondary region, which increases storage costs because you are paying for both the primary and secondary copies. Additionally, when using GRS with Azure Synapse SQL, read requests may experience higher latency if they are directed to the secondary region, especially during a failover scenario or when using read-access geo-redundant storage (RA-GRS). This makes cost and performance valid concerns when choosing GRS over locally redundant storage (LRS).

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
GRS will increase storage costs and may cause higher latency
Why this is correct
Geo-redundant storage (GRS) replicates your data to a paired secondary region, meaning you are billed for two copies of the database, which increases storage costs. Write latency may also increase because each transaction must be committed to the primary region and, depending on transaction durability settings, may require acknowledgment from the replication process, adding network overhead. This is a common trade-off for higher durability and disaster recovery capability.
✗
The collation setting is not compatible with Azure Synapse
Why it's wrong here
SQL_Latin1_General_CP1_CI_AS is a standard Windows SQL Server collation that is fully supported by Azure Synapse Analytics, including both dedicated SQL pools and serverless SQL endpoints. Synapse supports a wide range of collations, and this collation is in fact the default for many Azure SQL resources. Therefore, the collation setting is not a barrier to using Synapse; any incompatibility would be due to a different aspect of the template, such as connection policy or storage account configuration.
✗
The database cannot be part of a failover group
Why it's wrong here
Auto-failover groups in Azure SQL Database are defined at the logical server level and allow a set of user databases to fail over as a unit to a secondary server in another region. The ability to create a failover group depends solely on the servers being paired and having the appropriate permissions, not on the storage redundancy option chosen for the individual database. Because GRS is a valid storage redundancy setting, there is no restriction preventing the database from being included in a failover group.
✗
The database will not support Transparent Data Encryption
Why it's wrong here
Transparent Data Encryption (TDE) performs real-time encryption and decryption of database files, backups, and transaction logs at the page level, independently of how the underlying storage is replicated. Whether a database uses locally redundant storage (LRS), geo-redundant storage (GRS), or read-access geo-redundant storage (RA-GRS), TDE can be enabled without any change to the storage redundancy setting. Encryption keys are managed through Azure Key Vault or the service-managed key, and this does not affect or get affected by geographic replication.

Go deeper

DP-900 Describe an analytics workload on Azure Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question