MENU
An Architect clones a database and all of its objects, including tasks. After the cloning, the tasks stop running.
Why is this occurring?
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
40 comments · newest first
ST
Stefany
11 months ago
I disagree, it's all about the references not being right.
BE
Belen
11 months ago
Definitely insufficient privileges causing the issue.
AL
Aleisha
11 months ago
Wait, tasks can't be cloned at all? That seems odd.
CA
Carlene
11 months ago
I think it's because the objects aren't fully qualified.
OM
Omega
11 months ago
Cloned tasks are suspended by default and must be manually resumed.
CA
Carmen
12 months ago
I’m a bit confused about the privileges part. Could D be a factor? But I feel like it’s more about how tasks behave after cloning.
TI
Tish
12 months ago
I practiced a similar question, and I think it was mentioned that cloned tasks might be suspended by default. So, I’m leaning towards C as well.
CH
Cherelle
12 months ago
I'm not entirely sure, but I feel like tasks can be cloned. Maybe it's more about the references not being fully qualified?
DO
Dorthy
1 year ago
I remember something about tasks needing to be resumed after cloning, so I think C might be the right answer.
BE
Benedict
1 year ago
I'm a bit confused on this one. I'm not sure if the tasks can't be cloned or if the Architect doesn't have the right privileges to alter the tasks. I'll have to think about this a bit more.
BE
Benton
1 year ago
I'm pretty confident the answer is C - the cloned tasks are suspended by default and need to be manually resumed. I've seen this happen before when cloning databases with scheduled tasks.
AS
Ashlee
1 year ago
Okay, let's see. I'm guessing it has something to do with the objects that the tasks reference not being fully qualified. That would make sense if the tasks are relying on specific object names or locations that don't match the cloned database.
HE
Helga
1 year ago
Hmm, this is a tricky one. I'm not entirely sure why the tasks would stop running after cloning the database. Let me think this through carefully.
SH
Shelba
1 year ago
Cloning a database and expecting the tasks to just keep running? That's like cloning a dog and expecting it to walk on its own. Option C is the only one that makes sense to me.
AG
Agustin
1 year ago
Yeah, it's like the tasks are put on hold until someone manually resumes them.
WI
William
1 year ago
That makes sense, the cloned tasks probably need to be activated after the cloning process.
WE
Weldon
1 year ago
I think the tasks are suspended by default and need to be manually resumed.
EL
Ellsworth
1 year ago
Wait, the Architect has insufficient privileges to alter the tasks? That sounds like a classic 'blame the IT guy' scenario. I'm going with option D.
RY
Ryan
1 year ago
User 3: I believe the Architect has insufficient privileges to alter tasks on the cloned database.
DE
Desmond
1 year ago
User 2: Maybe the objects that the tasks reference are not fully qualified.
DO
Dorothy
1 year ago
I agree with you, it does sound like a 'blame the IT guy' situation. Option D seems plausible.
RY
Ryan
1 year ago
No, I believe the objects that the tasks reference are not fully qualified.
TR
Trinidad
1 year ago
User 1: I think the tasks are suspended by default on the cloned database.
JA
Jacquelyne
1 year ago
I think the tasks are suspended by default and need to be manually resumed.
AV
Avery
1 year ago
Aha! I know this one. Cloned tasks are suspended by default, so the Architect needs to manually resume them. Option C is the way to go.
DE
Deeann
1 year ago
Good job on knowing the solution!
ME
Melynda
1 year ago
That makes sense. Option C is the correct answer.
KR
Kristian
1 year ago
So, the Architect needs to manually resume them to get them running again.
GE
German
1 year ago
Yes, you're right. Cloned tasks are suspended by default.
MA
Marylin
2 years ago
I'm a bit confused by the wording of the question. Wouldn't the objects that the tasks reference need to be fully qualified for the tasks to work? I'm leaning towards option B.
BR
Brynn
1 year ago
User 2: That makes sense, maybe the Architect needs to update the references for the tasks to work properly.
LE
Leontine
1 year ago
User 1: I think the tasks stopped running because the objects they reference are not fully qualified.
RE
Rene
2 years ago
Hmm, I'm pretty sure the tasks can't be cloned since they are tied to the original database. Option A seems like the obvious choice here.
BE
Benton
1 year ago
It could also be that the Architect doesn't have enough privileges to alter the tasks on the cloned database.
RO
Rolland
1 year ago
I believe the tasks stop running because the objects they reference are not fully qualified.
GI
Gianna
1 year ago
But maybe the tasks cannot be cloned at all.
CH
Chandra
1 year ago
I think the tasks are suspended by default after cloning.
CA
Carolann
2 years ago
Maybe the objects that the tasks reference are not fully qualified.
JO
Jonelle
2 years ago
I agree with Linn, cloned tasks need to be manually resumed.
LI
Linn
2 years ago
I think the tasks are suspended by default.