Microsoft DP-800 Practice Test 3
Question 20
A database engineer at Briarfield Foods is investigating this case: A payment ledger stores decimal currency with exact reconciliation. The relevant finding is: FLOAT introduces approximate representations in money calculations. What operational condition would provide the earliest useful regression warning?
- Watch conversion and arithmetic overflow errors
- Observe constraint violations in ingestion logs
- Watch partition boundary maintenance and skew
- Watch rowgroup health and segment elimination
Explanation
Correct Answer
A:
FLOAT introduces approximate representations in money calculations. Watch conversion and arithmetic overflow errors.
Incorrect Answers
B:
“Observe constraint violations in ingestion logs” addresses the foreign key referential integrity situation—orphan records appear after bulk import. The observed failure is: FLOAT introduces approximate representations in money calculations. Watch conversion and arithmetic overflow errors.
C:
“Watch partition boundary maintenance and skew” concerns Large deletes cause long log usage and blocking; the reported problem instead is FLOAT introduces approximate representations in money calculations. Watch conversion and arithmetic overflow errors.
D:
“Watch rowgroup health and segment elimination” concerns Row-oriented scans consume excessive I/O for aggregation; the reported problem instead is FLOAT introduces approximate representations in money calculations. Watch conversion and arithmetic overflow errors.
Question 21
Northstar Analytics is responsible for an Azure SQL or Microsoft SQL workload. A vendor needs the full history of contract row changes. Operational evidence: Overwriting rows discards prior valid values. What initial check best narrows the technical cause without altering business data?
- Inspect current defaults and time-zone expectations
- Inspect range boundaries and partition-alignment requirements
- Inspect existing out-of-range values and column nullability
- Inspect whether system time and change history must be queryable
Explanation
Correct Answer
D:
Overwriting rows discards prior valid values. Inspect whether system time and change history must be queryable.
Incorrect Answers
A:
An insertion timestamp records one moment but does not retain the previous values after an UPDATE. Temporal history or a defined versioning approach is needed to query prior states.
B:
Date partitions can ease data management and pruning; they do not automatically preserve earlier versions of a row that an update overwrites.
C:
A CHECK constraint rejects values outside allowed ranges, but it does not preserve superseded values for historical audits. Row version history is the missing capability.
Question 22
At Maple Harbor Research, a vendor needs the full history of contract row changes. The observed constraint is: Overwriting rows discards prior valid values. Which proposed change is the most suitable response to the observed constraint?
- Define supported external tables and credentials for the remote source
- Consider graph node and edge tables when relationship traversal justifies them
- Evaluate a memory-optimized table only when workload and supported features fit
- Configure system-versioned temporal tables with a history table
Explanation
Correct Answer
D:
Overwriting rows discards prior valid values. Configure system-versioned temporal tables with a history table.
Incorrect Answers
A:
“Define supported external tables and credentials for the remote source” concerns Copying all external data hourly is costly; the reported problem instead is Overwriting rows discards prior valid values. Configure system-versioned temporal tables with a history table.
B:
“Consider graph node and edge tables when relationship traversal justifies them” concerns Multiple self-joins make variable-depth connections difficult; the reported problem instead is Overwriting rows discards prior valid values. Configure system-versioned temporal tables with a history table.
C:
“Evaluate a memory-optimized table only when workload and supported features fit” concerns A small set of hot rows is updated at high frequency; the reported problem instead is Overwriting rows discards prior valid values. Configure system-versioned temporal tables with a history table.
Question 23
A database engineer at Juniper Commerce is investigating this case: A vendor needs the full history of contract row changes. The relevant finding is: Overwriting rows discards prior valid values. What isolated pilot would provide the strongest evidence before rollout?
- Run concurrent inserts for the same synthetic SKU
- Update synthetic contracts and query an earlier AS OF timestamp
- Insert sample rows omitting and specifying a timestamp
- Insert synthetic transfer edges and run a MATCH graph query
Explanation
Correct Answer
B:
Overwriting rows discards prior valid values. Update synthetic contracts and query an earlier AS OF timestamp.
Incorrect Answers
A:
“Run concurrent inserts for the same synthetic SKU” concerns Application-level duplicate checks race under concurrency; the reported problem instead is Overwriting rows discards prior valid values. Update synthetic contracts and query an earlier AS OF timestamp.
C:
An insertion timestamp records one moment but does not retain the previous values after an UPDATE. Temporal history or a defined versioning approach is needed to query prior states.
D:
“Insert synthetic transfer edges and run a MATCH graph query” concerns Multiple self-joins make variable-depth connections difficult; the reported problem instead is Overwriting rows discards prior valid values. Update synthetic contracts and query an earlier AS OF timestamp.
Question 24
Summit Logistics is responsible for an Azure SQL or Microsoft SQL workload. A vendor needs the full history of contract row changes. Operational evidence: Overwriting rows discards prior valid values. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Database rejects disallowed values regardless of client
- Historical values are retrievable after updates without custom triggers
- Missing values receive the documented default without overwriting explicit values
- Unauthorized historical manipulation is detectable through verification
Explanation
Correct Answer
B:
Overwriting rows discards prior valid values. Historical values are retrievable after updates without custom triggers.
Incorrect Answers
A:
A CHECK constraint rejects values outside allowed ranges, but it does not preserve superseded values for historical audits. Row version history is the missing capability.
C:
An insertion timestamp records one moment but does not retain the previous values after an UPDATE. Temporal history or a defined versioning approach is needed to query prior states.
D:
“Unauthorized historical manipulation is detectable through verification” concerns Ordinary audit timestamps are not tamper-evident; the reported problem instead is Overwriting rows discards prior valid values. Historical values are retrievable after updates without custom triggers.
Question 25
At BrightPath Studios, a vendor needs the full history of contract row changes. The observed constraint is: Overwriting rows discards prior valid values. What operational condition would provide the earliest useful regression warning?
- Monitor history-table growth and retention settings
- Monitor edge integrity and query cost
- Monitor plan regressions and index maintenance
- Monitor truncation failures and unexpected growth
Explanation
Correct Answer
A:
Overwriting rows discards prior valid values. Monitor history-table growth and retention settings.
Incorrect Answers
B:
“Monitor edge integrity and query cost” concerns Multiple self-joins make variable-depth connections difficult; the reported problem instead is Overwriting rows discards prior valid values. Monitor history-table growth and retention settings.
C:
“Monitor plan regressions and index maintenance” concerns Repeated JSON_VALUE evaluation produces expensive scans; the reported problem instead is Overwriting rows discards prior valid values. Monitor history-table growth and retention settings.
D:
“Monitor truncation failures and unexpected growth” concerns Fixed CHAR allocation wastes space on short product names; the reported problem instead is Overwriting rows discards prior valid values. Monitor history-table growth and retention settings.
Question 26
A database engineer at Lakeview Services is investigating this case: An organization needs cryptographic evidence when transaction records change. The relevant finding is: Ordinary audit timestamps are not tamper-evident. What initial check best narrows the technical cause without altering business data?
- Review audit assurance requirement and ledger feature availability
- Compare contention waits and transactional feature limitations
- Assess key stability, uniqueness, and referencing tables
- Inspect index fragmentation, page splits, and insert pattern
Explanation
Correct Answer
A:
Ordinary audit timestamps are not tamper-evident. Review audit assurance requirement and ledger feature availability.
Incorrect Answers
B:
Memory-optimized tables address transactional concurrency and latency; they do not provide the cryptographically verifiable audit chain required for tamper-evident records.
C:
“Assess key stability, uniqueness, and referencing tables” concerns Username changes cascade to many child records; the reported problem instead is Ordinary audit timestamps are not tamper-evident. Review audit assurance requirement and ledger feature availability.
D:
B-tree fill factor is a page-maintenance tuning choice. Reducing page splits cannot make an audit timestamp or record history tamper-evident.
Question 27
Crownridge Travel is responsible for an Azure SQL or Microsoft SQL workload. An organization needs cryptographic evidence when transaction records change. Operational evidence: Ordinary audit timestamps are not tamper-evident. Which proposed change is the most suitable response to the observed constraint?
- Configure system-versioned temporal tables with a history table
- Evaluate a memory-optimized table only when workload and supported features fit
- Evaluate an append-only or updatable ledger table with digest verification
- Evaluate fill factor or a less-random clustering key when evidence supports it
Explanation
Correct Answer
C:
Ordinary audit timestamps are not tamper-evident. Evaluate an append-only or updatable ledger table with digest verification.
Incorrect Answers
A:
Temporal tables preserve row versions and validity periods, but historical storage alone is not cryptographic evidence that privileged modification has not occurred. SQL ledger supplies tamper-evidence features.
B:
Memory-optimized tables address transactional concurrency and latency; they do not provide the cryptographically verifiable audit chain required for tamper-evident records.
D:
B-tree fill factor is a page-maintenance tuning choice. Reducing page splits cannot make an audit timestamp or record history tamper-evident.
Question 28
At Oakridge Advisors, an organization needs cryptographic evidence when transaction records change. The observed constraint is: Ordinary audit timestamps are not tamper-evident. What isolated pilot would provide the strongest evidence before rollout?
- Change a sandbox ledger record and validate digest verification
- Insert synthetic transfer edges and run a MATCH graph query
- Benchmark representative insert sequences with alternative designs
- Change test usernames while maintaining foreign references
Explanation
Correct Answer
A:
Ordinary audit timestamps are not tamper-evident. Change a sandbox ledger record and validate digest verification.
Incorrect Answers
B:
“Insert synthetic transfer edges and run a MATCH graph query” concerns Multiple self-joins make variable-depth connections difficult; the reported problem instead is Ordinary audit timestamps are not tamper-evident. Change a sandbox ledger record and validate digest verification.
C:
B-tree fill factor is a page-maintenance tuning choice. Reducing page splits cannot make an audit timestamp or record history tamper-evident.
D:
“Change test usernames while maintaining foreign references” concerns Username changes cascade to many child records; the reported problem instead is Ordinary audit timestamps are not tamper-evident. Change a sandbox ledger record and validate digest verification.
Question 29
A database engineer at Horizon Communications is investigating this case: An organization needs cryptographic evidence when transaction records change. The relevant finding is: Ordinary audit timestamps are not tamper-evident. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Page-split rate falls without excessive storage growth
- Historical values are retrievable after updates without custom triggers
- Unauthorized historical manipulation is detectable through verification
- Child relationships survive mutable business-field changes
Explanation
Correct Answer
C:
Ordinary audit timestamps are not tamper-evident. Unauthorized historical manipulation is detectable through verification.
Incorrect Answers
A:
B-tree fill factor is a page-maintenance tuning choice. Reducing page splits cannot make an audit timestamp or record history tamper-evident.
B:
Temporal tables preserve row versions and validity periods, but historical storage alone is not cryptographic evidence that privileged modification has not occurred. SQL ledger supplies tamper-evidence features.
D:
“Child relationships survive mutable business-field changes” concerns Username changes cascade to many child records; the reported problem instead is Ordinary audit timestamps are not tamper-evident. Unauthorized historical manipulation is detectable through verification.
Question 30
Brookfield Labs is responsible for an Azure SQL or Microsoft SQL workload. An organization needs cryptographic evidence when transaction records change. Operational evidence: Ordinary audit timestamps are not tamper-evident. What operational condition would provide the earliest useful regression warning?
- Track digest storage, verification failures, and feature compatibility
- Track fragmentation and write amplification over time
- Monitor truncation failures and unexpected growth
- Track index usage and modification overhead after rollout
Explanation
Correct Answer
A:
Ordinary audit timestamps are not tamper-evident. Track digest storage, verification failures, and feature compatibility.
Incorrect Answers
B:
B-tree fill factor is a page-maintenance tuning choice. Reducing page splits cannot make an audit timestamp or record history tamper-evident.
C:
“Monitor truncation failures and unexpected growth” concerns Fixed CHAR allocation wastes space on short product names; the reported problem instead is Ordinary audit timestamps are not tamper-evident. Track digest storage, verification failures, and feature compatibility.
D:
“Track index usage and modification overhead after rollout” concerns Table scans occur despite highly selective filters; the reported problem instead is Ordinary audit timestamps are not tamper-evident. Track digest storage, verification failures, and feature compatibility.
