100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 290
A query must identify strings matching a supported regular expression. The team selects: Use REGEXP_LIKE on supported SQL engine/version. Which implementation action puts this design into practice?
- Compute JARO_WINKLER_DISTANCE on normalized surname strings and test a threshold
- BEGIN CATCH ROLLBACK; THROW; END CATCH
- Call REGEXP_SUBSTR with tested expression
- REGEXP_LIKE(ColumnName, approved_pattern) in WHERE
Explanation
Correct Answer
D:REGEXP_LIKE(ColumnName, approved_pattern) in WHERE. This is the concrete setup for use regexp_like on supported sql engine/version, and test positive and negative fixtures supplies a direct confirmation.
Incorrect Answers
A:Compute JARO_WINKLER_DISTANCE on normalized surname strings and test a threshold. This concerns typo-resistant matching on customer surnames with prefix-sensitive scores. Here, rEGEXP_LIKE(ColumnName, approved_pattern) in WHERE.
B:BEGIN CATCH ROLLBACK; THROW; END CATCH. This concerns rethrow original error after cleanup. Here, rEGEXP_LIKE(ColumnName, approved_pattern) in WHERE.
C:Call REGEXP_SUBSTR with tested expression. This concerns a log-cleaning query extracts the first matched token. Here, rEGEXP_LIKE(ColumnName, approved_pattern) in WHERE.
Question 291
A query must identify strings matching a supported regular expression. After implementing the design, which check most directly validates the expected behavior?
- Compare with sorted small data samples
- Compare expected cleaned output for complex cases
- Test expected two-hop results
- Test positive and negative fixtures
Explanation
Correct Answer
D:Test positive and negative fixtures. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that pattern matching lacks required regex structure.
Incorrect Answers
A:Compare with sorted small data samples. This concerns returning median of response times by region. Instead, test positive and negative fixtures.
B:Compare expected cleaned output for complex cases. This concerns a text cleansing query replaces matching substrings using regex. Instead, test positive and negative fixtures.
C:Test expected two-hop results. This concerns a graph database query asks for friends of friends. Instead, test positive and negative fixtures.
Question 292
A query must identify strings matching a supported regular expression. A test instead finds: Ordinary LIKE incorrectly accepts malformed IDs. Which underlying issue best explains this finding?
- Regular-expression boundary or greedy capture is wrong
- A cycle or missing recursion guard exists
- REPLACE used where a pattern was required
- Pattern matching lacks required regex structure
Explanation
Correct Answer
D:Pattern matching lacks required regex structure. It accounts for the specific observed failure: ordinary like incorrectly accepts malformed ids. The intended solution is use regexp_like on supported sql engine/version with the required setup.
Incorrect Answers
A:Regular-expression boundary or greedy capture is wrong. This concerns unexpected fragment returned when delimiters vary. Here, pattern matching lacks required regex structure.
B:A cycle or missing recursion guard exists. This concerns recursion errors on circular manager data. Here, pattern matching lacks required regex structure.
C:REPLACE used where a pattern was required. This concerns only literal substring is replaced. Here, pattern matching lacks required regex structure.
Question 293
A log-cleaning query extracts the first matched token. Which database design or engineering approach most directly meets this requirement?
- Use SUM windowed with ordered ROWS frame
- Use REGEXP_LIKE on supported SQL engine/version
- Use REGEXP_REPLACE on supported engine
- Use REGEXP_SUBSTR where supported
Explanation
Correct Answer
D:Use REGEXP_SUBSTR where supported. The implementation is call regexp_substr with tested expression; success can be checked by compare extraction with known log text. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Use SUM windowed with ordered ROWS frame. This concerns cumulative revenue by day. Instead, use REGEXP_SUBSTR where supported.
B:Use REGEXP_LIKE on supported SQL engine/version. This concerns identifying strings matching a supported regular expression. Instead, use REGEXP_SUBSTR where supported.
C:Use REGEXP_REPLACE on supported engine. This concerns a text cleansing query replaces matching substrings using regex. Instead, use REGEXP_SUBSTR where supported.
Question 294
A log-cleaning query extracts the first matched token. The team selects: Use REGEXP_SUBSTR where supported. Which implementation action puts this design into practice?
- Specify tested pattern and replacement with REGEXP_REPLACE
- SUM(Amount) OVER(ORDER BY SaleDate ROWS UNBOUNDED PRECEDING)
- REGEXP_LIKE(ColumnName, approved_pattern) in WHERE
- Call REGEXP_SUBSTR with tested expression
Explanation
Correct Answer
D:Call REGEXP_SUBSTR with tested expression. This is the concrete setup for use regexp_substr where supported, and compare extraction with known log text supplies a direct confirmation.
Incorrect Answers
A:Specify tested pattern and replacement with REGEXP_REPLACE. This concerns a text cleansing query replaces matching substrings using regex. Here, call REGEXP_SUBSTR with tested expression.
B:SUM(Amount) OVER(ORDER BY SaleDate ROWS UNBOUNDED PRECEDING). This concerns cumulative revenue by day. Here, call REGEXP_SUBSTR with tested expression.
C:REGEXP_LIKE(ColumnName, approved_pattern) in WHERE. This concerns identifying strings matching a supported regular expression. Here, call REGEXP_SUBSTR with tested expression.
Question 295
A log-cleaning query extracts the first matched token. After implementing the design, which check most directly validates the expected behavior?
- Compare extraction with known log text
- Compare selected order with each customer's maximum date
- Compare expected cleaned output for complex cases
- Test extraction against known example payload
Explanation
Correct Answer
A:Compare extraction with known log text. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that regular-expression boundary or greedy capture is wrong.
Incorrect Answers
B:Compare selected order with each customer's maximum date. This concerns pick latest order per customer. Instead, compare extraction with known log text.
C:Compare expected cleaned output for complex cases. This concerns a text cleansing query replaces matching substrings using regex. Instead, compare extraction with known log text.
D:Test extraction against known example payload. This concerns reading one scalar value from json document. Instead, compare extraction with known log text.
Question 296
A log-cleaning query extracts the first matched token. A test instead finds: Unexpected fragment returned when delimiters vary. Which underlying issue best explains this finding?
- Regular-expression boundary or greedy capture is wrong
- Window ordering lacks a deterministic tie-breaker
- Pattern matching lacks required regex structure
- JSON path is wrong or payload shape differs
Explanation
Correct Answer
A:Regular-expression boundary or greedy capture is wrong. It accounts for the specific observed failure: unexpected fragment returned when delimiters vary. The intended solution is use regexp_substr where supported with the required setup.
Incorrect Answers
B:Window ordering lacks a deterministic tie-breaker. This concerns top ranks drift across executions on ties. Here, regular-expression boundary or greedy capture is wrong.
C:Pattern matching lacks required regex structure. This concerns ordinary like incorrectly accepts malformed ids. Here, regular-expression boundary or greedy capture is wrong.
D:JSON path is wrong or payload shape differs. This concerns returned value is null for present nested field. Here, regular-expression boundary or greedy capture is wrong.
Question 297
An app scores the similarity of two misspelled names. Which database design or engineering approach most directly meets this requirement?
- Use REGEXP_LIKE on supported SQL engine/version
- Use JSON_ARRAYAGG where supported
- Use JARO_WINKLER_DISTANCE on supported edition
- Use EDIT_DISTANCE_SIMILARITY if supported
Explanation
Correct Answer
D:Use EDIT_DISTANCE_SIMILARITY if supported. The implementation is apply function to normalized names and define threshold; success can be checked by measure score against labeled match/nonmatch pairs. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Use REGEXP_LIKE on supported SQL engine/version. This concerns identifying strings matching a supported regular expression. Instead, use EDIT_DISTANCE_SIMILARITY if supported.
B:Use JSON_ARRAYAGG where supported. This concerns a json array aggregation produces product ids per customer. Instead, use EDIT_DISTANCE_SIMILARITY if supported.
C:Use JARO_WINKLER_DISTANCE on supported edition. This concerns typo-resistant matching on customer surnames with prefix-sensitive scores. Instead, use EDIT_DISTANCE_SIMILARITY if supported.
Question 298
An app scores the similarity of two misspelled names. The team selects: Use EDIT_DISTANCE_SIMILARITY if supported. Which implementation action puts this design into practice?
- Define ROW_NUMBER() OVER(PARTITION BY SalespersonID ORDER BY Amount DESC, OrderID)
- BEGIN CATCH ROLLBACK; THROW; END CATCH
- Apply function to normalized names and define threshold
- Compute JARO_WINKLER_DISTANCE on normalized surname strings and test a threshold
Explanation
Correct Answer
C:Apply function to normalized names and define threshold. This is the concrete setup for use edit_distance_similarity if supported, and measure score against labeled match/nonmatch pairs supplies a direct confirmation.
Incorrect Answers
A:Define ROW_NUMBER() OVER(PARTITION BY SalespersonID ORDER BY Amount DESC, OrderID). This concerns top three sales orders per salesperson. Instead, apply function to normalized names and define threshold.
B:BEGIN CATCH ROLLBACK; THROW; END CATCH. This concerns rethrow original error after cleanup. Instead, apply function to normalized names and define threshold.
D:Compute JARO_WINKLER_DISTANCE on normalized surname strings and test a threshold. This concerns typo-resistant matching on customer surnames with prefix-sensitive scores. Instead, apply function to normalized names and define threshold.
Question 299
An app scores the similarity of two misspelled names. After implementing the design, which check most directly validates the expected behavior?
- Measure score against labeled match/nonmatch pairs
- Verify customers with zero rows are included
- Check known one-insertion and substitution cases
- Inspect known transposition and prefix examples
Explanation
Correct Answer
A:Measure score against labeled match/nonmatch pairs. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that match threshold was not evaluated on labeled data.
Incorrect Answers
B:Verify customers with zero rows are included. This concerns finding customers with no orders. Instead, measure score against labeled match/nonmatch pairs.
C:Check known one-insertion and substitution cases. This concerns the minimum insert/delete/substitute character count rather than a percentage. Instead, measure score against labeled match/nonmatch pairs.
D:Inspect known transposition and prefix examples. This concerns typo-resistant matching on customer surnames with prefix-sensitive scores. Instead, measure score against labeled match/nonmatch pairs.
Question 300
An app scores the similarity of two misspelled names. A test instead finds: Unrelated records are merged by weak similarity threshold. Which underlying issue best explains this finding?
- JSON path or case-sensitive property names do not match
- Match threshold was not evaluated on labeled data
- Similarity was interpreted without a validated threshold
- Regular-expression boundary or greedy capture is wrong
Explanation
Correct Answer
B:Match threshold was not evaluated on labeled data. It accounts for the specific observed failure: unrelated records are merged by weak similarity threshold. The intended solution is use edit_distance_similarity if supported with the required setup.
Incorrect Answers
A:JSON path or case-sensitive property names do not match. This concerns nested array values are null in projection. Here, match threshold was not evaluated on labeled data.
C:Similarity was interpreted without a validated threshold. This concerns names with same prefix falsely merge. Here, match threshold was not evaluated on labeled data.
D:Regular-expression boundary or greedy capture is wrong. This concerns unexpected fragment returned when delimiters vary. Here, match threshold was not evaluated on labeled data.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests