Certified Data Engineer Professional Practice Test

Certified Data Engineer Professional Practice Test practice questions, page 10 of 14, with answer review and explanations.

Question 46

Although the Databricks Utilities Secrets module provides tools to store sensitive credentials and avoid accidentally displaying them in plain text users should still be careful with which credentials are stored here and which users have access to using these secrets. Which statement describes a limitation of Databricks Secrets?

Because the SHA256 hash is used to obfuscate stored secrets, reversing this hash will display the value in plain text.
Account administrators can see all secrets in plain text by logging on to the Databricks Accounts console.
Secrets are stored in an administrators-only table within the Hive Metastore; database administrators have permission to query this table by default.
Iterating through a stored secret and printing each character will display secret contents in plain text.
The Databricks REST API can be used to list secrets in plain text if the personal access token has proper credentials.

Question 47

It is retained until you export or delete job run logs
It is retained for 30 days, during which time you can deliver job run logs to DBFS or S3
It is retained for 60 days, during which you can export notebook run results to HTML
It is retained for 60 days, after which logs are archived
It is retained for 90 days or until the run-id is re-used through custom run configuration

Question 48

Because the REST API was used for job creation and triggering runs, a Service Principal will be automatically used to identify these events.
Because User B last configured the jobs, their identity will be associated with both the job creation events and the job run events.
Because these events are managed separately, User A will have their identity associated with the job creation events and User B will have their identity associated with the job run events.
Because the REST API was used for job creation and triggering runs, user identity will not be captured in the audit logs.
Because User A created the jobs, their identity will be associated with both the job creation events and the job run events.

Question 49

Scala is the only language that can be accurately tested using interactive notebooks; because the best performance is achieved by using Scala code compiled to JARs, all PySpark and Spark SQL logic should be refactored.
The only way to meaningfully troubleshoot code execution times in development notebooks Is to use production-sized data and production-sized clusters with Run All execution.
Production code development should only be done using an IDE; executing code against a local build of open source Spark and Delta Lake will provide the most accurate benchmarks for how code will perform in production.
Calling display() forces a job to trigger, while many transformations will only add to the logical query plan; because of caching, repeated execution of the same logic does not provide meaningful results.
The Jobs UI should be leveraged to occasionally run the notebook as a job and track execution time during incremental code development because Photon can only be enabled on clusters launched for scheduled jobs.

Question 50