Microsoft DP-700 Practice Test 25
Question 240
Eventhouse must support frequent indexed searches over newly ingested telemetry. Where should the events be stored?
- Check shortcut connection and effective permissions to the referenced target.
- Create a OneLake shortcut in a KQL database and query it using external_table().
- Alter the external Delta table schema to include the new source column or re-enable automatic schema synchronization.
- Ingest into native Eventhouse KQL tables rather than relying solely on external shortcut reads.
Explanation
Correct Answer
D:Native ingestion supplies Eventhouse indexing and storage optimization for repeated low-latency event queries. Measure filter latency against a representative dataset.
Incorrect Answers
A:Creating an external table reference does not bypass authorization for the source data.
B:KQL database shortcuts expose external data as queryable tables without making a native ingested copy.
C:A KQL external table may require updated metadata after Delta schema changes; its logical link alone does not guarantee every consumer schema stays synchronized.
Question 241
A team wants to query an existing lakehouse Delta table through KQL without copying it. Which feature provides the logical reference?
- Create a OneLake shortcut in a KQL database and query it using external_table().
- Recognize the shortcut as external data without the same native ingestion indexes.
- Ingest into native Eventhouse KQL tables rather than relying solely on external shortcut reads.
- Alter the external Delta table schema to include the new source column or re-enable automatic schema synchronization.
Explanation
Correct Answer
A:KQL database shortcuts expose external data as queryable tables without making a native ingested copy. Run a scoped external_table query.
Incorrect Answers
B:External reads can pay storage fetch and indexing penalties compared with native Eventhouse tables.
C:Native ingestion supplies Eventhouse indexing and storage optimization for repeated low-latency event queries.
D:A KQL external table may require updated metadata after Delta schema changes; its logical link alone does not guarantee every consumer schema stays synchronized.
Question 242
A KQL query against a shortcut is slower than a native ingested table because external files must be fetched. Which distinction explains it?
- Check shortcut connection and effective permissions to the referenced target.
- Create a OneLake shortcut in a KQL database and query it using external_table().
- Recognize the shortcut as external data without the same native ingestion indexes.
- Alter the external Delta table schema to include the new source column or re-enable automatic schema synchronization.
Explanation
Correct Answer
C:External reads can pay storage fetch and indexing penalties compared with native Eventhouse tables. Compare the query plans and data access metrics.
Incorrect Answers
A:Creating an external table reference does not bypass authorization for the source data.
B:KQL database shortcuts expose external data as queryable tables without making a native ingested copy.
D:A KQL external table may require updated metadata after Delta schema changes; its logical link alone does not guarantee every consumer schema stays synchronized.
Question 243
A KQL database external Delta shortcut has AutoUpdateSchema disabled. The OneLake source adds a column, but KQL still shows the old schema. What must be changed to expose the new column?
- Design a native ingestion path if the materialized-view requirement cannot be satisfied on the external shortcut.
- Recognize the shortcut as external data without the same native ingestion indexes.
- Alter the external Delta table schema to include the new source column or re-enable automatic schema synchronization.
- Create a OneLake shortcut in a KQL database and query it using external_table().
Explanation
Correct Answer
C:A KQL external table may require updated metadata after Delta schema changes; its logical link alone does not guarantee every consumer schema stays synchronized. Inspect the external table columns after updating its schema.
Incorrect Answers
A:Accelerated external tables retain shortcut limitations, including unavailable native update-policy or materialized-view capabilities.
B:External reads can pay storage fetch and indexing penalties compared with native Eventhouse tables.
D:KQL database shortcuts expose external data as queryable tables without making a native ingested copy.
Question 244
A telemetry database must retain raw ingested events and use update policies for derived native tables. Which landing form is appropriate?
- Land the source events into supported native KQL tables.
- Create a OneLake shortcut in a KQL database and query it using external_table().
- Alter the external Delta table schema to include the new source column or re-enable automatic schema synchronization.
- Check shortcut connection and effective permissions to the referenced target.
Explanation
Correct Answer
A:Native tables support ingestion-time processing patterns that external shortcut tables may not support. Inspect the table and derived update-policy results.
Incorrect Answers
B:KQL database shortcuts expose external data as queryable tables without making a native ingested copy.
C:A KQL external table may require updated metadata after Delta schema changes; its logical link alone does not guarantee every consumer schema stays synchronized.
D:Creating an external table reference does not bypass authorization for the source data.
Question 245
A team wants to apply a native materialized view over an accelerated external Delta shortcut. What limitation should they respect?
- Keep the native materialized view bound directly to the accelerated external Delta shortcut because caching supposedly turns that shortcut into a native KQL table.
- Check shortcut connection and effective permissions to the referenced target.
- Design a native ingestion path if the materialized-view requirement cannot be satisfied on the external shortcut.
- Alter the external Delta table schema to include the new source column or re-enable automatic schema synchronization.
Explanation
Correct Answer
C:Query acceleration improves reads over an external Delta shortcut but does not convert the external table into a native Eventhouse table. If a native materialized view is required, ingest the selected data into a supported native table and build the view there.
Incorrect Answers
A:Accelerated shortcuts remain external Delta tables even when they have query caches and indexes. Microsoft documents that query acceleration does not make materialized views or update policies supported on external shortcuts, so the direct native view would still be invalid.
B:Creating an external table reference does not bypass authorization for the source data. Accelerated external tables retain shortcut limitations, including unavailable native update-policy or materialized-view capabilities. Validate the chosen table type supports the planned view.
D:A KQL external table may require updated metadata after Delta schema changes; its logical link alone does not guarantee every consumer schema stays synchronized. Accelerated external tables retain shortcut limitations, including unavailable native update-policy or materialized-view capabilities. Validate the chosen table type supports the planned view.
Question 246
A KQL external shortcut points to a data location where the user lacks access. What should be verified?
- Design a native ingestion path if the materialized-view requirement cannot be satisfied on the external shortcut.
- Create a OneLake shortcut in a KQL database and query it using external_table().
- Ingest into native Eventhouse KQL tables rather than relying solely on external shortcut reads.
- Check shortcut connection and effective permissions to the referenced target.
Explanation
Correct Answer
D:Creating an external table reference does not bypass authorization for the source data. Test the same query with a correctly authorized identity.
Incorrect Answers
A:Accelerated external tables retain shortcut limitations, including unavailable native update-policy or materialized-view capabilities.
B:KQL database shortcuts expose external data as queryable tables without making a native ingested copy.
C:Native ingestion supplies Eventhouse indexing and storage optimization for repeated low-latency event queries.
Question 247
A frequently queried external Delta shortcut is slower than expected, and copying all source data is prohibited. What optimization should be considered?
- Optimize source Delta file layout and count where the owning system permits it.
- Include applicable OneLake premium cache and indexing consumption in the cost model.
- Configure query acceleration caching for the eligible external Delta table.
- Set a cache duration aligned with the intended recent-data query window.
Explanation
Correct Answer
C:Query acceleration caches selected shortcut data for faster queries while leaving the source as an external reference. Compare query latency and cache statistics.
Incorrect Answers
A:File count and metadata overhead still affect external scan and caching efficiency despite acceleration.
B:Acceleration uses cache capacity and may consume CUs for indexing; it is not a zero-cost equivalent of leaving the data uncached.
D:Acceleration cost and cached volume depend on policy duration; retaining unused history is unnecessary.
Question 248
An external Delta dataset changes schema, and accelerated KQL queries now fail. What metadata action may be needed?
- Treat it as accelerated external Delta access, not full native ingestion.
- Include applicable OneLake premium cache and indexing consumption in the cost model.
- Set a cache duration aligned with the intended recent-data query window.
- Update the external Delta table schema definition and re-evaluate its acceleration policy.
Explanation
Correct Answer
D:External schema metadata must reflect source changes; incompatible schema changes can invalidate or restart acceleration. Inspect the external table schema and acceleration status.
Incorrect Answers
A:Caching improves shortcut query performance but keeps external-table feature limitations and source representation.
B:Acceleration uses cache capacity and may consume CUs for indexing; it is not a zero-cost equivalent of leaving the data uncached.
C:Acceleration cost and cached volume depend on policy duration; retaining unused history is unnecessary.
Question 249
A query acceleration policy caches data for far longer than the actual query lookback, inflating cache cost. What should be tuned?
- Set a cache duration aligned with the intended recent-data query window.
- Update the external Delta table schema definition and re-evaluate its acceleration policy.
- Treat it as accelerated external Delta access, not full native ingestion.
- Optimize source Delta file layout and count where the owning system permits it.
Explanation
Correct Answer
A:Acceleration cost and cached volume depend on policy duration; retaining unused history is unnecessary. Review cached days and cache billing telemetry.
Incorrect Answers
B:External schema metadata must reflect source changes; incompatible schema changes can invalidate or restart acceleration.
C:Caching improves shortcut query performance but keeps external-table feature limitations and source representation.
D:File count and metadata overhead still affect external scan and caching efficiency despite acceleration.
Question 250
An Eventhouse shortcut to a massive Delta table reports acceleration progress unknown. Which command provides diagnostic statistics?
- Optimize source Delta file layout and count where the owning system permits it.
- Update the external Delta table schema definition and re-evaluate its acceleration policy.
- Use the supported external-table query-acceleration statistics command for that table.
- Include applicable OneLake premium cache and indexing consumption in the cost model.
Explanation
Correct Answer
C:Acceleration initialization and cache activity can be monitored explicitly rather than inferred from general query duration. Inspect cache state over time.
Incorrect Answers
A:File count and metadata overhead still affect external scan and caching efficiency despite acceleration.
B:External schema metadata must reflect source changes; incompatible schema changes can invalidate or restart acceleration.
D:Acceleration uses cache capacity and may consume CUs for indexing; it is not a zero-cost equivalent of leaving the data uncached.