Select Two (Multi-Select) Questions

Auto-failover group with a secondary in the same region.

Why wrong: Failover groups use asynchronous geo-replication, so RPO > 0.

General Purpose service tier with zone redundancy enabled.

Why wrong: General Purpose uses asynchronous replication and does not guarantee zero data loss.

Active geo-replication to a secondary in a different region.

Why wrong: Geo-replication is asynchronous, so data loss may occur (RPO > 0).

Reduce read latency for globally distributed users.

Why wrong: Not related.

Automatic failover to a paired region.

Why wrong: Zone redundancy is within a region.

Protection against a regional disaster.

Why wrong: Zone redundancy does not protect across regions.

Number of deadlocks per second.

Why wrong: Incorrect. Number of deadlocks per second measures concurrency issues, not resource usage like CPU or I/O.

Used storage space in GB.

Why wrong: Incorrect. Used storage space in GB is a capacity metric, not a performance metric for identifying CPU or I/O bottlenecks.

Number of active sessions.

Why wrong: Incorrect. Number of active sessions indicates concurrency, not resource utilization; it does not directly pinpoint CPU or I/O bottlenecks.

Configure the column master key to be stored in Azure Key Vault.

Why wrong: The column master key must be stored in the enclave, not in Azure Key Vault.

Enable the enclave attestation policy on the managed instance.

Why wrong: The attestation policy is configured in Azure Attestation, not on the instance itself.

Enable Virtualization-Based Security (VBS) enclave type.

Why wrong: VBS enclaves are not supported for SQL Managed Instance; Intel SGX is required.

Enable SQL Server authentication only.

Why wrong: SQL Server authentication is separate and does not enable Entra ID authentication.

Assign the SQL Server Contributor role to the Entra ID users.

Why wrong: This role is for managing the server, not for database authentication.

Enable Azure AD integration on the SQL server.

Why wrong: Integration is automatically enabled when you set an admin; no separate step.

Geo-restore

Why wrong: Incorrect: Geo-restore is a recovery method, not a continuous DR option.

Zone-redundant configuration

Why wrong: Incorrect: Zone-redundant provides HA within a region, not cross-region.

Auto-failover groups

Why wrong: Incorrect: This is synonymous with failover groups, but not a separate option.

Requirement for elastic pool scalability.

Why wrong: Both support elastic pools (single database) or instance pools (Managed Instance).

Need for automated backups with point-in-time restore.

Why wrong: Both support this.

Configure resource governor to limit CPU usage.

Why wrong: Resource governor is not supported in Hyperscale.

Increase the service tier to Business Critical.

Why wrong: Hyperscale is already the highest tier for scalability; changing is not an optimization.

Azure Automation account

Why wrong: Azure Automation is not required for elastic jobs.

SQL Server Agent

Why wrong: SQL Server Agent is for on-premises or IaaS, not elastic jobs.

Rebuild the clustered index to reduce fragmentation.

Why wrong: Fragmentation is not the primary issue; a scan is due to missing indexes.

Force a different query plan using Query Store hints.

Why wrong: Forcing a plan without analysis can cause performance regression.

Increase the DTU service tier of the database.

Why wrong: DTU model is not applicable to vCore-based Azure SQL Database.

Set database compatibility level to 150

Why wrong: Compatibility level affects features, not direct optimization.

Increase the maximum storage size

Why wrong: More storage does not improve query speed.

Enable Transparent Data Encryption (TDE)

Why wrong: TDE encrypts data, does not improve query performance.

Only vCore supports Azure Hybrid Benefit.

Why wrong: Both support Azure Hybrid Benefit.

Only DTU supports elastic pools.

Why wrong: Both support elastic pools.

Database-level maintenance schedule

Why wrong: Maintenance window is set at the instance level, not per database.

Maximum number of concurrent databases

Why wrong: This is not a configurable parameter in maintenance window settings.

Failover group listener.

Why wrong: The listener is automatically provisioned; not a separate configuration step.

An elastic pool.

Why wrong: Elastic pools are optional; databases can be standalone.

Dynamic Management Views (DMVs)

Why wrong: DMVs show current state, not historical trends.

Intelligent Insights

Why wrong: Intelligent Insights provides summaries, not detailed query history.

Extended Events

Why wrong: Extended Events are for real-time tracing, not historical analysis.

Geo-redundant backup storage

Why wrong: Backups are not used during failover; they are for point-in-time restore.

Azure Traffic Manager with priority routing

Why wrong: Failover group listener already handles routing.

Initiate a forced failover to ensure the fastest switchover.

Why wrong: Forced failover may cause data loss; planned failover is preferred for maintenance.

Manually seed the new secondary database after failover.

Why wrong: Seeding happens automatically when geo-replication is established.

Active geo-replication

Why wrong: For cross-region, not within region.

Always On availability groups

Why wrong: Internal implementation, not a configurable feature.

Auto-failover groups

Why wrong: For cross-region failover.

It requires a failover group to be configured.

Why wrong: Zone-redundant does not require a failover group.

It is only available in the Business Critical service tier.

Why wrong: Also available in General Purpose tier.

It incurs additional cost compared to non-zone-redundant configurations.

Why wrong: General Purpose zone-redundant has no additional cost; Business Critical does.

Active geo-replication

Why wrong: Active geo-replication is a separate feature; failover groups use a different replication mechanism.

An availability group listener

Why wrong: Listener is automatically created; not a separate component to configure.