Question 750
A large append-heavy fact table powers aggregate scans across millions of sales while rare row updates remain. Which implementation step most directly addresses this requirement?
Explanation
Correct Answer
Columnstore indexes compress columnar data and can accelerate scan-heavy analytic aggregation. Pilot a suitable clustered or nonclustered columnstore configuration on supported SQL. Aggregate workload improves while operational update latency stays acceptable.
Incorrect Answers
That change leaves the underlying defect unresolved: Columnstore optimizes large columnar scans and compression; benchmark actual aggregate workload and residual writes.
The proposed implementation creates the wrong boundary because Columnstore is workload-dependent; test ingestion/update behavior and point-access requirements.
This step would not produce the required behavior: Compression and batch execution depend on realistic data distribution, rowgroups and query shape. This alternative omits a necessary contract or control and leaves the tested failure path open.