Databricks Databricks-Certified-Professional-Data-Engineer Exam Dumps

All records from an Apache Kafka producer are being ingested into a single Delta Lake table with the following schema: key BINARY, value BINARY, topic STRING, partition LONG, offset LONG, timestamp LONG There are 5 unique topics being ingested. Only the "registration" topic contains Personal Identifiable Information (PII). The company wishes to restrict access to PII. The company also wishes to only retain records containing PII in this table for 14 days after initial ingestion. However, for non-PII information, it would like to retain these records indefinitely. Which of the following solutions meets the requirements? 

A. All data should be deleted biweekly; Delta Lake's time travel functionality should be leveraged to maintain a history of non-PII information. 
B. Data should be partitioned by the registration field, allowing ACLs and delete statements to be set for the PII directory. 
C. Because the value field is stored as binary data, this information is not considered PII and no special precautions should be taken. 
D. Separate object storage containers should be specified based on the partition field, allowing isolation at the storage level. 
E. Data should be partitioned by the topic field, allowing ACLs and delete statements to leverage partition boundaries. 

Answer: B

Each configuration below is identical to the extent that each cluster has 400 GB total of RAM, 160 total cores and only one Executor per VM. Given a job with at least one wide transformation, which of the following cluster configurations will result in maximum performance? 

A. • Total VMs; 1 • 400 GB per Executor • 160 Cores / Executor 
B. • Total VMs: 8 • 50 GB per Executor • 20 Cores / Executor 
C. • Total VMs: 4 • 100 GB per Executor • 40 Cores/Executor 
D. • Total VMs:2 • 200 GB per Executor • 80 Cores / Executor 

Answer: B

A new data engineer notices that a critical field was omitted from an application that writes its Kafka source to Delta Lake. This happened even though the critical field was in the Kafka source. That field was further missing from data written to dependent, long-term storage. The retention threshold on the Kafka service is seven days. The pipeline has been in production for three months. Which describes how Delta Lake can help to avoid data loss of this nature in the future?

A. The Delta log and Structured Streaming checkpoints record the full history of the Kafka  producer. 
B. Delta Lake schema evolution can retroactively calculate the correct value for newly added fields, as long as the data was in the original source. 
C. Delta Lake automatically checks that all fields present in the source data are included in the ingestion layer. 
D. Data can never be permanently dropped or deleted from Delta Lake, so data loss is not possible under any circumstance. 
E. Ingestine all raw data and metadata from Kafka to a bronze Delta table creates a permanent, replayable history of the data state. 

Answer: E

Which statement describes Delta Lake Auto Compaction?

 A. An asynchronous job runs after the write completes to detect if files could be further compacted; if yes, an optimize job is executed toward a default of 1 GB. 
B. Before a Jobs cluster terminates, optimize is executed on all tables modified during the most recent job. 
C. Optimized writes use logical partitions instead of directory partitions; because partition boundaries are only represented in metadata, fewer small files are written. 
D. Data is queued in a messaging bus instead of committing data directly to memory; all data is committed from the messaging bus in one batch once the job is complete. 
E. An asynchronous job runs after the write completes to detect if files could be further compacted; if yes, an optimize job is executed toward a default of 128 MB. 

Answer: E

The view updates represents an incremental batch of all newly ingested data to be inserted or updated in the customers table. The following logic is used to process these records. MERGE INTO customers USING ( SELECT updates.customer_id as merge_ey, updates .* FROM updates UNION ALL SELECT NULL as merge_key, updates .* FROM updates JOIN customers ON updates.customer_id = customers.customer_id WHERE customers.current = true AND updates.address <> customers.address ) staged_updates ON customers.customer_id = mergekey WHEN MATCHED AND customers. current = true AND customers.address <> staged_updates.address THEN UPDATE SET current = false, end_date = staged_updates.effective_date WHEN NOT MATCHED THEN INSERT (customer_id, address, current, effective_date, end_date) VALUES (staged_updates.customer_id, staged_updates.address, true, staged_updates.effective_date, null) Which statement describes this implementation? 

A. The customers table is implemented as a Type 2 table; old values are overwritten and new customers are appended. 
B. The customers table is implemented as a Type 1 table; old values are overwritten by new values and no history is maintained. 
C. The customers table is implemented as a Type 2 table; old values are maintained but marked as no longer current and new values are inserted. 
D. The customers table is implemented as a Type 0 table; all writes are append only with no changes to existing values. 

Answer: C