MENU
How is the change of local time due to daylight savings time handled in Snowflake tasks? (Choose two.)
Suggested Answer: D
Get Premium ARA-R01 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
When a new table (table_6) is added to a schema in the provider's account that is part of a data share, the consumer will not automatically see the new table. The consumer will only be able to access the new table once the appropriate privileges are granted by the provider. The correct process, as outlined in option D, involves using the provider's ACCOUNTADMIN role to grant USAGE privileges on the database and schema, followed by SELECT privileges on the new table, specifically to the share that includes the consumer's database. This ensures that the consumer account can access the new table under the established data sharing setup. Reference:
Snowflake Documentation on Managing Access Control
Snowflake Documentation on Data Sharing
32 comments · newest first
LE
Lettie
11 months ago
E seems a bit harsh, can a task really just fail like that?
PA
Paz
11 months ago
D is interesting, but I think it’s more about the task history than execution.
CR
Cristina
11 months ago
Wait, C? That sounds off. Are you sure?
MA
Marjory
11 months ago
I agree, B is definitely true too.
VE
Verda
11 months ago
A tasks in UTC are totally fine with time changes!
BA
Barrett
12 months ago
I practiced a question similar to this, and I think option E is tricky because it mentions failing to handle lost hours, which seems plausible.
CA
Cammy
12 months ago
I vaguely recall something about tasks getting suspended during the time change, but I'm not sure if that's accurate. Maybe option C?
TO
Tom
12 months ago
I'm a bit unsure, but I think tasks can be set to local time zones to handle daylight savings. That sounds like option B.
KA
Kate
1 year ago
I remember that UTC schedules shouldn't have issues with daylight savings, so I think option A might be correct.
MA
Mammie
1 year ago
The best approach here is to think about how the task schedules are defined. If they're based on UTC, that should avoid any issues with daylight savings time changes.
KA
Katheryn
1 year ago
I'm a bit confused on this one. I'll need to review the documentation to make sure I understand the different options for handling time changes in Snowflake tasks.
MA
Maryann
1 year ago
Ah, I've seen this type of question before. I'm pretty confident I know how Snowflake deals with daylight savings time changes in tasks.
AL
Alverta
1 year ago
Okay, let's see. I think the key is understanding how the task schedules work in Snowflake. I'll need to review the options carefully.
GR
Gracia
1 year ago
Hmm, this seems like a tricky one. I'll need to think carefully about how Snowflake handles daylight savings time changes.
LA
Lawrence
1 year ago
I'm a bit confused by the question. Can the @Future annotation really help with query performance?
FA
Fanny
1 year ago
Okay, I think I've got a strategy here. The question is asking about the independent variable in the cost equation, so I need to identify which variable is driving the changes in maintenance cost. Patient days seems to be the logical choice based on the data provided.
DE
Desiree
1 year ago
I'm going with A and B. Gotta love that Snowflake flexibility when it comes to time zones and daylight savings. No need to stress about the clocks changing.
YA
Yasuko
1 year ago
Noble: No problem, Snowflake has us covered when it comes to time zones and daylight savings.
LA
Lashawna
1 year ago
User 3: I think I'll stick with A and B too, thanks for the tip!
NO
Noble
1 year ago
User 2: Definitely, Snowflake makes it easy to schedule tasks without worrying about time changes.
SH
Shaun
1 year ago
User 1: I agree, A and B are the way to go for handling daylight savings time.
AB
Abel
1 year ago
Haha, I bet the 'frequent task execution' option is a trap. Like, 'oh, you thought that would work? Nope, still affects the history!'
GE
Gerald
1 year ago
C and E seem like the wrong answers. Tasks shouldn't suspend or fail to handle time changes, that would be a major limitation.
RY
Ryan
1 year ago
D) A frequent task execution schedule like minutes may not cause a problem, but will affect the task history.
LA
Laurel
1 year ago
B) Task schedules can be designed to follow specified or local time zones to accommodate the time changes.
KR
Kristine
1 year ago
A) A task scheduled in a UTC-based schedule will have no issues with the time changes.
LE
Leonardo
1 year ago
I think A and B are the correct answers. Snowflake handles daylight savings time by using UTC-based schedules and allowing for time zone customization.
AN
Annabelle
1 year ago
Yes, tasks scheduled in UTC or customized time zones will not be affected by the time changes.
ET
Ettie
1 year ago
I agree, A and B are the correct answers. Snowflake handles daylight savings time well.
TU
Tu
2 years ago
I believe option D is incorrect because frequent task execution schedules like minutes can still be affected by daylight savings time changes.
AR
Arlene
2 years ago
I agree with Xenia. Option A is also valid since UTC-based schedules are not affected by daylight savings time changes.
XE
Xenia
2 years ago
I think option B is correct because tasks can be scheduled based on local time zones.