Identify Trends in Job Performance Using the Lakeflow Jobs Run History View to Compare Current Execution Times Against Historical Baselines. DATA-ENGINEER-ASSOCIATE Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A team notices that a job's execution time has been decreasing over the past week. The data volume has been constant. What is the most likely explanation for this improvement?

   • AThe team optimized the job's Spark query or added a better file layout.
   • BThe cluster was downsized, making the job run faster.
   • CThe job's schedule was changed to run less frequently.
   • DThe job is now failing earlier in the process, so it takes less time.
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A team monitors a monthly financial reporting job. In the run history view, they notice that for the last three months, the execution time has been 55, 58, and 62 minutes respectively, while the previous six months were consistently around 50 minutes. The data volume has grown by 5% each month. What is the most likely conclusion based on this trend?

   • AThe job is failing intermittently and retrying, which inflates the execution time.
   • BThe job's schedule was changed to run less frequently, causing longer runtimes.
   • CThe job is experiencing a gradual performance degradation that may require investigation.
   • DThe job is performing as expected because data volume increases naturally lead to longer runtimes.
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A data engineering team runs a nightly batch job that processes sales data. Over the past week, the job's execution time has grown from 25 minutes to 40 minutes, while the data volume has remained constant. The team needs to determine whether this is a gradual degradation or a sudden spike. Which action in the Lakeflow Jobs run history view would best help them make this determination?

   • AOpen the most recent run's logs and look for error messages that might explain the longer execution time.
   • BFilter the run history to show only the last 7 runs and compare each run's duration to the historical average displayed in the view.
   • CReview the job's schedule settings to confirm the nightly trigger is still firing at the expected time.
   • DCheck the job's cluster configuration to see if the instance type was changed recently.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   A user wants to view the run history for a specific job they have access to. What is the first step in the Lakeflow Jobs UI?

   • ANavigate to the 'Compute' page and select the job's cluster.
   • BOpen the 'Workflows' page and click on the 'Runs' tab at the top.
   • CClick the 'Create Job' button to start a new run.
   • DSelect the job from the list of jobs on the Jobs page.
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   A data engineer wants to determine if the latest run of a job is slower than usual. What should they compare the current execution time against?

   • AThe execution time of the first run ever
   • BThe execution time of the most recent successful run only
   • CThe execution time of the fastest run
   • DThe historical average or trend of execution times
   Reveal Solution Discussion Select an answer first