Evaluate Business Needs11% of the exam
Classifying data as Public, Confidential or Secure
How to place integration data in the Public, Confidential and Secure tiers, record the tier on each field with Data Sensitivity Level and Compliance Categorization, read it from middleware through FieldDefinition, and turn each tier into concrete controls such as data minimization and mutual TLS.
Based on a given integration requirement, identify and classify data into Confidential/Secure/Public.
~7 min read · 9 practice questions ·
What the exam expects
- Place a data element in the Public, Confidential or Secure tier from what it is (published catalog, personal data, regulated identifiers).
- Map each tier to the protection an integration needs, from standard TLS to mutual TLS and exclusion from the payload.
- Record sensitivity and applicable regulations per field with Data Sensitivity Level and Compliance Categorization, and align the picklist to company policy.
- Classify many fields in bulk, and let middleware read classification programmatically.
- Apply data minimization: send only the fields a consumer needs.
- Key terms: Secure (the exam's highest, regulated tier; Salesforce's Trust guidance calls it Restricted); Data Sensitivity Level (field metadata stored as
SecurityClassification); Compliance Categorization (field metadata naming regulations such as GDPR or PCI); data dictionary (catalog of what data you hold and where sensitive data lives); data minimization (collect and move only what the purpose needs).
Key facts
Highest tier examples
- Detail
- PHI, payment data, authentication credentials, SSNs (Restricted = exam's Secure)
Public tier control
- Detail
- Standard platform TLS in transit
Restricted data in integrations
- Detail
- TLS 1.2+ enforced by the platform, plus certificate-based mutual authentication you configure
Granularity
- Detail
- Classify at the field level; one record can hold several tiers
Availability
- Detail
- Data classification is in all editions and automatically enabled in all orgs
Permission to edit
- Detail
- Customize Application or Modify Data Classification
API name
- Detail
- Data Sensitivity Level =
SecurityClassificationon FieldDefinition
Upload limit
- Detail
- CSV of at most 10,000 rows: object, field, sensitivity level
Download limits
- Detail
- 5 MB; only fields with a sensitivity value; first 2,000 records per value
High-risk flag
- Detail
- Mark a Data Sensitivity picklist value as High-risk level
Email default
- Detail
- Email field has a Confidential default sensitivity value
- Why is a stored payment card number Secure while customer email is Confidential?
- When does an integration need certificate-based mutual authentication on top of TLS 1.2?
- Which tool classifies 3,000 existing fields at once from Setup?
- Why classify at the field level instead of the object level?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 25 lessons of the Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams