100% Latest & Updated Databricks Certified Data Engineer Associate Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 150
A JSON API occasionally omits nested optional customer attributes. Which configuration or engineering action would most directly implement the requirement?
- Configure schema rescue and inspect _rescued_data for the source record.
- Implement cursor handling, throttling backoff, and idempotent writes to the bronze table.
- Parse nested keys with supported accessors and apply an explicit missing-value rule.
- Create the connector connection and managed ingestion pipeline with UC destinations.
Explanation
Correct Answer
C:Parse nested keys with supported accessors and apply an explicit missing-value rule. Records without optional values still load while mandatory fields are validated.
Incorrect Answers
A:A JSON source contains additional nested keys that are not part of a strongly typed downstream contract. In those circumstances, “Configure schema rescue and inspect _rescued_data for the source record” fits. Parse nested keys with supported accessors and apply an explicit missing-value rule.
B:When an external service exposes a paginated REST endpoint with rate limits and no managed connector, “Implement cursor handling, throttling backoff, and idempotent writes to the bronze table” could be relevant. Parse nested keys with supported accessors and apply an explicit missing-value rule.
D:A CRM administrator wants managed incremental ingestion into governed Databricks tables without writing custom REST pagination. In those circumstances, “Create the connector connection and managed ingestion pipeline with UC destinations” fits. Parse nested keys with supported accessors and apply an explicit missing-value rule.
Question 151
A JSON API occasionally omits nested optional customer attributes. Which test would establish that the change worked as intended?
- A corrected key changes its existing target row without creating another active duplicate.
- Records without optional values still load while mandatory fields are validated.
- The ingested tables are discoverable under the approved UC namespace and grants.
- Re-executing the same COPY INTO statement does not reload already tracked unchanged source files.
Explanation
Correct Answer
B:Records without optional values still load while mandatory fields are validated.
Incorrect Answers
A:When a partner publishes corrected records with stable business keys in each incremental delivery, “A corrected key changes its existing target row without creating another active duplicate” could be relevant. Records without optional values still load while mandatory fields are validated.
C:An audit team needs stable ownership of data ingested from a managed enterprise application. In those circumstances, “The ingested tables are discoverable under the approved UC namespace and grants” fits. Records without optional values still load while mandatory fields are validated.
D:When an operations team wants a SQL-only one-time load of historical CSV objects stored in an approved S3 prefix, “Re-executing the same COPY INTO statement does not reload already tracked unchanged source files” could be relevant. Records without optional values still load while mandatory fields are validated.
Question 152
A JSON API occasionally omits nested optional customer attributes. The team observes: Records lacking an optional nickname fail the whole ingestion batch. Which configuration or design gap best explains the symptom?
- The transformation treated a nonessential nested field as mandatory.
- The run started without a reliable completion signal for the monthly export.
- The pipeline uses a scheduled batch job instead of a streaming ingestion path.
- The connector destination was set to the wrong catalog or schema.
Explanation
Correct Answer
A:The transformation treated a nonessential nested field as mandatory. Parse nested keys with supported accessors and apply an explicit missing-value rule.
Incorrect Answers
B:A finance feed is delivered as one vetted CSV export at the end of each month. In those circumstances, “The run started without a reliable completion signal for the monthly export” fits. The transformation treated a nonessential nested field as mandatory.
C:When a fraud scoring table must incorporate arriving events with low latency rather than waiting for nightly files, “The pipeline uses a scheduled batch job instead of a streaming ingestion path” could be relevant. The transformation treated a nonessential nested field as mandatory.
D:If an audit team needs stable ownership of data ingested from a managed enterprise application, “The connector destination was set to the wrong catalog or schema” may be the appropriate response. The transformation treated a nonessential nested field as mandatory.
Question 153
An application exports documents plus metadata into object storage. Which architecture or engineering decision best fits this scenario?
- Choose a managed connector workflow supporting an initial snapshot and subsequent sync.
- Keep binary or text document payloads linked to their metadata in governed bronze records.
- Use a bounded REST extraction in a scheduled notebook with explicit pagination and retry handling.
- Constrain the COPY INTO format and source-file selection to the intended JSON dataset.
Explanation
Correct Answer
B:Keep binary or text document payloads linked to their metadata in governed bronze records. The downstream record can trace each document to its source file and metadata.
Incorrect Answers
A:A managed enterprise-source ingestion has an initial backfill followed by periodic change updates. In those circumstances, “Choose a managed connector workflow supporting an initial snapshot and subsequent sync” fits. Keep binary or text document payloads linked to their metadata in governed bronze records.
C:If an external service exposes a paginated REST endpoint with rate limits and no managed connector, “Use a bounded REST extraction in a scheduled notebook with explicit pagination and retry handling” may be the appropriate response. Keep binary or text document payloads linked to their metadata in governed bronze records.
D:A controlled data import should process only JSON files from a mixed-format landing folder. In those circumstances, “Constrain the COPY INTO format and source-file selection to the intended JSON dataset” fits. Keep binary or text document payloads linked to their metadata in governed bronze records.
Question 154
An application exports documents plus metadata into object storage. Which implementation step is most appropriate before production use?
- Use a supported binary-file or text ingestion source and persist content identifiers.
- Configure a one-time COPY INTO statement against the approved Delta table.
- Restore the original checkpointLocation rather than creating an empty path.
- Use Auto Loader discovery and a durable progress checkpoint for incremental processing.
Explanation
Correct Answer
A:Use a supported binary-file or text ingestion source and persist content identifiers. The downstream record can trace each document to its source file and metadata.
Incorrect Answers
B:If a static set of archive files must be loaded once through SQL with minimal pipeline machinery, “Configure a one-time COPY INTO statement against the approved Delta table” may be the appropriate response. Use a supported binary-file or text ingestion source and persist content identifiers.
C: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. Use a supported binary-file or text ingestion source and persist content identifiers.
D:When a large object-store drop includes millions of files with continual arrivals, “Use Auto Loader discovery and a durable progress checkpoint for incremental processing” could be relevant. Use a supported binary-file or text ingestion source and persist content identifiers.
Question 155
An application exports documents plus metadata into object storage. Which acceptance test provides the strongest evidence that the intended outcome has been achieved?
- The downstream record can trace each document to its source file and metadata.
- The connector can enumerate and ingest the selected ERP objects without broader rights.
- Reruns skip already processed files while added archive files can be loaded.
- Historical rows appear first and later changes are reflected without full custom reimports.
Explanation
Correct Answer
A:The downstream record can trace each document to its source file and metadata.
Incorrect Answers
B:An ERP table is replicated through a managed connector but its ingestion account lacks read access. In those circumstances, “The connector can enumerate and ingest the selected ERP objects without broader rights” fits. The downstream record can trace each document to its source file and metadata.
C:When a static set of archive files must be loaded once through SQL with minimal pipeline machinery, “Reruns skip already processed files while added archive files can be loaded” could be relevant. The downstream record can trace each document to its source file and metadata.
D:If a managed enterprise-source ingestion has an initial backfill followed by periodic change updates, “Historical rows appear first and later changes are reflected without full custom reimports” may be the appropriate response. The downstream record can trace each document to its source file and metadata.
Question 156
An application exports documents plus metadata into object storage. The team observes: Documents arrive without any resolvable source path or identifier. Which root cause should be addressed first given this evidence?
- The COPY INTO source selection did not restrict ingestion to JSON input.
- The ingestion discarded the file provenance needed to link content and metadata.
- The job never persisted the inferred schema to a stable schema location.
- The destination was an unqualified legacy table, not the required UC namespace.
Explanation
Correct Answer
B:The ingestion discarded the file provenance needed to link content and metadata. Use a supported binary-file or text ingestion source and persist content identifiers.
Incorrect Answers
A: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. The ingestion discarded the file provenance needed to link content and metadata.
C:If an Auto Loader job reads many new files and needs to persist inferred schema changes independently of checkpoints, “The job never persisted the inferred schema to a stable schema location” may be the appropriate response. The ingestion discarded the file provenance needed to link content and metadata.
D:A platform team must load raw cloud files to a three-part Unity Catalog table using SQL. In those circumstances, “The destination was an unqualified legacy table, not the required UC namespace” fits. The ingestion discarded the file provenance needed to link content and metadata.
Question 157
A telemetry source emits JSON lines with heterogeneous optional keys. Which technical design is most appropriate for the stated constraint?
- Land raw semi-structured records before enforcing the stable analytics projection.
- Prefer Auto Loader over a repeated full-directory file scan.
- Use a continuously updating Structured Streaming ingestion pattern.
- Use a scheduled batch ingestion job aligned with the monthly delivery.
Explanation
Correct Answer
A:Land raw semi-structured records before enforcing the stable analytics projection. Previously unseen optional keys do not erase the original raw record.
Incorrect Answers
B:If a large object-store drop includes millions of files with continual arrivals, “Prefer Auto Loader over a repeated full-directory file scan” may be the appropriate response. Land raw semi-structured records before enforcing the stable analytics projection.
C:A fraud scoring table must incorporate arriving events with low latency rather than waiting for nightly files. In those circumstances, “Use a continuously updating Structured Streaming ingestion pattern” fits. Land raw semi-structured records before enforcing the stable analytics projection.
D:When a finance feed is delivered as one vetted CSV export at the end of each month, “Use a scheduled batch ingestion job aligned with the monthly delivery” could be relevant. Land raw semi-structured records before enforcing the stable analytics projection.
Question 158
A telemetry source emits JSON lines with heterogeneous optional keys. Which action should the engineer perform to establish the intended control?
- Configure the supported connector pipeline and its schedule or update cadence.
- Create the connector connection and managed ingestion pipeline with UC destinations.
- Ingest JSON to bronze with controlled schema handling and standardize selected fields in silver.
- Persist cloudFiles.schemaLocation and choose addNewColumns for an inferred source schema.
Explanation
Correct Answer
C:Ingest JSON to bronze with controlled schema handling and standardize selected fields in silver. Previously unseen optional keys do not erase the original raw record.
Incorrect Answers
A:If a managed enterprise-source ingestion has an initial backfill followed by periodic change updates, “Configure the supported connector pipeline and its schedule or update cadence” may be the appropriate response. Ingest JSON to bronze with controlled schema handling and standardize selected fields in silver.
B:A CRM administrator wants managed incremental ingestion into governed Databricks tables without writing custom REST pagination. In those circumstances, “Create the connector connection and managed ingestion pipeline with UC destinations” fits. Ingest JSON to bronze with controlled schema handling and standardize selected fields in silver.
D:If 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” may be the appropriate response. Ingest JSON to bronze with controlled schema handling and standardize selected fields in silver.
Question 159
A telemetry source emits JSON lines with heterogeneous optional keys. Which observation best proves the workload meets its requirement?
- Previously unseen optional keys do not erase the original raw record.
- A newly arriving object is processed while previously checkpointed objects are not redundantly ingested.
- After the controlled restart the new column appears in the schema and rows are processed.
- The stream stops for an unapproved added column until the schema is updated.
Explanation
Correct Answer
A:Previously unseen optional keys do not erase the original raw record.
Incorrect Answers
B:When a point-of-sale system publishes a new immutable object-store file every five minutes, “A newly arriving object is processed while previously checkpointed objects are not redundantly ingested” could be relevant. Previously unseen optional keys do not erase the original raw record.
C:If an Auto Loader JSON feed adds optional fields during the quarter and schema changes must be tracked, “After the controlled restart the new column appears in the schema and rows are processed” may be the appropriate response. Previously unseen optional keys do not erase the original raw record.
D:A customer source cannot accept newly introduced columns without explicit schema approval. In those circumstances, “The stream stops for an unapproved added column until the schema is updated” fits. Previously unseen optional keys do not erase the original raw record.
Question 160
A telemetry source emits JSON lines with heterogeneous optional keys. The team observes: A new optional property prevents all valid records from loading. Which underlying cause most directly explains this failure?
- A naive batch file scan was chosen instead of incremental Auto Loader discovery.
- The connector destination was set to the wrong catalog or schema.
- A continuously active stream was chosen for an essentially one-off load.
- Schema handling was too strict at the raw landing boundary for this variable payload.
Explanation
Correct Answer
D:Schema handling was too strict at the raw landing boundary for this variable payload. Ingest JSON to bronze with controlled schema handling and standardize selected fields in silver.
Incorrect Answers
A:When a large object-store drop includes millions of files with continual arrivals, “A naive batch file scan was chosen instead of incremental Auto Loader discovery” could be relevant. Schema handling was too strict at the raw landing boundary for this variable payload.
B:If an audit team needs stable ownership of data ingested from a managed enterprise application, “The connector destination was set to the wrong catalog or schema” may be the appropriate response. Schema handling was too strict at the raw landing boundary for this variable payload.
C:A static set of archive files must be loaded once through SQL with minimal pipeline machinery. In those circumstances, “A continuously active stream was chosen for an essentially one-off load” fits. Schema handling was too strict at the raw landing boundary for this variable payload.
Certified Data Engineer Associate Practice Tests