Microsoft DP-800 Practice Test 45
Question 440
A database engineer at Pinecrest Operations is investigating this case: A highly selective lookup repeatedly scans a large customers table. The relevant finding is: Existing index begins with a rarely filtered column. What operational condition would provide the earliest useful regression warning?
- Monitor index seek usage and write cost
- Track index usage and storage overhead
- Monitor version-store usage and long transactions
- Monitor Query Store regressed queries
Explanation
Correct Answer
A:
Existing index begins with a rarely filtered column. Monitor index seek usage and write cost.
Incorrect Answers
B:
“Track index usage and storage overhead” addresses the missing index dmv caution situation—a single recommendation ignores write/storage cost. The observed failure is: Existing index begins with a rarely filtered column. Monitor index seek usage and write cost.
C:
“Monitor version-store usage and long transactions” concerns Concurrent updates produce inconsistent intermediate totals; the reported problem instead is Existing index begins with a rarely filtered column. Monitor index seek usage and write cost.
D:
“Monitor Query Store regressed queries” concerns Query Store captures a new high-cost plan; the reported problem instead is Existing index begins with a rarely filtered column. Monitor index seek usage and write cost.
Question 441
Marigold Banking is responsible for an Azure SQL or Microsoft SQL workload. OLTP writes wait behind one idle open transaction. Operational evidence: Lock waits remain while session is inactive. What initial check best narrows the technical cause without altering business data?
- Inspect blocking_session_id, active transaction DMVs and lock owner
- Collect deadlock XML and lock acquisition order
- Inspect columnstore rowgroup DMVs and ingestion batch pattern
- Inspect wait stats, isolation settings and transaction duration
Explanation
Correct Answer
A:
Lock waits remain while session is inactive. Inspect blocking_session_id, active transaction DMVs and lock owner.
Incorrect Answers
B:
“Collect deadlock XML and lock acquisition order” concerns Deadlock graphs repeatedly identify the same pair of statements; the reported problem instead is Lock waits remain while session is inactive. Inspect blocking_session_id, active transaction DMVs and lock owner.
C:
“Inspect columnstore rowgroup DMVs and ingestion batch pattern” concerns Columnstore contains many small delta rowgroups; the reported problem instead is Lock waits remain while session is inactive. Inspect blocking_session_id, active transaction DMVs and lock owner.
D:
“Inspect wait stats, isolation settings and transaction duration” concerns Readers wait for exclusive locks during updates; the reported problem instead is Lock waits remain while session is inactive. Inspect blocking_session_id, active transaction DMVs and lock owner.
Question 442
At Riverbend Retail, oLTP writes wait behind one idle open transaction. The observed constraint is: Lock waits remain while session is inactive. Which proposed change is the most suitable response to the observed constraint?
- Apply bounded retry with idempotency after handling conflicts
- Fix cardinality/index design or query shape before increasing resources
- Choose supported snapshot-based isolation consistent with application needs
- Fix application transaction lifetime and safely handle the blocker
Explanation
Correct Answer
D:
Lock waits remain while session is inactive. Fix application transaction lifetime and safely handle the blocker.
Incorrect Answers
A:
“Apply bounded retry with idempotency after handling conflicts” concerns App treats concurrency conflict as permanent failure; the reported problem instead is Lock waits remain while session is inactive. Fix application transaction lifetime and safely handle the blocker.
B:
“Fix cardinality/index design or query shape before increasing resources” concerns Actual plan warns of spill and high memory grant; the reported problem instead is Lock waits remain while session is inactive. Fix application transaction lifetime and safely handle the blocker.
C:
“Choose supported snapshot-based isolation consistent with application needs” concerns Concurrent updates produce inconsistent intermediate totals; the reported problem instead is Lock waits remain while session is inactive. Fix application transaction lifetime and safely handle the blocker.
Question 443
A database engineer at Prairie Logistics is investigating this case: OLTP writes wait behind one idle open transaction. The relevant finding is: Lock waits remain while session is inactive. What isolated pilot would provide the strongest evidence before rollout?
- Open a test transaction and reproduce blocked update
- Benchmark small and large tenant parameter sets in test SQL
- Replay concurrent update/read workload against a sandbox copy
- Run simultaneous test writer and reader transactions
Explanation
Correct Answer
A:
Lock waits remain while session is inactive. Open a test transaction and reproduce blocked update.
Incorrect Answers
B:
“Benchmark small and large tenant parameter sets in test SQL” concerns The cached query plan favors one selectivity pattern; the reported problem instead is Lock waits remain while session is inactive. Open a test transaction and reproduce blocked update.
C:
“Replay concurrent update/read workload against a sandbox copy” concerns Readers wait for exclusive locks during updates; the reported problem instead is Lock waits remain while session is inactive. Open a test transaction and reproduce blocked update.
D:
“Run simultaneous test writer and reader transactions” concerns Concurrent updates produce inconsistent intermediate totals; the reported problem instead is Lock waits remain while session is inactive. Open a test transaction and reproduce blocked update.
Question 444
Silverpine Labs is responsible for an Azure SQL or Microsoft SQL workload. OLTP writes wait behind one idle open transaction. Operational evidence: Lock waits remain while session is inactive. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Compressed rowgroups and scan efficiency improve
- Spill events decrease and query remains correct
- Invariant preserved and expected one transaction eventually succeeds
- Transactions complete without persistent idle blocking
Explanation
Correct Answer
D:
Lock waits remain while session is inactive. Transactions complete without persistent idle blocking.
Incorrect Answers
A:
“Compressed rowgroups and scan efficiency improve” concerns Columnstore contains many small delta rowgroups; the reported problem instead is Lock waits remain while session is inactive. Transactions complete without persistent idle blocking.
B:
“Spill events decrease and query remains correct” concerns Actual plan warns of spill and high memory grant; the reported problem instead is Lock waits remain while session is inactive. Transactions complete without persistent idle blocking.
C:
“Invariant preserved and expected one transaction eventually succeeds” concerns App treats concurrency conflict as permanent failure; the reported problem instead is Lock waits remain while session is inactive. Transactions complete without persistent idle blocking.
Question 445
At Briarfield Foods, oLTP writes wait behind one idle open transaction. The observed constraint is: Lock waits remain while session is inactive. What operational condition would provide the earliest useful regression warning?
- Monitor open and deleted rowgroup ratios
- Monitor long-running open transactions
- Monitor version-store usage and long transactions
- Monitor index usage and storage overhead
Explanation
Correct Answer
B:
Lock waits remain while session is inactive. Monitor long-running open transactions.
Incorrect Answers
A:
“Monitor open and deleted rowgroup ratios” concerns Columnstore contains many small delta rowgroups; the reported problem instead is Lock waits remain while session is inactive. Monitor long-running open transactions.
C:
“Monitor version-store usage and long transactions” concerns Concurrent updates produce inconsistent intermediate totals; the reported problem instead is Lock waits remain while session is inactive. Monitor long-running open transactions.
D:
“Monitor index usage and storage overhead” concerns A single recommendation ignores write/storage cost; the reported problem instead is Lock waits remain while session is inactive. Monitor long-running open transactions.
Question 446
A database engineer at Northstar Analytics is investigating this case: A large analytic table performs poorly after many tiny inserts. The relevant finding is: Columnstore contains many small delta rowgroups. What initial check best narrows the technical cause without altering business data?
- Inspect columnstore rowgroup DMVs and ingestion batch pattern
- Inspect isolation and row-version conflict errors
- Inspect Query Store plans and parameter distributions
- Inspect blocking_session_id, active transaction DMVs and lock owner
Explanation
Correct Answer
A:
Columnstore contains many small delta rowgroups. Inspect columnstore rowgroup DMVs and ingestion batch pattern.
Incorrect Answers
B:
“Inspect isolation and row-version conflict errors” concerns App treats concurrency conflict as permanent failure; the reported problem instead is Columnstore contains many small delta rowgroups. Inspect columnstore rowgroup DMVs and ingestion batch pattern.
C:
“Inspect Query Store plans and parameter distributions” concerns The cached query plan favors one selectivity pattern; the reported problem instead is Columnstore contains many small delta rowgroups. Inspect columnstore rowgroup DMVs and ingestion batch pattern.
D:
“Inspect blocking_session_id, active transaction DMVs and lock owner” concerns Lock waits remain while session is inactive; the reported problem instead is Columnstore contains many small delta rowgroups. Inspect columnstore rowgroup DMVs and ingestion batch pattern.
Question 447
Maple Harbor Research is responsible for an Azure SQL or Microsoft SQL workload. A large analytic table performs poorly after many tiny inserts. Operational evidence: Columnstore contains many small delta rowgroups. Which proposed change is the most suitable response to the observed constraint?
- Improve batching and supported rowgroup maintenance strategy
- Choose supported snapshot-based isolation consistent with application needs
- Update appropriate statistics or adjust stats maintenance process
- Use appropriate plan-stability or parameter-sensitivity strategy based on supported engine
Explanation
Correct Answer
A:
Columnstore contains many small delta rowgroups. Improve batching and supported rowgroup maintenance strategy.
Incorrect Answers
B:
“Choose supported snapshot-based isolation consistent with application needs” concerns Concurrent updates produce inconsistent intermediate totals; the reported problem instead is Columnstore contains many small delta rowgroups. Improve batching and supported rowgroup maintenance strategy.
C:
“Update appropriate statistics or adjust stats maintenance process” concerns Outdated statistics misestimate filtered cardinality; the reported problem instead is Columnstore contains many small delta rowgroups. Improve batching and supported rowgroup maintenance strategy.
D:
“Use appropriate plan-stability or parameter-sensitivity strategy based on supported engine” concerns The cached query plan favors one selectivity pattern; the reported problem instead is Columnstore contains many small delta rowgroups. Improve batching and supported rowgroup maintenance strategy.
Question 448
At Juniper Commerce, a large analytic table performs poorly after many tiny inserts. The observed constraint is: Columnstore contains many small delta rowgroups. What isolated pilot would provide the strongest evidence before rollout?
- Run two conflicting sandbox updates with retry policy
- Run simultaneous test writer and reader transactions
- Bulk-load comparable test batches and run aggregates
- Load skewed fixture and compare query plans before/after stats refresh
Explanation
Correct Answer
C:
Columnstore contains many small delta rowgroups. Bulk-load comparable test batches and run aggregates.
Incorrect Answers
A:
“Run two conflicting sandbox updates with retry policy” concerns App treats concurrency conflict as permanent failure; the reported problem instead is Columnstore contains many small delta rowgroups. Bulk-load comparable test batches and run aggregates.
B:
“Run simultaneous test writer and reader transactions” concerns Concurrent updates produce inconsistent intermediate totals; the reported problem instead is Columnstore contains many small delta rowgroups. Bulk-load comparable test batches and run aggregates.
D:
“Load skewed fixture and compare query plans before/after stats refresh” concerns Outdated statistics misestimate filtered cardinality; the reported problem instead is Columnstore contains many small delta rowgroups. Bulk-load comparable test batches and run aggregates.
Question 449
A database engineer at Summit Logistics is investigating this case: A large analytic table performs poorly after many tiny inserts. The relevant finding is: Columnstore contains many small delta rowgroups. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Invariant preserved and expected one transaction eventually succeeds
- Cardinality estimates and plan selection improve appropriately
- Compressed rowgroups and scan efficiency improve
- Spill events decrease and query remains correct
Explanation
Correct Answer
C:
Columnstore contains many small delta rowgroups. Compressed rowgroups and scan efficiency improve.
Incorrect Answers
A:
“Invariant preserved and expected one transaction eventually succeeds” concerns App treats concurrency conflict as permanent failure; the reported problem instead is Columnstore contains many small delta rowgroups. Compressed rowgroups and scan efficiency improve.
B:
“Cardinality estimates and plan selection improve appropriately” concerns Outdated statistics misestimate filtered cardinality; the reported problem instead is Columnstore contains many small delta rowgroups. Compressed rowgroups and scan efficiency improve.
D:
“Spill events decrease and query remains correct” concerns Actual plan warns of spill and high memory grant; the reported problem instead is Columnstore contains many small delta rowgroups. Compressed rowgroups and scan efficiency improve.
Question 450
BrightPath Studios is responsible for an Azure SQL or Microsoft SQL workload. A large analytic table performs poorly after many tiny inserts. Operational evidence: Columnstore contains many small delta rowgroups. What operational condition would provide the earliest useful regression warning?
- Monitor long-running open transactions
- Monitor open and deleted rowgroup ratios
- Monitor Query Store regressed queries
- Monitor index usage and storage overhead
Explanation
Correct Answer
B:
Columnstore contains many small delta rowgroups. Monitor open and deleted rowgroup ratios.
Incorrect Answers
A:
“Monitor long-running open transactions” concerns Lock waits remain while session is inactive; the reported problem instead is Columnstore contains many small delta rowgroups. Monitor open and deleted rowgroup ratios.
C:
“Monitor Query Store regressed queries” concerns Query Store captures a new high-cost plan; the reported problem instead is Columnstore contains many small delta rowgroups. Monitor open and deleted rowgroup ratios.
D:
“Monitor index usage and storage overhead” concerns A single recommendation ignores write/storage cost; the reported problem instead is Columnstore contains many small delta rowgroups. Monitor open and deleted rowgroup ratios.