Large historical aggregation reports slow down short customer transactions in the production SQL system. Which architecture addresses the contention?

Choose the single best answer.

A.Run every historical report more frequently on the same primary
B.Catalog report queries without separating their execution from customer transactions
C.Increase primary capacity without considering independent analytical scaling or workload contention
D.Prepare a separate analytical store with independent capacity and a freshness-appropriate ingestion process

Show the answer and explanation

✓ Correct answer

Prepare a separate analytical store with independent capacity and a freshness-appropriate ingestion process

Separating OLAP capacity and data layout isolates large scans from OLTP while freshness drives integration. More scans worsen contention. Larger primary capacity may help temporarily but does not provide independent analytical workload isolation; cataloging does not change where expensive queries run. Source guide: PDF page 32.

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.