Related questions
Question 34 - ADA-C01 discussion
An Administrator has been asked to support the company's application team need to build a loyalty program for its customers. The customer table contains Personal
Identifiable Information (PII), and the application team's role is DEVELOPER.
CREATE TABLE customer_data (
customer_first_name string,
customer_last_name string,
customer_address string,
customer_email string,
... some other columns,
);
The application team would like to access the customer data, but the email field must be obfuscated.
How can the Administrator protect the sensitive information, while maintaining the usability of the data?
A.
Create a view on the customer_data table to eliminate the email column by omitting it from the SELECT clause. Grant the role DEVELOPER access to the view.
B.
Create a separate table for all the non-Pll columns and grant the role DEVELOPER access to the new table.
C.
Use the CURRENT_ROLE and CURRENT_USER context functions to integrate with a secure view and filter the sensitive data.
D.
Use the CURRENT_ROLE context function to integrate with a masking policy on the fields that contain sensitive data.
Your answer:
0 comments
Sorted by
Leave a comment first