Salesforce Certified Data Architect Practice Exam
Prepare for the Salesforce Certified Data Architect exam with scenario-based, source-cited practice questions across all six exam objectives — data modeling & database design, Salesforce data management, large data volumes, data migration, data governance, and master data management. Every explanation links to the exact Salesforce documentation it derives from. Includes Learn mode and full timed Exam mode.
Start 24-hour free trial →Salesforce Data Architect exam at a glance
- Vendor
- Salesforce
- Credential
- Salesforce Certified Data Architect
- Exam code
- None — Salesforce architect exams are identified by name, not a numeric code
- Level
- Architect (advanced)
- Blueprint
- Salesforce Certified Data Architect Exam Guide (Spring ’26); verify current edition before publish
- Format
- 60 multiple-choice / multiple-select questions (up to 5 additional unscored)
- Duration
- 105 minutes
- Passing score
- Salesforce sets a scaled cut score and does not prominently publish a fixed figure; it has been cited in the ~58–67% range and can vary by release
- Registration fee
- USD $400 (retake USD $200), plus applicable taxes
- Delivery
- Proctored — onsite test center or online
- Prerequisites
- None to sit the exam. It is a step in the Salesforce Architect journey (Application / System / Technical Architect)
- Maintenance
- Kept current via Salesforce’s free release/maintenance modules on Trailhead
Source: Salesforce — Data Architect credential & official exam guide. Salesforce updates exam guides each release; verify the current format, fee, and objective weights before scheduling.
About the Salesforce Certified Data Architect credential
The Salesforce Certified Data Architect credential is for professionals who design and implement enterprise-scale data solutions on the Salesforce Platform. It validates that you can build scalable data models, manage large data volumes, plan and execute data migrations, and put master-data-management and governance frameworks in place across complex, multi-cloud Salesforce environments. This is an advanced, scenario-driven exam: most questions hand you a customer situation with competing valid options and ask for the best architectural decision, where the wrong answers are wrong for specific, learnable reasons (storage implications, sharing recalculation, query selectivity, referential integrity).
It is one of the domain architect credentials in the Salesforce Architect journey, alongside credentials such as Integration Architect, and it feeds toward the System and Application Architect designations and ultimately the Certified Technical Architect path. You do not need any prerequisite certification to sit it, but Salesforce assumes real hands-on experience with data modeling, sharing and security, and the platform’s data tools. For the data-architecture concepts these scenarios test, see the Salesforce architect study guides in the Learning Hub.
Salesforce Data Architect exam objectives and weights
Six weighted objectives. Data Modeling & Database Design and Salesforce Data Management together make up half the exam, so weight your study there first — but scenario questions routinely blend objectives (a model that must also scale under large data volumes and satisfy governance policies). The weights below reflect the official exam guide and sum to 100%.
Object relationships, schema design, standard/custom/external/big objects, field types, and scalable models that respect the security and sharing model.
Managing data across Salesforce objects and orgs, metadata capture, data quality and lifecycle, and virtualized/external data access patterns.
Indexing, skinny tables, data skew (ownership, lookup, account), selective queries, PK chunking, and archiving strategies for millions of records.
ETL strategy, Bulk API, external IDs and referential integrity, parallel loading, high-quality load techniques, and export considerations.
Enterprise data governance programs, data quality frameworks, roles and responsibilities, compliance (e.g. GDPR), and monitoring.
MDM implementation styles, golden-record / system-of-truth design, survivorship rules, consolidation from multiple sources, and hierarchy management.
Source: Salesforce Certified Data Architect Exam Guide. Weights are drawn from the official exam guide and sum to 100%; verify against the current release before publish. (Some third-party pages list a four-domains-at-10% split that only reaches 90% — that is incomplete.)
Who the Salesforce Data Architect exam is for
This is an advanced credential for experienced practitioners who own the data layer of enterprise Salesforce implementations:
- Data architects designing enterprise data models, LDV strategies, and migration plans on the Salesforce Platform.
- Technical and solution architects who make cross-cloud data decisions and need to defend design trade-offs to business stakeholders.
- Senior developers and consultants moving into architecture who already work with sharing, integration, and data-loading tools.
- Platform leads and admins responsible for data quality, governance, and org performance at scale.
If you are newer to the platform, a role-based Administrator or Platform Developer credential is the better starting point; the Data Architect exam assumes you have already wrestled with data skew, storage limits, and referential integrity in a real org. For the roles this credential supports and where the Salesforce architect track leads, see the Salesforce architect career paths in the Career Hub.
What this Salesforce Data Architect practice exam delivers
Learn mode
Get the correct answer, the reasoning, why each distractor is wrong, and a link to the exact Salesforce documentation page — immediately after each question. Built for the architectural trade-off scenarios this exam is made of.
Exam mode
60 questions on a 105-minute timer — the real Data Architect format. Build the pacing and stamina for multi-layered scenario questions under pressure.
Source-linked explanations
Every answer cites the exact Salesforce documentation (developer.salesforce.com, Trailhead) the question was built from — so you verify against the source, not just memorize.
Score by objective
Results break down across the six official objectives — data modeling, Salesforce data management, LDV, migration, governance, and MDM — so practice tells you exactly which domain to revisit.
Sample Salesforce Data Architect practice questions
Ten free questions across the six exam objectives, with full explanations and links to the Salesforce documentation each is derived from. The complete bank is available with the 24-hour trial.
A global retail company is migrating 500 million historical transaction records to Salesforce. The records are rarely accessed but must be available for compliance reporting. Which Salesforce data storage solution should the data architect recommend?
- Big Objects to store the historical transactions, with Async SOQL for reporting
- External Objects connected to the legacy system via Salesforce Connect
- A custom Heroku database with OData integration
- Custom objects with archival record types and a scheduled purge job
Show answer & explanation
Correct: A — Big Objects with Async SOQL. Big Objects store massive volumes (hundreds of millions to billions of records) without consuming standard data storage, and Async SOQL is designed to query them for reporting.
Why not the others: External Objects (B) require the legacy system to stay online and reachable; a Heroku database (C) adds infrastructure and integration complexity for data that only needs archival access; and standard custom objects (D) would consume standard storage and hit limits at this volume.
Source: Salesforce — Big Objects → Further reading: PowerKram — Large Data Volume strategies →A financial institution is experiencing slow SOQL query performance on an Account object with 20 million records. Most queries filter by Account Type and Region. What should the data architect recommend to improve query performance?
- Partition the Account object into separate custom objects by region
- Add skinny tables through Salesforce Support
- Convert the Account object to a Big Object
- Request a custom composite index on Account Type and Region from Salesforce Support
Show answer & explanation
Correct: D — a custom composite index. A composite index on the frequently filtered field combination (Account Type + Region) makes those queries selective and significantly improves SOQL performance at large volume.
Why not the others: partitioning by region (A) breaks the data model and reporting; skinny tables (B) help wide-field read performance but are not the primary fix for filter selectivity; and converting to a Big Object (C) is for archival data, not an active, queried Account object.
Source: Salesforce — LDV: Indexes →A company is migrating from SAP to Salesforce — Accounts, Contacts, and Opportunities with complex lookup relationships and 5 million records. What is the correct approach for maintaining referential integrity?
- Use Data Loader with auto-matching to resolve relationships after all data is loaded
- Load all objects simultaneously using parallel Bulk API jobs
- Load parent objects first, then children, using external ID fields for relationship mapping
- Create temporary text fields for relationship keys and resolve them with a post-migration flow
Show answer & explanation
Correct: C — parents first, children by external ID. Loading parents before children and using external ID fields lets the Bulk API resolve relationships by matching legacy identifiers on upsert, preserving referential integrity.
Why not the others: loading all objects in parallel (B) risks orphaned child records; “auto-matching” (A) is not a real Data Loader capability; and temporary key fields with a post-migration flow (D) are error-prone and slow at 5 million records.
Source: Salesforce — Bulk API: Upsert & External IDs → Further reading: PowerKram — Integration Architect exam →An e-commerce company wants to display real-time product inventory from its warehouse management system on Salesforce record pages without storing the data in Salesforce. Which solution should the data architect recommend?
- A scheduled batch job that syncs inventory data every 5 minutes
- A Lightning Web Component that calls the warehouse API directly from the browser
- Platform Events to stream inventory updates into a custom Salesforce object
- External Objects using Salesforce Connect with an OData adapter
Show answer & explanation
Correct: D — External Objects via Salesforce Connect (OData). Salesforce Connect exposes external data as External Objects with real-time, on-demand access — the data is retrieved live and never stored in Salesforce.
Why not the others: a 5-minute batch sync (A) produces stale data and storage overhead; a browser-side API call (B) raises CORS and security problems; and Platform Events (C) still land the data in a Salesforce object, which the requirement rules out.
Source: Salesforce — Salesforce Connect & External Objects → Further reading: PowerKram — Data Cloud Consultant exam →A healthcare organization must deduplicate patient Contact records based on Last Name, Date of Birth, and a custom National ID field. Which configuration should the data architect implement?
- A matching rule with fuzzy match on Last Name and exact match on the other fields, paired with a duplicate rule that alerts users
- A before-save flow that searches for duplicates and blocks the save
- A Batch Apex job that runs nightly to merge duplicate Contacts
- A validation rule that queries for existing records with the same field values
Show answer & explanation
Correct: A — matching rule + duplicate rule. Salesforce Duplicate Management uses matching rules (supporting fuzzy and exact matching per field) with duplicate rules to detect or block duplicates in real time — exactly this mixed fuzzy/exact requirement.
Why not the others: a validation rule (D) cannot query other records; a custom flow (B) lacks the built-in fuzzy-matching engine; and a nightly Batch Apex merge (C) only catches duplicates after they are already created.
Source: Salesforce — Duplicate Management →A manufacturing company has an Account ownership skew problem where a single integration user owns 3 million Account records. What should the data architect recommend?
- Increase the sharing recalculation timeout threshold
- Convert the Account org-wide default to Public Read/Write
- Redistribute ownership of the records across users by region or business unit
- Move the 3 million records to a Big Object
Show answer & explanation
Correct: C — redistribute ownership. Ownership skew (one user owning a very large share of records) causes lock contention and slow sharing recalculation; spreading ownership across many users removes the skew. Salesforce guidance is to avoid concentrating large record counts under a single owner.
Why not the others: there is no configurable sharing-recalculation timeout (A); switching the OWD to Public Read/Write (B) removes needed security controls; and Big Objects (D) cannot hold active, operational Account data.
Source: Salesforce — LDV: Data Skew →A telecom company stores Customer, Contract, and Service records. Each Customer has multiple Contracts; each Contract has multiple Services. Roll-up summaries of Service revenue are needed at both levels. How should the data architect design the data model?
- Master-detail relationships (Service to Contract to Customer), leveraging native roll-up summary fields
- Lookup relationships between all three objects, calculating roll-ups with Apex
- External objects with Salesforce Connect for aggregation
- A single flat object with record types for each entity
Show answer & explanation
Correct: A — master-detail with native roll-up summaries. Master-detail relationships enable native roll-up summary fields at each level (Service→Contract→Customer) without code, giving revenue roll-ups at both tiers.
Why not the others: lookup relationships (B) do not support native roll-up summary fields, forcing custom Apex; external objects (C) cannot host roll-up summaries; and a single flat object (D) violates normalization and loses the hierarchy.
Source: Salesforce — Data Modeling: Object Relationships → Further reading: PowerKram — Platform Developer II exam →A data architect is planning a weekend migration of 50 million records using the Bulk API within a 48-hour window. Which approach should maximize throughput?
- Bulk API 1.0 in serial mode
- REST API with individual record inserts
- Data Loader with the maximum batch size
- Bulk API 2.0 with parallel processing and optimally sized data files
Show answer & explanation
Correct: D — Bulk API 2.0 with parallel processing. Bulk API 2.0 automatically manages job chunking, parallelization, and retries, giving the best throughput for a large one-time load within a tight window.
Why not the others: Bulk API 1.0 serial mode (A) processes batches one at a time and is slower; REST API single-record inserts (B) are far too slow at 50 million records; and Data Loader (C) runs on the Bulk API underneath but gives less direct control than calling Bulk API 2.0.
Source: Salesforce — Bulk API 2.0 →A governance team finds 30% of Account records have missing or inconsistent Industry values. They want to enforce quality going forward and clean existing data. What strategy should the data architect implement?
- A screen flow for data entry that requires Industry, plus Data Loader for existing records
- A validation rule to enforce Industry, plus a Batch Apex cleanup of existing records
- A page-layout required-field constraint
- A report to identify bad records, with emails to Account owners
Show answer & explanation
Correct: B — validation rule + Batch Apex cleanup. A validation rule enforces the Industry requirement at the point of entry across all interfaces (UI and API), while Batch Apex systematically remediates the existing bad records — forward enforcement plus back-fill.
Why not the others: a screen flow (A) only enforces on the specific pages that use it; a page-layout required field (C) is not enforced through the API; and a report with emails (D) relies on manual, inconsistent compliance.
Source: Salesforce — Data Quality → Further reading: PowerKram — enterprise data governance guide →A data architect needs an archival strategy for an org approaching its storage limit. Case records older than two years should be archived but still accessible. Which approach should the data architect recommend?
- Compress the Case records by removing attachment data
- Move old Cases to a secondary Salesforce org
- Delete old Cases and rely on the Recycle Bin
- Export old Cases to Big Objects and build a custom Lightning component for lookup access
Show answer & explanation
Correct: D — archive to Big Objects with a custom lookup component. Big Objects provide scalable, low-cost storage for archived data that stays queryable, and a custom Lightning component can surface it on demand — archived but still accessible.
Why not the others: removing attachments (A) may violate retention requirements and barely reduces record count; a secondary org (B) adds cost and integration complexity; and deleting with Recycle Bin reliance (C) fails — the Recycle Bin only retains records for 15 days.
Source: Salesforce — Big Objects →Keep going: Learning & Career resources
The Data Architect credential is one step in the Salesforce Architect journey. Both PowerKram hubs back this exam.
Deep dive: exam format, scoring, study path, and the Salesforce Architect journey
Exam format and scoring
The Salesforce Certified Data Architect exam is 60 multiple-choice/multiple-select questions (plus up to 5 unscored) in 105 minutes, delivered proctored at a test center or online. The registration fee is USD $400 with a USD $200 retake. Salesforce sets a scaled cut score and does not prominently publish a single fixed passing percentage; figures cited across releases fall roughly in the 58–67% band, so treat any specific number as approximate and confirm against the current exam guide. There is no prerequisite certification. Read the Data Architect format & scoring guide →
What the exam actually tests
This is a scenario exam, not a recall exam. Nearly every question is a customer situation with several defensible options where you pick the best architectural decision. The recurring themes: when to use standard vs custom vs external vs big objects; how to keep queries selective at large data volume (indexing, skinny tables, avoiding data skew); how to preserve referential integrity in a migration (parents first, external IDs, Bulk API 2.0); and how to design governance and MDM so data quality holds up over time. Know the trade-offs cold — storage, sharing recalculation, query selectivity, and retention. See more Salesforce exams →
Realistic study path
Most candidates need eight to sixteen weeks depending on experience. Weight your time by the objective percentages: the two 25% domains (Data Modeling & Database Design, Salesforce Data Management) come first, then Large Data Volumes at 20%. Build hands-on in a Developer Org — create master-detail vs lookup relationships, implement Big Objects, configure duplicate management, and run Data Loader / Bulk API loads in parallel mode — because this exam cannot be passed by reading alone. Then rehearse scenario reasoning in Learn mode and run full timed simulations in Exam mode. Read the Data Architect study plan →
The Salesforce Architect journey
Data Architect is a domain architect credential. It contributes toward the higher System Architect and Application Architect designations, which in turn build toward the Certified Technical Architect (CTA). It pairs naturally with Integration Architect for architects working across systems, and with Platform Developer II for those coming from a build background. Sitting Data Architect first is a common on-ramp because its data-modeling and LDV content underpins so much of the rest of the track. See the Integration Architect exam →
Maintenance and staying current
Salesforce credentials are kept current through free release/maintenance modules on Trailhead rather than a full re-sit, so once earned the credential stays valid as long as you complete the periodic maintenance. Because Salesforce refreshes exam guides each release, confirm the current objective weights, fee, and format on the official credential page before you schedule. Salesforce — Data Architect credential →
Frequently asked questions
What are the Salesforce Data Architect exam objectives and weights?
Six objectives: Data Modeling & Database Design (25%), Salesforce Data Management (25%), Large Data Volumes (20%), Data Migration (15%), Data Governance (10%), and Master Data Management (5%). The two 25% domains together make up half the exam. Weights are from the official exam guide and sum to 100%.
What format is the Salesforce Data Architect exam?
60 multiple-choice/multiple-select questions (plus up to 5 unscored) in 105 minutes, delivered proctored onsite or online. The registration fee is USD $400 with a USD $200 retake. Salesforce sets a scaled cut score and does not prominently publish a single fixed passing percentage.
Does the Salesforce Data Architect exam have prerequisites?
No prerequisite certification is required to sit it. It is a domain credential in the Salesforce Architect journey and contributes toward the System Architect and Application Architect designations and ultimately the Certified Technical Architect path. Salesforce assumes hands-on data-architecture experience.
Is there an exam code or “exam number” for this credential?
No. Salesforce architect exams are identified by name (Salesforce Certified Data Architect), not by a numeric exam code. Any numeric “exam number” you see attached to it is an internal catalog identifier, not a code you use to register.
How do I keep the credential current?
Salesforce credentials are maintained through free release/maintenance modules on Trailhead rather than re-sitting the full exam. Complete the periodic maintenance to keep the credential valid, and check the official exam guide each release for objective or format changes.
Start your free 24-hour Salesforce Data Architect practice trial
Full access to 1600+ questions, both study modes, source-linked explanations, and score-by-objective. No credit card required.
Start free trial →