Match each performance optimization technique to its description.
Drag a concept onto its matching description — or click a concept then click the description.
Dividing data into smaller manageable segments
Creating structures to speed up data retrieval
Pre-computed and stored query results
Column-based storage for analytics queries
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Columnstore Indexes: Improves query performance by storing data in columnar format, allowing better compression and faster scanning.
Correct matches: Columnstore indexes improve scan performance via columnar storage; partition switching enables fast data segment movement; materialized views pre-compute aggregations; result set caching caches query results. Common confusions include swapping partition switching with columnstore indexes or materialized views with result set caching.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Columnstore Indexes: Improves query performance by storing data in columnar format, allowing better compression and faster scanning.
Why this is correct
Columnstore indexes store data in columnar format, improving compression and scan performance for analytical queries.
Partition Switching: Enables fast loading and removal of large data segments by moving entire partitions between tables without data movement.
Why this is correct
Partition switching allows efficient data loading and archiving by moving whole partitions, avoiding costly data movement.
Materialized Views: Pre-computed and stored views that improve performance of complex aggregations by reducing recomputation.
Why this is correct
Materialized views store pre-computed results, speeding up aggregations and complex queries.
Result Set Caching: Stores query results in cache to reuse for repeated queries, reducing computation time.
Why this is correct
Result set caching caches query results so identical queries can be served from cache, reducing compute overhead.
Columnstore Indexes: Enables fast loading and removal of large data segments.
Why it's wrong here
Incorrect — this definition describes partition switching, not columnstore indexes.
Materialized Views: Stores query results in cache to reuse for repeated queries.
Why it's wrong here
Incorrect — this definition describes result set caching, not materialized views.
Go deeper
About these practice questions
This DP-203 question is part of Courseiva's 760-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-203 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-203 exam.