MENU
What are characteristics of Dynamic Data Masking? (Select TWO).
Suggested Answer: C
Get Premium ARA-R01 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
For the configuration of data unloading in Snowflake, the valid option among the provided choices is 'C.' This is because Snowflake supports unloading data into Google Cloud Storage using the COPY INTO <location> command with specific configurations. The configurations listed in option C, such as Parquet file format with UTF-8 encoding and gzip compression, are all supported by Snowflake. Notably, Parquet is a columnar storage file format, which is optimal for high-performance data processing tasks in Snowflake. The UTF-8 file encoding and gzip compression are both standard and widely used settings that are compatible with Snowflake's capabilities for data unloading to cloud storage platforms. Reference:
Snowflake Documentation on COPY INTO command
Snowflake Documentation on Supported File Formats
Snowflake Documentation on Compression and Encoding Options
35 comments · newest first
SH
Sharika
11 months ago
Geography data type? That's interesting, didn't know that!
AL
Alpha
11 months ago
I thought only the role that created it could see unmasked data.
PA
Pamella
11 months ago
Wait, can it really be applied to external tables? Sounds odd.
BE
Bettina
11 months ago
I agree, and a single policy can apply to different tables too!
RE
Rebbeca
11 months ago
A masking policy can definitely be dropped from a table.
BE
Beatriz
12 months ago
I have a vague memory of GEOGRAPHY data types, but I'm not confident if option E is correct. We might have touched on that in our review.
RO
Roxane
12 months ago
I remember something about roles and masking policies, so option D seems right. The creator should see unmasked data, right?
AM
Amina
12 months ago
I'm not entirely sure about option C; I feel like we might have gone over external tables, but I can't recall if masking policies apply to them.
RO
Rosamond
1 year ago
I think option B sounds familiar, like we discussed how a single policy can cover multiple tables in our practice sessions.
CA
Catalina
1 year ago
Alright, time to put my knowledge to the test. I'm pretty confident that a masking policy can't be applied to the value column of an external table, and the role that creates the policy won't always see unmasked data.
QU
Queen
1 year ago
Ah, I remember learning about this in class. I believe a masking policy can be dropped, and it can be applied to columns in different tables. But I'm not certain about the other options.
ME
Merissa
1 year ago
I think I've got a handle on this. Dynamic Data Masking allows you to apply a masking policy to columns, but I'm not sure if that policy can be applied across different tables.
LE
Leoma
1 year ago
Okay, let's see. I know Dynamic Data Masking is used to protect sensitive data, but I'm not sure about the specifics of how it works.
RO
Rosenda
1 year ago
Hmm, this looks like a tricky one. I'll need to think carefully about the characteristics of Dynamic Data Masking.
LU
Luis
1 year ago
Wait, can you apply Dynamic Data Masking to the data in my crystal ball? That would be a real magic trick!
SI
Simona
1 year ago
D) The role that creates the masking policy will always see unmasked data In query results
LA
Layla
1 year ago
B) A single masking policy can be applied to columns in different tables.
DO
Dorcas
1 year ago
A) A masking policy that Is currently set on a table can be dropped.
VI
Vivienne
1 year ago
C is a bit of a head-scratcher. Applying a masking policy to an external table's value column? Hmm, I'm not so sure about that one.
EL
Elmer
1 year ago
E is probably not correct. I don't think Dynamic Data Masking can be applied to a GEOGRAPHY data type column. That just seems a bit too specific.
LO
Louvenia
1 year ago
I believe B and D are the correct characteristics for Dynamic Data Masking.
EL
Elza
1 year ago
So, which characteristics do you think are correct for Dynamic Data Masking?
VA
Val
1 year ago
I agree, it's more likely that a masking policy can't be applied to a GEOGRAPHY data type column.
CA
Catalina
1 year ago
I think you're right, E does seem too specific for Dynamic Data Masking.
CL
Clemencia
1 year ago
D sounds like it could be a valid answer too. If the role that creates the masking policy can see the unmasked data, that's an important characteristic of Dynamic Data Masking.
GL
Glennis
1 year ago
D) The role that creates the masking policy will always see unmasked data In query results
CA
Carissa
1 year ago
A) A masking policy that Is currently set on a table can be dropped.
BE
Belen
1 year ago
I'm not sure about option D. I think it might be option A and option C instead.
OC
Ocie
1 year ago
I agree with Weldon. Applying a single masking policy to columns in different tables and the role creating the policy always seeing unmasked data make sense.
KR
Kristal
2 years ago
I'm pretty sure A and B are the correct answers. Dynamic Data Masking is all about applying a policy to mask sensitive data, and that policy should be able to be dropped or applied across different tables.
DE
Delfina
1 year ago
So, A and B are the characteristics of Dynamic Data Masking.
DE
Delila
1 year ago
That's correct, the policy can also be dropped if needed.
KI
King
1 year ago
Yes, Dynamic Data Masking allows for a masking policy to be applied across different tables.
TR
Tresa
1 year ago
I think you're right, A and B are the correct answers.
WE
Weldon
2 years ago
I think characteristics of Dynamic Data Masking include option B and option D.