Exam Certified Data Engineer Professional All Questions

View all questions & answers for the Certified Data Engineer Professional exam

Exam Certified Data Engineer Professional topic 1 question 219 discussion

Actual exam question from Databricks's Certified Data Engineer Professional

Question #: 219
Topic #: 1

[All Certified Data Engineer Professional Questions]

A user new to Databricks is trying to troubleshoot long execution times for some pipeline logic they are working on. Presently, the user is executing code cell-by-cell, using display() calls to confirm code is producing the logically correct results as new transformations are added to an operation. To get a measure of average time to execute, the user is running each cell multiple times interactively.

Which of the following adjustments will get a more accurate measure of how code is likely to perform in production?

A. 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.
B. 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.
C. 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.
D. 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.

Show Suggested Answer

Suggested Answer: B 🗳️

by Bishal at Dec. 28, 2024, 2:09 p.m.

Comments

Submit Cancel

c315d10

3 weeks ago

Selected Answer: D

production data in reality is not used for development testing

upvoted 1 times

...

KadELbied

1 month, 1 week ago

Selected Answer: B

suretly B

upvoted 1 times

...

kishanu

2 months, 1 week ago

Selected Answer: D

Using display() will force the job to trigger and hence won't be tested as per production

upvoted 1 times

...

kishanu

2 months, 1 week ago

Selected Answer: D

Using display() will force the job to trigger and hence won't be tested as per production

upvoted 1 times

...

suranga4

2 months, 3 weeks ago

Selected Answer: B

B is the right answer

upvoted 1 times

...

mohadjhamad

3 months ago

Selected Answer: D

Calling display() forces a job to trigger,

upvoted 1 times

...

mouthwash

5 months, 1 week ago

Selected Answer: B

B is the right answer.

upvoted 1 times

...

arekm

5 months, 2 weeks ago

Selected Answer: B

B - this is a repeated question. You need production like data & environment to be able to troubleshoot the performance issues. display() does introduce overhead, but we use it here to investigate, where the problems start to surface. We still need the production like env and data first.

upvoted 1 times

...