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

- Free Preparation Discussions

Snowflake COF-R02 Exam - Topic 6 Question 39 Discussion

Actual exam question for Snowflake's COF-R02 exam

Question #: 39
Topic #: 6

[All COF-R02 Questions]

Data storage for individual tables can be monitored using which commands and/or objects? (Choose two.)

ASHOW STORAGE BY TABLE;

BSHOW TABLES;

CInformation Schema -> TABLE_HISTORY

DInformation Schema -> TABLE_FUNCTION

EInformation Schema -> TABLE_STORAGE_METRICS

Show Suggested Answer

Suggested Answer: A, E

by Sherell at Aug 28, 2024, 11:33 AM

Limited Time Offer

25%

Off

Get Premium COF-R02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Sol

8 months ago

I thought TABLE_HISTORY was just for tracking changes, not storage!

upvoted 0 times

...

Lashon

8 months ago

SHOW TABLES is too basic for this question.

upvoted 0 times

...

Antonio

8 months ago

Wait, is SHOW STORAGE BY TABLE even a real command?

upvoted 0 times

...

Oretha

8 months ago

I agree, E is the way to go!

upvoted 0 times

...

Kina

8 months ago

I think it's definitely E and C!

upvoted 0 times

...

Ben

9 months ago

I remember TABLE_STORAGE_METRICS being mentioned in class, but I can't recall if it's the right one for this question.

upvoted 0 times

...

Caitlin

9 months ago

I'm not entirely sure, but I think SHOW TABLES is more about listing tables rather than monitoring storage.

upvoted 0 times

...

Shaun

9 months ago

I practiced a question similar to this, and I feel like SHOW STORAGE BY TABLE was one of the commands we discussed.

upvoted 0 times

...

Gary

9 months ago

I think we might need to use the Information Schema for monitoring storage, but I can't remember if it's TABLE_HISTORY or TABLE_STORAGE_METRICS.

upvoted 0 times

...

Bea

9 months ago

I'm feeling pretty confident about this one. I know there are a few different ways to monitor data storage, and I think the correct answers are going to be the most direct and specific options.

upvoted 0 times

...

Solange

9 months ago

I'm a bit confused by the options here. I'm not sure if I should be looking for SQL commands or database objects. Let me re-read the question carefully.

upvoted 0 times

...

Tegan

9 months ago

Okay, I think I've got this. The key is to focus on the commands and objects that specifically monitor data storage for individual tables.

upvoted 0 times

...

Stevie

9 months ago

Hmm, this looks like a tricky one. I'll need to think carefully about the options and make sure I understand the differences between them.

upvoted 0 times

...

Larae

9 months ago

Ah, I see what they're getting at now. I think the best approach is to eliminate the options that are too broad or don't directly address the question.

upvoted 0 times

...

Rachael

9 months ago

I think the key here is finding a way to efficiently index and retrieve the files for the auditors. Option C with the DynamoDB table looks promising, but I'll need to consider the other choices as well.

upvoted 0 times

...

Maryann

10 months ago

Okay, this looks straightforward. Azure Key Vault is designed to securely store sensitive data, so it should be a good fit for protecting the content of the scanned intake forms. I'll make sure to review the documentation to confirm the security guarantees.

upvoted 0 times

...

Marge

2 years ago

D) Information Schema -> TABLE_FUNCTION? Really? That's about as useful as a chocolate teapot for monitoring data storage. E) and C) are the way to go, for sure.

upvoted 0 times

Glory

2 years ago

E) SHOW STORAGE BY TABLE and Information Schema -> TABLE_STORAGE_METRICS are the best choices for monitoring data storage.

upvoted 0 times

...

Nohemi

2 years ago

D) Yeah, I agree, Information Schema -> TABLE_FUNCTION doesn't seem very useful for this.

upvoted 0 times

...

Carlee

2 years ago

D) Yeah, I agree. Information Schema -> TABLE_FUNCTION doesn't seem very helpful for monitoring data storage.

upvoted 0 times

...

Roosevelt

2 years ago

C) Information Schema -> TABLE_HISTORY is also a good choice for keeping track of data storage changes.

upvoted 0 times

...

Edna

2 years ago

C) Information Schema -> TABLE_HISTORY is also a good option for monitoring individual table storage.

upvoted 0 times

...

Willetta

2 years ago

E) Information Schema -> TABLE_STORAGE_METRICS is definitely the best option for monitoring data storage.

upvoted 0 times

...

Ashleigh

2 years ago

E) Information Schema -> TABLE_STORAGE_METRICS is definitely the way to go for monitoring data storage.

upvoted 0 times

...

...

Daniel

2 years ago

A) SHOW STORAGE BY TABLE sounds like it could work, but I've never heard of that command before. E) and C) seem like the reliable choices here.

upvoted 0 times

...

Denna

2 years ago

Chocolate teapot? I'm going to have to remember that one! Good one, mate.

upvoted 0 times

Arlean

2 years ago

E) Information Schema -> TABLE_STORAGE_METRICS

upvoted 0 times

...

Valentine

2 years ago

C) Information Schema -> TABLE_HISTORY

upvoted 0 times

...

Heidy

2 years ago

A) SHOW STORAGE BY TABLE;

upvoted 0 times

...

...

Fernanda

2 years ago

Haha, yeah, that's a pretty creative analogy. Gotta love a bit of humor in these dry exam questions.

upvoted 0 times

Jarvis

2 years ago

C) Information Schema -> TABLE_HISTORY

upvoted 0 times

...

Claribel

2 years ago

A) SHOW STORAGE BY TABLE;

upvoted 0 times

...

...

Shawnda

2 years ago

I believe option E) Information Schema -> TABLE_STORAGE_METRICS could also be a valid choice for monitoring data storage.

upvoted 0 times

...

Suzan

2 years ago

I'm not sure about option D) Information Schema -> TABLE_FUNCTION. I think it's not related to monitoring data storage.

upvoted 0 times

...

Charisse

2 years ago

I agree with Magnolia. Those commands and objects are used to monitor data storage for individual tables.

upvoted 0 times

...

Magnolia

2 years ago

I think the answer is A) SHOW STORAGE BY TABLE and C) Information Schema -> TABLE_HISTORY.

upvoted 0 times

...