A write-heavy SaaS workload has reached practical single-database limits. Tenant-scoped transactions dominate and cross-tenant queries are rare. Which design best supports further write scaling?

Choose the single best answer.

A.Put all tenants in an elastic pool and assume it multiplies one database's write throughput indefinitely
B.Add read-only replicas and send writes to them unchanged
C.Cache every write without persisting it
D.Shard tenants across databases using an access-aligned key and plan cross-shard operations

Show the answer and explanation

✓ Correct answer

Shard tenants across databases using an access-aligned key and plan cross-shard operations

Sharding distributes write ownership across databases but requires query/transaction design. Read-only replicas do not accept ordinary primary writes. Pooling shares resources and does not make one database unlimited. A cache is not durable write ownership. Source guide: PDF page 24.

Read the source reference

This item is flagged for content review.

Read and review here, or open the app to practise and save your results on this device.

Practise in the app

Unofficial study aid; not affiliated with or endorsed by Microsoft. Original practice questions are not real examination questions and do not guarantee an exam result.