Salesforce Certified Platform Data Architect
Design scalable, high-performing, and well-governed data architectures on Salesforce. This guide walks you through the exam structure, key topics, study strategy and curated resources to help you pass the Platform Data Architect exam.
Who Should Take the Platform Data Architect Exam?
The Salesforce Certified Platform Data Architect credential targets professionals who design and implement enterprise-scale data strategies on Salesforce and across integrated systems.
- Salesforce Architects and Senior Consultants working on complex data programs.
- Experienced Admins / App Builders who frequently design data models and integrations.
- Technical leads responsible for data quality, governance, and performance at scale.
If you’re aiming for the Application Architect or Technical Architect (CTA) path, Platform Data Architect is one of the cornerstone domain certifications.
📊 Exam Snapshot
| Exam Name | Salesforce Certified Platform Data Architect |
| Credential Type | Domain Architect | Data Architecture & Management |
| Format | 60 scored multiple-choice / multiple-select (plus a few unscored items) |
| Time | ~105 minutes |
| Passing Score | Around 58% (always check the latest official exam guide) |
| Registration Fee | USD $400 (Retake: USD $200) |
| Recommended Experience | 2–3+ years hands-on Salesforce plus significant experience in data modeling, integrations, and data governance in enterprise environments. |
⚠️ Numbers above can change. Always confirm on the official Salesforce exam guide before booking your exam.
📘 High-Level Exam Outline
Exact weightings change over releases, but most questions will cluster around the following domains:
1. Data Modeling & Database Design
Core vs. custom objects, relationships (MD, lookup, junction), LDV & performance considerations.
2. Master Data Management & Data Governance
Duplicate management, golden records, governance frameworks, ownership models.
3. Large Data Volumes & Performance
Indexes, skinny tables, selective queries, partitioning, archiving strategies.
4. Data Migration & Lifecycle
Migration tools, sequencing, rollback, backup & restore, sandbox seeding.
5. External Data & Integration Patterns
External objects, data virtualization vs. replication, Data Cloud & data lakes.
6. Compliance, Security & Data Residency
Retention policies, regional residency, regulatory requirements (GDPR-style scenarios).
Tip: Your goal is not just knowing features, but being able to choose the right data pattern for a given business / technical scenario.
📝 4–6 Week Study Strategy
Week 1 – Understand the Blueprint
- Read the official exam guide end-to-end.
- Map topics to your own strengths and gaps.
- Review existing orgs you’ve worked on – how is data modeled today?
Weeks 2–3 – Go Deep by Domain
- Study one major area at a time (LDV, MDM, migration, external data…).
- Build or tweak sample data models in a dev org.
- Experiment with indexes, skinny tables, archiving, and query plans.
Weeks 4–5 – Scenario Practice
- Practice reading long scenario questions slowly and under time pressure.
- Draw target data architectures on paper / whiteboard.
- Focus on trade-offs: cost vs. performance vs. complexity.
Week 6 – Final Review
- Review weak areas using notes and Trailhead modules.
- Do 2–3 full-length practice sessions (timed).
- Finalize an exam-day checklist and book / reconfirm your slot.
🔗 Recommended Resources
- Official Exam Guide: Download the latest “Salesforce Certified Platform Data Architect” exam guide from Salesforce Credential site and keep it as your baseline.
- Trailhead: Follow data-focused trails – Data Management, Large Data Volumes, Data Quality, Data Cloud (if applicable for your exam version).
- Architect Journey: Explore the Data Architect section in the Salesforce Architect Journey for reference designs and patterns.
- Your Practice Guide: 📖 View Complete Platform Data Architect Guide
- Project Experience: Revisit past projects – identify how you handled LDV, integrations, and archiving; think about how you’d redesign them now as an architect.
❓ Sample Scenario-Style Questions
These are unofficial practice questions to help you think like a data architect. They are not taken from the real exam.
Question 1 – Large Data Volumes & Reporting
- Implement partitioning and filtered list views for current-year transactions only.
- Move older data to a separate archival object or external store, surfaced via external objects.
- Use indexing and skinny tables to support most common current-year queries.
Think about LDV strategy + user experience instead of just “more storage”.
Question 2 – Master Data & Duplicate Management
How would you design the MDM and matching strategy on Salesforce? Consider:
- External IDs and source-of-truth fields.
- Duplicate rules & matching rules vs. external MDM tooling.
- How to manage merges, survivorship rules and auditability.
Question 3 – External vs. Replicated Data
Which pattern is usually most appropriate?
- Use External Objects for line items with selective access via SOQL & OData.
- Replicate only a subset of recent orders locally for performance-critical scenarios.
- Avoid copying the full dataset into Salesforce due to storage & LDV constraints.
🎯 Where Platform Data Architect Fits in Your Journey
Platform Data Architect is a core building block for several higher-level Salesforce credentials:
- Application Architect: Platform Data Architect + Sharing & Visibility + Identity & Access + Dev Lifecycle & Deployment (exact combination may vary by release).
- System Architect: Complements Integration, Identity, and other system-level domain certs.
- Technical Architect (CTA): Deep data architecture expertise is critical for the CTA review board.
❔ Quick FAQ – Platform Data Architect
Do I need to be a developer to pass this exam?
You don’t have to be a full-time developer, but you should understand how data decisions impact APEX, integrations, and performance. Being able to read SOQL and reason about query selectivity is helpful.
Is this more about tools or about architecture?
Strongly architecture-focused. You’ll be tested on patterns, trade-offs, and end-to-end design, not just “where to click” to set up features.
How long should I prepare?
With solid project experience, many candidates prepare for 4–8 weeks. If data architecture is newer for you, plan extra time to build hands-on scenarios in a dev org.