IntegrationAdvancedencryptionshieldintegration
Handle integration with Salesforce encrypted fields
Real World Scenario
Integration cannot filter warehouse sync on encrypted SSN field breaking match logic.
Expected Answer
• Deterministic encryption for fields needing equality match
• Hash companion field for integration matching not encrypted
• Integration reads decrypted only via authorized service user
• Document fields unavailable for external filter
• Rotate encryption keys with integration pause plan
• Tokenization external vault alternative for highest sensitivity
• Test integration in Shield-enabled sandbox
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Deterministic encryption for fields needing equality match Also consider: Hash companion field for integration matching not encrypted In practice: Integration reads decrypted only via authorized service user Optimize for scale and operational observability.
Architect Perspective
Encryption changes integration contracts—design hash or token fields before enabling Shield on match keys.