Salesforce Certified Platform Data Architect Free Sample Questions

Description

Covers standard and custom object data persistence, scalable data model design, large data volume performance and archiving, data migration techniques, governance, and consolidated data management.

20 free sample questions227 in the full practice test Other version: Plat-Arch-201(134)

Try simulator

DATA-ARCHITECT Sample Questions

  1. Question 1

    Advanced

    Data Modeling / Database Design · Scalable Data Model Design for Consolidation

    A global MedTech company, Vitality Health, is consolidating three regional Salesforce orgs (AMER, EMEA, APAC) into a single global org. Each region has a custom Patient__c object, but the data models have critical differences in fields, validation rules, and relationships to a custom Medical_Device__c object. The architect must design a unified, scalable data model that complies with GDPR and HIPAA, tracks device service history efficiently, and supports an anticipated volume of over 80 million patient records within two years.

    Key Requirements:

    • A single, global representation of a Patient.
    • Strict compliance with regional data privacy laws (GDPR/HIPAA).
    • A scalable many-to-many relationship between Patients and their assigned Medical Devices, including a detailed service history for each device assignment.
    • High performance for patient record retrieval and reporting.

    Which data model should the architect recommend to meet these complex requirements?

    Answer and explanation

    Correct answer: A

    This is the optimal solution. Person Accounts provide a standard, scalable way to represent individuals, combining Account and Contact functionality, which is ideal for a Patient model. A junction object (Device_Assignment__c) correctly models the many-to-many relationship and can hold rich details like service history. Record types on the Person Account effectively manage regional variations in layouts and processes, while standard field encryption and security features can be leveraged for GDPR/HIPAA compliance.

  2. Question 2

    Intermediate

    Salesforce Data Management · Record Locking and Data Skew

    Nimbostratus Solutions has a custom object Project__c with over 50 million records, which is the child in a master-detail relationship to the standard Account object. A nightly batch job that updates a Status__c field on a large subset of Project__c records is frequently failing with UNABLE_TO_LOCK_ROW errors. Investigation reveals that many of the updated Project__c records are children of a few very large Accounts.

    What is the most effective approach to mitigate these locking errors during the batch update?

    Answer and explanation

    Correct answer: B

    This is the recommended best practice for mitigating lock contention caused by parent-child data skew. By ordering the child records by their parent ID (AccountId), the batch job processes all children for a single parent sequentially. This prevents different parallel batches from attempting to lock the same parent Account record simultaneously, thus avoiding the UNABLE_TO_LOCK_ROW error.

  3. Question 3

    IntermediateMultiple answers

    Large Data Volume Considerations · Big Objects and Querying

    An e-commerce company, ShopSphere, needs to store customer clickstream data and IoT device events in Salesforce. The anticipated data volume is several billion records per year. The data must be queryable for large-scale trend analysis and machine learning models, but it does not need to support standard sharing rules, triggers, or workflows. The solution must be native to the Salesforce platform.

    Which TWO Salesforce technologies should an architect recommend for storing and querying this data? (Select TWO)

    Answer and explanation

    Correct answers: B, E

    Big Objects are specifically designed to store and manage massive data volumes (billions of records) on the Salesforce platform. They are ideal for archival, event monitoring, or historical data that doesn't require the full feature set of standard or custom objects.

    Async SOQL is the primary mechanism for running queries against Big Objects. It is designed to handle the massive scale of data stored in Big Objects by running the query in the background and storing the results in a target object.

  4. Question 4

    Beginner

    Data Migration · Relationship Mapping with External IDs

    A consultant is migrating 500,000 Contact records into a Salesforce org where 10,000 corresponding Account records already exist. The source system provides a unique 'Legacy_Account_ID__c' on each Account. The Contact CSV file contains this same legacy ID to identify the parent Account.

    What is the most efficient method to establish the relationship between the imported Contacts and the existing Accounts using Data Loader?

    Answer and explanation

    Correct answer: B

    This is the correct and most efficient best practice. By marking Legacy_Account_ID__c as an External ID, Data Loader can use this unique identifier to look up the parent Account record and automatically populate the AccountId lookup field on the Contact object. This avoids the need for manual ID mapping and is the primary purpose of External ID fields in data migration.

  5. Question 5

    Beginner

    Data Governance · Platform Encryption

    True or False: Once Salesforce Shield Platform Encryption is enabled for a field, users with the 'View Encrypted Data' permission can view the plaintext value in reports and list views without any further configuration.

    Answer and explanation

    Correct answer: B

    This is correct. The 'View Encrypted Data' permission allows users to see the unmasked data on record detail pages. However, the data remains masked in reports, list views, search results, and other areas. Encryption significantly impacts how data can be used in filters and queries.

  6. Question 6

    Intermediate

    Master Data Management · Data Survivorship

    FinServe Inc. is implementing a Master Data Management (MDM) strategy for their customer data, which is sourced from their Salesforce org, a marketing automation platform, and a billing system. The goal is to create a 'golden record' for each customer in Salesforce. The billing system is considered the most reliable source for customer address information, while the marketing platform has the most up-to-date email addresses.

    Which MDM concept should be configured to ensure the final golden record uses the address from the billing system and the email from the marketing platform?

    Answer and explanation

    Correct answer: C

    Data Survivorship Rules are the specific configurations that determine which data from which source system should be preserved in the final 'golden record' when duplicates are merged. In this case, a rule would be set to prioritize the 'address' field from the billing system and the 'email' field from the marketing platform.

  7. Question 7

    Intermediate

    Data Modeling / Database Design · Data Skew

    A data architect at Global Motors has identified significant account data skew on their Service_Request__c custom object, where a few global fleet accounts own millions of service request records. This is causing slow report performance and record locking issues during data updates. The relationship to the Account is a lookup.

    Which is the most appropriate initial step to mitigate the performance impact of this lookup skew?

    Answer and explanation

    Correct answer: D

    This is a common and effective strategy for mitigating lookup skew. By creating multiple 'bucket' or 'sub-accounts' under the main fleet account and distributing the child records among them, you reduce the number of children linked to any single parent record. This breaks up the skew and significantly reduces lock contention and improves performance.

  8. Question 8

    Intermediate

    Salesforce Data Management · Data Quality and Duplicate Management

    A company is experiencing low user adoption of their Salesforce CRM due to poor data quality. A data quality assessment reveals high rates of duplication, incompleteness, and inaccuracy in the Lead and Contact objects. The Data Architect has been tasked with recommending a solution to improve data quality at the point of entry.

    Which declarative feature should be the primary recommendation to prevent the creation of new duplicate records?

    Answer and explanation

    Correct answer: B

    This is the standard, declarative feature set designed specifically for identifying and managing duplicates. A Matching Rule defines how to identify duplicates (e.g., based on fuzzy name and exact email), and a Duplicate Rule determines what to do when a duplicate is found (e.g., block creation or allow with an alert). This is the primary tool for preventing new duplicates.

  9. Question 9

    Advanced

    Large Data Volume Considerations · Skinny Tables

    Apex Innovations runs complex reports on their Opportunity and OpportunityLineItem objects, involving numerous formula fields and joins across 5 related custom objects. With over 20 million Opportunity records, these reports are frequently timing out. The most commonly used fields in the report filters and columns are spread across these objects.

    What Salesforce feature should the architect propose to specifically address this report performance issue?

    Answer and explanation

    Correct answer: D

    Skinny tables are the ideal solution for this scenario. They are custom database tables that contain a subset of fields from a standard or custom object, including fields from related objects. By combining fields from Opportunity, OpportunityLineItem, and the related custom objects into a single, denormalized table, Salesforce can avoid expensive joins at runtime, dramatically improving report and query performance.

  10. Question 10

    Advanced

    Data Migration · Large Scale Migration Strategy

    Quantum Corp, a large manufacturing firm, is migrating its legacy ERP data into a new Salesforce implementation. The migration involves approximately 100 million records across 15 related objects, including Account, Product2, Asset, and several custom objects for Work_Order__c and Maintenance_Plan__c. The business has mandated a maximum downtime window of 12 hours over a single weekend for the final data cutover.

    Constraints & Requirements:

    • The legacy system must remain operational until the final cutover begins.
    • Data integrity and all complex relationships must be perfectly preserved.
    • The migration must be completed within the 12-hour window.
    • Performance of the new org must not be degraded post-migration.

    Which data migration strategy should the architect propose?

    flowchart TD subgraph Pre-Cutover Phase A[Extract & Transform Legacy Data] --> B{Initial Bulk Load} B --> C[Suspend Automation & Sharing Rules] C --> D[Load Parent Objects e.g., Accounts] D --> E[Load Child Objects e.g., Assets] end subgraph Cutover Window (12 hours) F[Legacy System Offline] --> G{Delta Load} G --> H[Run Validation Scripts] H --> I[Re-enable Automation & Sharing Rules] I --> J[Perform Sharing Recalculation] end subgraph Post-Cutover K[New Salesforce Org Live] end E --> F J --> K
    Answer and explanation

    Correct answer: C

    This is the correct and standard approach for large-scale migrations with tight downtime constraints. By pre-loading the majority of the data beforehand, the work performed during the critical 12-hour window is minimized to only the delta. Deferring sharing calculations is a key performance optimization that saves significant time during the load process, allowing the recalculation to happen after the data is in place.

Register free for 10 more questions

Or unlock all 227 DATA-ARCHITECT questions with explanations, timed mode and flashcards.