Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Databricks Certified Data Engineer Associate Exam - Topic 3 Question 50 Discussion

Actual exam question for Databricks's Databricks Certified Data Engineer Associate exam
Question #: 50
Topic #: 3
[All Databricks Certified Data Engineer Associate Questions]

A data analyst has a series of queries in a SQL program. The data analyst wants this program to run every day. They only want the final query in the program to run on Sundays. They ask for help from the data engineering team to complete this task.

Which of the following approaches could be used by the data engineering team to complete this task?

Show Suggested Answer Hide Answer
Suggested Answer: B

This approach would allow the data engineering team to use the existing SQL program and add some logic to control the execution of the final query based on the day of the week. They could use thedatetimemodule in Python to get the current date and check if it is a Sunday. If so, they could run the final query, otherwise they could skip it. This way, they could schedule the program to run every day without changing the data model or the source table.Reference:PySpark SQL Module,Python datetime Module,Databricks Jobs


by Rebbeca at Jun 16, 2025, 10:07 PM

Limited Time Offer

25%

Off

Get Premium Databricks Certified Data Engineer Associate Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Rossana
5 months ago
I agree, option E could work but might be unnecessary.
upvoted 0 times
...
Lashanda
5 months ago
Option D seems overly complicated for this task.
upvoted 0 times
...
Hoa
5 months ago
Surprised they can't just schedule the final query separately!
upvoted 0 times
...
Sunshine
6 months ago
I think option C is too limiting.
upvoted 0 times
...
Krissy
6 months ago
Option B sounds like a solid plan!
upvoted 0 times
...
Fanny
6 months ago
I vaguely remember something about separating data into different tables, so option E might be a valid approach, but it feels like overkill for just one query.
upvoted 0 times
...
Jose
6 months ago
Option A seems like a long shot; I don't think submitting a feature request is practical for this situation.
upvoted 0 times
...
Lorrine
7 months ago
I think option C is too limiting since they want the program to run daily, but I can't recall if there's a way to schedule specific queries differently.
upvoted 0 times
...
Galen
7 months ago
I remember something about using control flow in Python, so option B sounds familiar, but I'm not entirely sure how it would work with SQL.
upvoted 0 times
...
Oretha
7 months ago
I'm leaning towards option B as well. Using Python's control flow to determine when to run the final query seems like a flexible and efficient way to handle this requirement.
upvoted 0 times
...
Yuonne
7 months ago
I think option E, redesigning the data model to separate the data used in the final query into a new table, could be a good long-term solution. It would make the program more modular and easier to maintain.
upvoted 0 times
...
Barrett
7 months ago
Hmm, I'm not sure I fully understand the requirements here. Is there a way to automatically restrict access to the source table in the final query so that it's only accessible on Sundays, as mentioned in option D? That could be an interesting approach to explore.
upvoted 0 times
...
Gilma
8 months ago
I'm a bit confused by this question. It's not clear to me why we can't just run the entire program on Sundays, as suggested in option C. That seems like the simplest solution.
upvoted 0 times
...
Linwood
8 months ago
This seems like a straightforward problem. I think the best approach would be to use Python's control flow system to determine when to run the final query, as described in option B.
upvoted 0 times
...
Lizbeth
10 months ago
Choosing option A would be like asking the janitor to fix the plumbing. Databricks is for data processing, not scheduling tasks.
upvoted 0 times
...
Adell
10 months ago
Wow, option D is really creative. Restricting access to the source table is a clever way to achieve the desired result. I wonder if it would work in a real-world scenario, though.
upvoted 0 times
Maynard
10 months ago
User 2: Yeah, it's definitely a unique approach. I'm curious to see if it would actually work seamlessly.
upvoted 0 times
...
Fredric
10 months ago
User 1: Option D does sound interesting. I wonder how effective it would be in practice.
upvoted 0 times
...
...
Reuben
11 months ago
Option C is just lazy. If the client wants the final query to run only on Sundays, we should find a way to make that happen without running the entire program on Sundays.
upvoted 0 times
Pearline
10 months ago
A: Exactly, we need to find a solution that meets the client's requirements without being lazy.
upvoted 0 times
...
Freeman
10 months ago
B: I agree. That way we can ensure the final query runs only on Sundays without running the entire program.
upvoted 0 times
...
Nathalie
11 months ago
A: I think option B is the best approach. We can use Python's control flow system to determine when to run the final query.
upvoted 0 times
...
...
Erinn
11 months ago
I would go with option E. Redesigning the data model to separate the data used in the final query seems like a more robust and maintainable approach.
upvoted 0 times
Alberto
11 months ago
I agree, redesigning the data model could definitely help in the long run.
upvoted 0 times
...
Larae
11 months ago
Option E sounds like a good idea. It would make the process more efficient.
upvoted 0 times
...
...
Wenona
11 months ago
I prefer option E, redesigning the data model seems like a more permanent solution.
upvoted 0 times
...
Josefa
11 months ago
I agree with Cherilyn, using PySpark and Python's control flow system gives more flexibility.
upvoted 0 times
...
Cherilyn
11 months ago
I think option B is the best approach.
upvoted 0 times
...
Hermila
11 months ago
Option B makes the most sense to me. Using Python's control flow to determine when to run the final query is a flexible and efficient solution.
upvoted 0 times
Lenna
10 months ago
Let's go ahead and implement this solution then. It seems like the best option for our needs.
upvoted 0 times
...
Barney
10 months ago
I think it would make the process more efficient and easier to manage in the long run.
upvoted 0 times
...
Loise
11 months ago
It's definitely a more dynamic approach compared to just running the entire program on Sundays.
upvoted 0 times
...
Lenna
11 months ago
I agree, using PySpark and Python's control flow system gives us more control over when to run the final query.
upvoted 0 times
...
...

Save Cancel