INTEGRATION-ARCHITECTURE-DESIGNER practice question 1 of 25

Northern Trail Outfitters has a requirement to encrypt few of widely used standard fields. They also want to be able to use these fields in workflow rules. Which security solution should an Integration Architect recommend to fulfill the business use case?

Full set: 106 questions

Domain Design a Security Solution

Answer options
A: Cryptography Class
B: Data Masking
C: Classic Encryption
D: Platform Shield Encryption Correct answer
Correct Answer:
D. Platform Shield Encryption
Explanation

Shield Platform Encryption is the appropriate solution as it allows for the encryption of a wide range of standard and custom fields while preserving critical business functionality. A key feature is its compatibility with declarative automation tools. Encrypted fields can be used in the criteria for workflow rules, meeting the specific requirement of the business use case. This solution provides strong, native encryption for data at rest without sacrificing the ability to automate processes based on that data.

Why Incorrect

A. Cryptography Class: This is an Apex class for custom, programmatic encryption within code. It does not provide transparent, at-rest encryption for standard fields that platform features like workflow rules can use.
B. Data Masking: This is a tool used to anonymize or pseudonymize data in non-production environments (sandboxes), not for encrypting live data in a production org.
C. Classic Encryption: Classic Encryption is an older feature with significant limitations. Critically, fields encrypted with Classic Encryption cannot be used in workflow rule criteria, directly contradicting the requirement.

References

1. Shield Platform Encryption Compatibility: Salesforce Help, "How Shield Platform Encryption Affects Salesforce Features". Under the "Workflow Rules" section, it states, "You can use encrypted fields in workflow rule criteria." This directly supports the correct answer.

2. Classic Encryption Limitations: Salesforce Help, "Classic Encryption for Custom Fields". In the "Classic Encryption Limitations" section, it explicitly lists that "Encrypted fields can't be used in... Workflow rule criteria." This confirms why option C is incorrect.

3. Apex Crypto Class: Salesforce Apex Developer Guide, "Crypto Class". The documentation describes this class for functions like encrypt(), decrypt(), and generating digests within Apex code, not for platform-level field encryption.

4. Data Mask: Salesforce Help, "Data Mask". The documentation states, "Data Mask is a data security tool that Salesforce admins can use to... mask sensitive data in a sandbox." This clarifies its purpose is for non-production environments.

Scroll to Top