Microsoft DP-700 Practice Test 35
Question 340
A warehouse statement reports a duplicate key or matching-row conflict during MERGE. What source-side rule should be inspected?
- Inspect the warehouse's current schema and fix the outdated column reference.
- Ensure the staging source has a single intended current record per merge key.
- Review the service principal's effective warehouse and table permissions.
- Correct the join grain or preaggregate the many side before summing.
Explanation
Correct Answer
B:Multiple source matches to one target key make an upsert ambiguous and can fail or produce wrong results. Count duplicate business keys before rerunning MERGE.
Incorrect Answers
A:SQL binding uses existing object metadata; a missing column cannot be corrected by increasing warehouse capacity.
C:Different identities can have different item and SQL grants; successful execution by an owner proves little about the pipeline identity.
D:Row multiplication is a relational logic error; adding memory does not restore additive correctness.
Question 341
A SQL query succeeds when run as an owner but fails under a service principal. What should be checked?
- Restore or update the dependent view to reference the current table definition.
- Review the service principal's effective warehouse and table permissions.
- Ensure the staging source has a single intended current record per merge key.
- Populate the required NOT NULL column or apply an approved default in the target design.
Explanation
Correct Answer
B:Different identities can have different item and SQL grants; successful execution by an owner proves little about the pipeline identity. Execute a least-privileged test SELECT.
Incorrect Answers
A:Schema dependencies must remain valid across deployments; retrying an unchanged invalid view will not help.
C:Multiple source matches to one target key make an upsert ambiguous and can fail or produce wrong results.
D:Required-column constraints prevent inserting incomplete records; bypassing validation would hide missing business data.
Question 342
A T-SQL aggregation reports inflated total sales after a join to a one-to-many table. What should be changed?
- Restore or update the dependent view to reference the current table definition.
- Correct the join grain or preaggregate the many side before summing.
- Ensure the staging source has a single intended current record per merge key.
- Populate the required NOT NULL column or apply an approved default in the target design.
Explanation
Correct Answer
B:Row multiplication is a relational logic error; adding memory does not restore additive correctness. Compare fact row counts before and after the join.
Incorrect Answers
A:Schema dependencies must remain valid across deployments; retrying an unchanged invalid view will not help.
C:Multiple source matches to one target key make an upsert ambiguous and can fail or produce wrong results.
D:Required-column constraints prevent inserting incomplete records; bypassing validation would hide missing business data.
Question 343
A query fails because a view references a table removed in the latest deployment. What remediation applies?
- Review the service principal's effective warehouse and table permissions.
- Correct the join grain or preaggregate the many side before summing.
- Ensure the staging source has a single intended current record per merge key.
- Restore or update the dependent view to reference the current table definition.
Explanation
Correct Answer
D:Schema dependencies must remain valid across deployments; retrying an unchanged invalid view will not help. Run dependency tests against the final warehouse objects.
Incorrect Answers
A:Different identities can have different item and SQL grants; successful execution by an owner proves little about the pipeline identity.
B:Row multiplication is a relational logic error; adding memory does not restore additive correctness.
C:Multiple source matches to one target key make an upsert ambiguous and can fail or produce wrong results.
Question 344
A shortcut fails after an S3 credential was rotated. What should be updated?
- Renew the cloud connection's S3 credential and verify the target bucket is still authorized.
- Grant the shortcut connection identity the needed source folder ACL traversal and read rights.
- Rename or recreate the shortcut with a Delta-compatible table name that contains no spaces.
- Correct the shortcut target key prefix and casing to match the actual S3 object path.
Explanation
Correct Answer
A:A shortcut uses connection authorization for external access; changing the lakehouse table name won't restore authentication. Read a test object through the repaired shortcut.
Incorrect Answers
B:Valid storage-account credentials do not by themselves guarantee directory-level access under hierarchical namespace ACLs.
C:Delta table discovery in the lakehouse requires valid names; a shortcut with spaces may not be recognized as a table.
D:S3 object keys and prefixes are case-sensitive; a path typo can make an authorized shortcut point to an absent source.
Question 345
An Amazon S3 shortcut resolves its bucket but returns not found for a case-sensitive key prefix. What should be corrected?
- Rename or recreate the shortcut with a Delta-compatible table name that contains no spaces.
- Compare connection binding authorization and OneLake security grants for the other identity.
- Correct the shortcut target key prefix and casing to match the actual S3 object path.
- Renew the cloud connection's S3 credential and verify the target bucket is still authorized.
Explanation
Correct Answer
C:S3 object keys and prefixes are case-sensitive; a path typo can make an authorized shortcut point to an absent source. List the exact prefix and read a known object through the shortcut.
Incorrect Answers
A:Delta table discovery in the lakehouse requires valid names; a shortcut with spaces may not be recognized as a table.
B:External shortcut reads depend on connection identity and the data permissions applicable to the user.
D:A shortcut uses connection authorization for external access; changing the lakehouse table name won't restore authentication.
Question 346
A new internal shortcut is visible but one viewer cannot read its Delta data. What should be evaluated?
- Correct the shortcut target key prefix and casing to match the actual S3 object path.
- Rename or recreate the shortcut with a Delta-compatible table name that contains no spaces.
- Check the viewer's read permission on the original OneLake target.
- Renew the cloud connection's S3 credential and verify the target bucket is still authorized.
Explanation
Correct Answer
C:Internal shortcut access is subject to source authorization; visibility of the pointer does not prove read rights. Query the target and shortcut with the same viewer identity.
Incorrect Answers
A:S3 object keys and prefixes are case-sensitive; a path typo can make an authorized shortcut point to an absent source.
B:Delta table discovery in the lakehouse requires valid names; a shortcut with spaces may not be recognized as a table.
D:A shortcut uses connection authorization for external access; changing the lakehouse table name won't restore authentication.
Question 347
An S3 shortcut points to a bucket that was deleted, leaving a stale entry in OneLake. What is the root issue?
- Rename or recreate the shortcut with a Delta-compatible table name that contains no spaces.
- Restore the intended external source or redirect the shortcut to an existing target.
- Grant the shortcut connection identity the needed source folder ACL traversal and read rights.
- Renew the cloud connection's S3 credential and verify the target bucket is still authorized.
Explanation
Correct Answer
B:The shortcut is only a pointer and cannot serve bytes absent from its source location. Verify the bucket or object actually exists.
Incorrect Answers
A:Delta table discovery in the lakehouse requires valid names; a shortcut with spaces may not be recognized as a table.
C:Valid storage-account credentials do not by themselves guarantee directory-level access under hierarchical namespace ACLs.
D:A shortcut uses connection authorization for external access; changing the lakehouse table name won't restore authentication.
Question 348
An ADLS Gen2 shortcut authenticates to the storage account but cannot traverse a restricted directory. What source-side control must be examined?
- Restore the intended external source or redirect the shortcut to an existing target.
- Rename or recreate the shortcut with a Delta-compatible table name that contains no spaces.
- Grant the shortcut connection identity the needed source folder ACL traversal and read rights.
- Correct the shortcut target key prefix and casing to match the actual S3 object path.
Explanation
Correct Answer
C:Valid storage-account credentials do not by themselves guarantee directory-level access under hierarchical namespace ACLs. Test path traversal and file reads using the bound connection identity.
Incorrect Answers
A:The shortcut is only a pointer and cannot serve bytes absent from its source location.
B:Delta table discovery in the lakehouse requires valid names; a shortcut with spaces may not be recognized as a table.
D:S3 object keys and prefixes are case-sensitive; a path typo can make an authorized shortcut point to an absent source.
Question 349
A shortcut under lakehouse Tables references valid Delta data but has a space in its name and is not recognized as a table. What should be corrected?
- Rename or recreate the shortcut with a Delta-compatible table name that contains no spaces.
- Correct the shortcut target key prefix and casing to match the actual S3 object path.
- Compare connection binding authorization and OneLake security grants for the other identity.
- Check the viewer's read permission on the original OneLake target.
Explanation
Correct Answer
A:Delta table discovery in the lakehouse requires valid names; a shortcut with spaces may not be recognized as a table. Verify the renamed shortcut appears as a table in SQL discovery.
Incorrect Answers
B:S3 object keys and prefixes are case-sensitive; a path typo can make an authorized shortcut point to an absent source.
C:External shortcut reads depend on connection identity and the data permissions applicable to the user.
D:Internal shortcut access is subject to source authorization; visibility of the pointer does not prove read rights.
Question 350
An external shortcut works for the author but not another user after a security change. Where should investigation focus?
- Correct the shortcut target key prefix and casing to match the actual S3 object path.
- Compare connection binding authorization and OneLake security grants for the other identity.
- Rename or recreate the shortcut with a Delta-compatible table name that contains no spaces.
- Grant the shortcut connection identity the needed source folder ACL traversal and read rights.
Explanation
Correct Answer
B:External shortcut reads depend on connection identity and the data permissions applicable to the user. Inspect effective roles and run a controlled read.
Incorrect Answers
A:S3 object keys and prefixes are case-sensitive; a path typo can make an authorized shortcut point to an absent source.
C:Delta table discovery in the lakehouse requires valid names; a shortcut with spaces may not be recognized as a table.
D:Valid storage-account credentials do not by themselves guarantee directory-level access under hierarchical namespace ACLs.
