Home › Azure AZ-305 › cloudcomputing › az305datastorage › Which Azure SQL Database feature should an archi…
Which Azure SQL Database feature should an architect recommend to scale a transactional database across many physical partitions while keeping a SQL programming model?
ADisabling indexes to save space
BManual data copies between separate DB servers
CAzure DNS
DAzure SQL Database elastic pools + sharding (or Hyperscale tier for vertical scaling) — plus the elastic database client library where horizontal sharding is needed
Answer & Solution
Correct answer: D. Azure SQL Database elastic pools + sharding (or Hyperscale tier for vertical scaling) — plus the elastic database client library where horizontal sharding is needed
Elastic pools / Hyperscale / sharding library are AZ-305 §2 scalability patterns. The other options either don't scale or degrade performance.
Related questions
Which Azure data-platform service should an architect recommend for streaming ingestion + Which Cosmos DB consistency level should an architect recommend for a globally-deployed apWhich Azure SQL Database feature should an architect recommend to recover from a regional Which Azure storage replication option should an architect recommend for data that must suWhich Azure storage capability should an architect recommend to provide a hierarchical-namWhich Azure service should an architect recommend to ingest, transform, and orchestrate ETWhich Azure service should an architect recommend for petabyte-scale columnar analytics + Which Cosmos DB feature should an architect recommend to handle a sudden burst from 100 to