Free Salesforce Platform Data Architect Practice Test Questions
257 questionsUpdated 18-Nov-2026
Question 61Choose 2
An Architect needs to document the data architecture for a multi-system, enterprise Salesforce implementation. Which two key artifacts should the Architect use? (Choose two.)
Correct answer:
B. Data model
C. Integration specification
Explanation:
For a multi-system Salesforce implementation, a data architect must produce artifacts that clearly represent how data is structured and how it flows between systems. A data model shows the entity relationships, attributes, and data ownership in Salesforce. An integration specification documents how Salesforce interacts with other systems, including data formats, transformation rules, and error handling. Together, these artifacts provide a comprehensive picture of how customer and business data moves through the enterprise landscape.
Why not the others?
A. User stories: User stories are valuable in Agile projects to capture business requirements from an end-user perspective. However, they focus on functionality and business outcomes, not technical documentation of data structures or integration flows. While user stories may inform design decisions, they are not formal artifacts for documenting enterprise data architecture.
D. Non-functional requirements: These requirements cover aspects such as scalability, performance, availability, and security. While important, they describe system qualities, not how data is structured or integrated. Non-functional requirements inform design constraints but do not serve as the architectural documentation an architect needs to illustrate data models and integration specifications.
Reference:
Salesforce Architect Guide: Data Modeling
Salesforce Integration Patterns and Practices
Question 62Choose 1
Get Cloudy Consulting uses an invoicing system that has specific requirements. One requirement is that attachments associated with the Invoice_c custom object be classified by Types (i.e., ""Purchase Order"", ""Receipt"", etc.) so that reporting can be performed on invoices showing the number of attachments grouped by Type. What should an Architect do to categorize the attachments to fulfill these requirements?
Correct answer:
D. Create a custom object related to the Invoice object with a picklist field for the Type.
Explanation:
The Attachment object is a legacy object that does not support custom fields or custom picklists for categorization. To enable reporting by attachment type, the best approach is to create a custom object (e.g., Invoice Attachment) that relates to the Invoice object. This object can store references to the actual file (via ContentDocument or external reference) and include a custom picklist field for categorization, which makes reporting and grouping possible.
Why not the others?
A. Add additional options to the standard ContentType picklist field: The ContentType field is not customizable. It is automatically populated by Salesforce based on the file type (e.g., PDF, JPG). You cannot add custom values such as “Purchase Order” or “Receipt,” so this option does not fulfill the business requirement.
B. Add a ContentType picklist field to the Attachment layout: The Attachment object does not allow adding custom fields directly, including picklists. Layout customization is limited. Even if possible, the field would not integrate with Salesforce reporting in the way the requirement demands. This option is not supported in practice.
C. Create a custom picklist field for the Type on the Attachment object: The Attachment object is system-defined and cannot be extended with custom fields. This limitation makes it impossible to track type values directly on Attachment records. Any reporting requirement would fail due to the inability to customize the object itself.
Universal Containers (CU) is in the process of implementing an enterprise data warehouse (EDW). UC needs to extract 100 million records from Salesforce for migration to the EDW. What data extraction strategy should a data architect use for maximum performance?
Correct answer:
C. Utilize PK Chunking with the Bulk API.
Explanation:
When extracting very large datasets (hundreds of millions of records), the Bulk API with PK Chunking is the recommended approach. PK Chunking automatically breaks the extraction into manageable chunks based on the record’s primary key (Id), which reduces the chance of query timeouts and improves overall throughput. It allows efficient parallel processing while keeping each batch within governor limits. For 100 million records, this is the most scalable and proven approach for Salesforce data extraction.
🔴 Why not the others?
A. Install a third-party AppExchange tool: Third-party tools can simplify extraction but ultimately use Salesforce APIs under the hood. They add overhead, licensing cost, and are not guaranteed to optimize for extreme high-volume exports. For a defined migration of 100 million records, direct use of Bulk API with PK Chunking is the most controlled and performant strategy.
B. Call the REST API in successive queries: REST API is synchronous and optimized for small to medium datasets. It has strict limits on the number of records per query and would timeout or hit daily API request limits when handling 100 million records. This approach is impractical for very large-scale data migrations.
D. Use the Bulk API in parallel mode: Bulk API in parallel mode improves throughput but without PK Chunking it risks uneven batch distribution, timeouts, or excessive failures. When datasets exceed tens of millions, PK Chunking ensures controlled segmentation. Parallel mode alone may increase the chance of hitting record lock or performance issues during extraction.
Northern Trail Outfitters (NTO) has a variety of customers that include householder, businesses, and individuals.
The following conditions exist within its system: 1. NTO has a total of five million customers.
2. Duplicate records exist, which is replicated across many systems, including Salesforce.
3. Given these conditions, there is a lack of consistent presentation and clear identification of a customer record.
Which three option should a data architect perform to resolve the issues with the customer data?
Correct answer:
A. Create a unique global customer ID for each customer and store that in all system for referential identity.
C. Invest in data duplicate tool to de-dupe and merge duplicate records across all systems.
E. Create a customer master database external to Salesforce as a system of truth and sync the customer data with all systems
Explanation:
This question addresses the core concepts of Master Data Management (MDM) and strategies for achieving a "single source of truth" for customer data across a fragmented ecosystem.
✅ Why A is Correct:
The fundamental first step in resolving data silos and duplicates is to establish a single, unique identifier (a global customer ID or Golden Record ID) for each distinct customer entity. This ID acts as a primary key that can be stored in all downstream systems (including Salesforce) to provide referential integrity. This allows systems to accurately link their records back to the master record, solving the "clear identification" problem.
✅ Why C is Correct:
Before a clean master database can be established, the existing duplicate data within each system (including Salesforce) must be cleansed. A dedicated data deduplication tool is necessary to identify, merge, and purge duplicate records at scale across all systems. This is a critical cleansing step that cannot be skipped.
✅ Why E is Correct:
The ultimate goal of an MDM initiative is to create a master database that serves as the authoritative system of truth for customer data. All other systems, including Salesforce, become "spoke" systems that consume this clean, mastered data. This architecture directly resolves the issues of inconsistent presentation and duplication by ensuring every system syncs from one central, clean source.
❌ Why B is Incorrect (Use Salesforce CDC):
Change Data Capture (CDC) is a tool for streaming changes out of Salesforce. The problem states that duplicates exist across many systems, and Salesforce is just one of them. Using CDC would only push potentially dirty data from Salesforce to other systems, exacerbating the problem. It does nothing to clean the data or create a master source.
❌ Why D is Incorrect (Duplicate records and two-way sync):
This is the exact opposite of a correct solution. Duplicating records and creating a complex web of two-way syncs would guarantee data inconsistency, create endless sync conflicts, and make the duplication problem exponentially worse. Data should flow from a single master out to other systems, not be synced bi-directionally between peers.
Reference:
This solution outlines a standard MDM implementation pattern:
1) Cleanse existing data (C)
2) Establish a unique identity framework (A)
3) Create a central master system and hub-and-spoke integration model (E)
That's the last free question
You've seen the free 25% of every topic (64 of 257 questions). Get complete access for every question, explanation and the timed exam simulator.
Our timed 2026 Salesforce Platform Data Architect practice test mirrors the format, number of questions and time limit of the official exam.
The #1 challenge isn't just knowing the material, it's managing the clock. The simulation builds your speed and stamina, so you walk in knowing exactly what to expect.