100% Latest & Updated Databricks Certified Data Engineer Associate Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 130
A common SaaS application has a vetted managed connector with built-in ingestion state. Which setup step most directly realizes the proposed design?
- Persist cloudFiles.schemaLocation and choose addNewColumns for an inferred source schema.
- Set cloudFiles.schemaEvolutionMode to rescue and keep a rescued-data column.
- Ingest JSON to bronze with controlled schema handling and standardize selected fields in silver.
- Configure the supported connector connection and its governed destination.
Explanation
Correct Answer
D:Configure the supported connector connection and its governed destination. New SaaS source changes appear without custom pagination code.
Incorrect Answers
A:When an Auto Loader JSON feed adds optional fields during the quarter and schema changes must be tracked, “Persist cloudFiles.schemaLocation and choose addNewColumns for an inferred source schema” could be relevant. Configure the supported connector connection and its governed destination.
B:If a regulated feed must retain unexpected JSON attributes without changing the approved table schema, “Set cloudFiles.schemaEvolutionMode to rescue and keep a rescued-data column” may be the appropriate response. Configure the supported connector connection and its governed destination.
C:A telemetry source emits JSON lines with heterogeneous optional keys. In those circumstances, “Ingest JSON to bronze with controlled schema handling and standardize selected fields in silver” fits. Configure the supported connector connection and its governed destination.
Question 131
A common SaaS application has a vetted managed connector with built-in ingestion state. What is the most relevant verification evidence for this case?
- Previously unseen optional keys do not erase the original raw record.
- The unexpected nested key and source path can be inspected in the rescue output.
- Only the intended JSON records are added; unrelated formats are left out.
- New SaaS source changes appear without custom pagination code.
Explanation
Correct Answer
D:New SaaS source changes appear without custom pagination code.
Incorrect Answers
A:If a telemetry source emits JSON lines with heterogeneous optional keys, “Previously unseen optional keys do not erase the original raw record” may be the appropriate response. New SaaS source changes appear without custom pagination code.
B:A JSON source contains additional nested keys that are not part of a strongly typed downstream contract. In those circumstances, “The unexpected nested key and source path can be inspected in the rescue output” fits. New SaaS source changes appear without custom pagination code.
C:When a controlled data import should process only JSON files from a mixed-format landing folder, “Only the intended JSON records are added; unrelated formats are left out” could be relevant. New SaaS source changes appear without custom pagination code.
Question 132
A common SaaS application has a vetted managed connector with built-in ingestion state. The team observes: A token refresh breaks a bespoke nightly API notebook. What is the most likely mechanism behind the observed defect?
- The connector destination was set to the wrong catalog or schema.
- Schema handling was too strict at the raw landing boundary for this variable payload.
- The team used plain INSERT FROM FILES without COPY INTO's loaded-file tracking.
- The team unnecessarily maintained custom API collection instead of using a suitable managed connector.
Explanation
Correct Answer
D:The team unnecessarily maintained custom API collection instead of using a suitable managed connector. Configure the supported connector connection and its governed destination.
Incorrect Answers
A:An audit team needs stable ownership of data ingested from a managed enterprise application. In those circumstances, “The connector destination was set to the wrong catalog or schema” fits. The team unnecessarily maintained custom API collection instead of using a suitable managed connector.
B:When a telemetry source emits JSON lines with heterogeneous optional keys, “Schema handling was too strict at the raw landing boundary for this variable payload” could be relevant. The team unnecessarily maintained custom API collection instead of using a suitable managed connector.
C:If an operations team wants a SQL-only one-time load of historical CSV objects stored in an approved S3 prefix, “The team used plain INSERT FROM FILES without COPY INTO's loaded-file tracking” may be the appropriate response. The team unnecessarily maintained custom API collection instead of using a suitable managed connector.
Question 133
A proprietary application has no native managed connector but a supported third-party integration. Which approach most directly satisfies the requirement?
- Use a supported Lakeflow Connect managed connector for the CRM source.
- Evaluate a governed partner connector compatible with the required source and volume.
- Use Auto Loader schema inference and managed column evolution with restart handling.
- Use null-safe extraction and a stable target schema for optional nested fields.
Explanation
Correct Answer
B:Evaluate a governed partner connector compatible with the required source and volume. Partner-sourced records pass lineage and permission checks in the target.
Incorrect Answers
A:When a CRM administrator wants managed incremental ingestion into governed Databricks tables without writing custom REST pagination, “Use a supported Lakeflow Connect managed connector for the CRM source” could be relevant. Evaluate a governed partner connector compatible with the required source and volume.
C:An Auto Loader JSON feed adds optional fields during the quarter and schema changes must be tracked. In those circumstances, “Use Auto Loader schema inference and managed column evolution with restart handling” fits. Evaluate a governed partner connector compatible with the required source and volume.
D:When a JSON API occasionally omits nested optional customer attributes, “Use null-safe extraction and a stable target schema for optional nested fields” could be relevant. Evaluate a governed partner connector compatible with the required source and volume.
Question 134
A proprietary application has no native managed connector but a supported third-party integration. Which configuration or engineering action would most directly implement the requirement?
- Configure the partner ingestion to land in an approved UC-managed dataset.
- Restore the original checkpointLocation rather than creating an empty path.
- Set up a JDBC client with secret-backed credentials and write results to a UC Delta table.
- Create the connector connection and managed ingestion pipeline with UC destinations.
Explanation
Correct Answer
A:Configure the partner ingestion to land in an approved UC-managed dataset. Partner-sourced records pass lineage and permission checks in the target.
Incorrect Answers
B:A streaming ingestion restarts after maintenance and must continue from its last committed progress. In those circumstances, “Restore the original checkpointLocation rather than creating an empty path” fits. Configure the partner ingestion to land in an approved UC-managed dataset.
C:When a niche on-premises database lacks a supported managed connector but allows JDBC reads, “Set up a JDBC client with secret-backed credentials and write results to a UC Delta table” could be relevant. Configure the partner ingestion to land in an approved UC-managed dataset.
D:If a CRM administrator wants managed incremental ingestion into governed Databricks tables without writing custom REST pagination, “Create the connector connection and managed ingestion pipeline with UC destinations” may be the appropriate response. Configure the partner ingestion to land in an approved UC-managed dataset.
Question 135
A proprietary application has no native managed connector but a supported third-party integration. Which test would establish that the change worked as intended?
- Previously unseen optional keys do not erase the original raw record.
- Partner-sourced records pass lineage and permission checks in the target.
- Only the intended JSON records are added; unrelated formats are left out.
- An order with three items produces three correct item-level silver rows.
Explanation
Correct Answer
B:Partner-sourced records pass lineage and permission checks in the target.
Incorrect Answers
A:A telemetry source emits JSON lines with heterogeneous optional keys. In those circumstances, “Previously unseen optional keys do not erase the original raw record” fits. Partner-sourced records pass lineage and permission checks in the target.
C:If a controlled data import should process only JSON files from a mixed-format landing folder, “Only the intended JSON records are added; unrelated formats are left out” may be the appropriate response. Partner-sourced records pass lineage and permission checks in the target.
D:An order feed supplies JSON objects with nested arrays of items. In those circumstances, “An order with three items produces three correct item-level silver rows” fits. Partner-sourced records pass lineage and permission checks in the target.
Question 136
A proprietary application has no native managed connector but a supported third-party integration. The team observes: An assumed native connector cannot locate the proprietary source type. Which configuration or design gap best explains the symptom?
- The chosen ingestion method does not support this proprietary source.
- A handwritten REST poller was used instead of the supported managed connector.
- The connector destination was set to the wrong catalog or schema.
- The team used plain INSERT FROM FILES without COPY INTO's loaded-file tracking.
Explanation
Correct Answer
A:The chosen ingestion method does not support this proprietary source. Configure the partner ingestion to land in an approved UC-managed dataset.
Incorrect Answers
B:If a CRM administrator wants managed incremental ingestion into governed Databricks tables without writing custom REST pagination, “A handwritten REST poller was used instead of the supported managed connector” may be the appropriate response. The chosen ingestion method does not support this proprietary source.
C:An audit team needs stable ownership of data ingested from a managed enterprise application. In those circumstances, “The connector destination was set to the wrong catalog or schema” fits. The chosen ingestion method does not support this proprietary source.
D:When an operations team wants a SQL-only one-time load of historical CSV objects stored in an approved S3 prefix, “The team used plain INSERT FROM FILES without COPY INTO's loaded-file tracking” could be relevant. The chosen ingestion method does not support this proprietary source.
Question 137
A static set of archive files must be loaded once through SQL with minimal pipeline machinery. Which architecture or engineering decision best fits this scenario?
- Maintain an explicit schema location as well as stream progress storage.
- Choose COPY INTO for a simple repeatable bulk import.
- Use Auto Loader rescue mode for unforeseen fields.
- Use Auto Loader schema inference and managed column evolution with restart handling.
Explanation
Correct Answer
B:Choose COPY INTO for a simple repeatable bulk import. Reruns skip already processed files while added archive files can be loaded.
Incorrect Answers
A:If an Auto Loader job reads many new files and needs to persist inferred schema changes independently of checkpoints, “Maintain an explicit schema location as well as stream progress storage” may be the appropriate response. Choose COPY INTO for a simple repeatable bulk import.
C:When a regulated feed must retain unexpected JSON attributes without changing the approved table schema, “Use Auto Loader rescue mode for unforeseen fields” could be relevant. Choose COPY INTO for a simple repeatable bulk import.
D:If an Auto Loader JSON feed adds optional fields during the quarter and schema changes must be tracked, “Use Auto Loader schema inference and managed column evolution with restart handling” may be the appropriate response. Choose COPY INTO for a simple repeatable bulk import.
Question 138
A static set of archive files must be loaded once through SQL with minimal pipeline machinery. Which implementation step is most appropriate before production use?
- Run COPY INTO with a source location and explicit file format against the governed table.
- Configure cloudFiles.schemaLocation separately from the stream checkpointLocation.
- Set up a JDBC client with secret-backed credentials and write results to a UC Delta table.
- Configure a one-time COPY INTO statement against the approved Delta table.
Explanation
Correct Answer
D:Configure a one-time COPY INTO statement against the approved Delta table. Reruns skip already processed files while added archive files can be loaded.
Incorrect Answers
A:An operations team wants a SQL-only one-time load of historical CSV objects stored in an approved S3 prefix. In those circumstances, “Run COPY INTO with a source location and explicit file format against the governed table” fits. Configure a one-time COPY INTO statement against the approved Delta table.
B:When an Auto Loader job reads many new files and needs to persist inferred schema changes independently of checkpoints, “Configure cloudFiles.schemaLocation separately from the stream checkpointLocation” could be relevant. Configure a one-time COPY INTO statement against the approved Delta table.
C:If a niche on-premises database lacks a supported managed connector but allows JDBC reads, “Set up a JDBC client with secret-backed credentials and write results to a UC Delta table” may be the appropriate response. Configure a one-time COPY INTO statement against the approved Delta table.
Question 139
A static set of archive files must be loaded once through SQL with minimal pipeline machinery. Which acceptance test provides the strongest evidence that the intended outcome has been achieved?
- Reruns skip already processed files while added archive files can be loaded.
- All pages are ingested once and a rate-limit response is retried safely.
- A delayed source event retains its original business event time in the bronze record.
- Only the intended JSON records are added; unrelated formats are left out.
Explanation
Correct Answer
A:Reruns skip already processed files while added archive files can be loaded.
Incorrect Answers
B:If an external service exposes a paginated REST endpoint with rate limits and no managed connector, “All pages are ingested once and a rate-limit response is retried safely” may be the appropriate response. Reruns skip already processed files while added archive files can be loaded.
C:A vendor's data source sends records with event timestamps older than ingestion time. In those circumstances, “A delayed source event retains its original business event time in the bronze record” fits. Reruns skip already processed files while added archive files can be loaded.
D:When a controlled data import should process only JSON files from a mixed-format landing folder, “Only the intended JSON records are added; unrelated formats are left out” could be relevant. Reruns skip already processed files while added archive files can be loaded.
Question 140
A static set of archive files must be loaded once through SQL with minimal pipeline machinery. The team observes: A streaming cluster runs indefinitely after the one-time archive import. Which root cause should be addressed first given this evidence?
- The managed ingestion schedule or ongoing sync was never activated.
- The COPY INTO source selection did not restrict ingestion to JSON input.
- The pipeline appended update records without matching them to existing keys.
- A continuously active stream was chosen for an essentially one-off load.
Explanation
Correct Answer
D:A continuously active stream was chosen for an essentially one-off load. Configure a one-time COPY INTO statement against the approved Delta table.
Incorrect Answers
A:If a managed enterprise-source ingestion has an initial backfill followed by periodic change updates, “The managed ingestion schedule or ongoing sync was never activated” may be the appropriate response. A continuously active stream was chosen for an essentially one-off load.
B:A controlled data import should process only JSON files from a mixed-format landing folder. In those circumstances, “The COPY INTO source selection did not restrict ingestion to JSON input” fits. A continuously active stream was chosen for an essentially one-off load.
C:When a partner publishes corrected records with stable business keys in each incremental delivery, “The pipeline appended update records without matching them to existing keys” could be relevant. A continuously active stream was chosen for an essentially one-off load.
Certified Data Engineer Associate Practice Tests