ADA-C01 · Question #86
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 correct answer is D. Use the CURRENT_ROLE context function to integrate with a masking policy on the fields that. See the full explanation below for the reasoning.
Question
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?
Options
- ACreate a view on the customer_data table to eliminate the email column by omitting it from the
- BCreate a separate table for all the non-Pll columns and grant the role DEVELOPER access to the
- CUse the CURRENT_ROLE and CURRENT_USER context functions to integrate with a secure
- DUse the CURRENT_ROLE context function to integrate with a masking policy on the fields that
How the community answered
(25 responses)- A12% (3)
- B4% (1)
- C4% (1)
- D80% (20)
Community Discussion
No community discussion yet for this question.