Plat-Arch-201 — Salesforce Certified Platform Data Architect

Full question text, answer options, and explanations for this practice set — a spoiler-free alternative is the interactive quiz above for scored, shuffled practice.

1. 1. A company must comply with GDPR and needs to automatically delete personal data records 24 months after a customer's last interaction. Which Salesforce feature should a Data Architect recommend?

   • A. Workflow Rules with time-based triggers
   • B. Scheduled Flows with date-based criteria(correct)
   • C. Data Retention Policies using the Data Archive feature
   • D. Apex Batch jobs triggered by Platform Events

   Explanation: Scheduled Flows (formerly Scheduled Process Builder actions) can be configured to run on a date-relative basis and delete or anonymize records that meet GDPR retention criteria. This is the declarative, maintainable approach recommended for data retention automation without custom code.

2. 2. Standard Field History Tracking in Salesforce has which of the following limitations?

   • A. It can track up to 20 fields per object and retains history for 18 months(correct)
   • B. It can track up to 10 fields per object and retains history for 12 months
   • C. It can track up to 20 fields per object and retains history indefinitely
   • D. It can track up to 50 fields per object and retains history for 24 months

   Explanation: Standard Field History Tracking supports up to 20 fields per object and retains history for 18 months. For longer retention, Salesforce Shield's Field Audit Trail extends this to up to 60 fields and up to 10 years of retention.

3. 3. A healthcare company storing PHI in Salesforce needs field-level encryption that also allows search and sorting on encrypted fields. Which Salesforce feature supports this requirement?

   • A. Classic Encryption (encrypted custom fields)
   • B. Shield Platform Encryption with Deterministic encryption scheme(correct)
   • C. Shield Platform Encryption with Probabilistic encryption scheme
   • D. External key management via Bring Your Own Key (BYOK)

   Explanation: Shield Platform Encryption with the Deterministic encryption scheme encrypts field data while still supporting equality searches, SOQL filters, and sorting. Probabilistic encryption is more secure but does not support search. Classic Encryption uses masking and does not support search on encrypted data.

4. 4. A Data Architect is designing a data classification framework for a Salesforce org containing PII. Which two actions are recommended best practices? (Choose 2)

   • A. Assign a Data Sensitivity Level to each custom field containing PII(correct)
   • B. Use the Compliance Categorization field to tag PII fields for regulatory reporting(correct)
   • C. Store all PII in a separate external database and use Salesforce Connect for access
   • D. Create a custom picklist field on every object to manually flag PII records

   Explanation: Salesforce provides built-in Data Sensitivity Level (e.g., Public, Internal, Confidential, Restricted) and Compliance Categorization (e.g., PII, HIPAA, GDPR) fields on custom and some standard fields. Using these metadata attributes enables automated reporting and integration with Shield features. External databases and manual custom fields are not the recommended approach.

5. 5. An org has 50 million Contact records. A nightly batch process frequently times out when running SOQL queries without filters on the Contact object. The most appropriate solution for the Data Architect is:

   • A. Request Salesforce to create a custom index on the queried field(correct)
   • B. Partition the Contact object using Record Types to reduce query scope
   • C. Enable the 'Improve Performance of Similar SOQL Queries' org preference
   • D. Switch from SOQL to SOSL for all batch queries

   Explanation: For Large Data Volume (LDV) objects with millions of records, custom indexes created by Salesforce Support are the primary solution to improve SOQL query performance. Custom indexes allow selective queries on non-selective fields. Partitioning via Record Types does not reduce actual query scope in the database. SOSL is for full-text search and not suitable for batch processing patterns.

6. 6. A company's legal team requires an audit log of all administrator configuration changes in Salesforce for the past 6 months. Which standard feature provides this?

   • A. Login History
   • B. Setup Audit Trail(correct)
   • C. Event Monitoring
   • D. Debug Logs

   Explanation: Setup Audit Trail tracks changes made in Setup (configuration changes, user management, security settings, etc.) for the last 180 days (6 months). Login History tracks login events. Event Monitoring (Shield) tracks user activity like API calls and record views. Debug Logs track Apex execution, not admin changes.

7. 7. A Data Architect needs to implement a data quality strategy for an org receiving data from multiple source systems via API integrations. Which two approaches should be included? (Choose 2)

   • A. Define Validation Rules on critical fields to enforce format and business constraints at the platform layer(correct)
   • B. Use Duplicate Rules with Matching Rules to prevent and report duplicate records during upsert operations(correct)
   • C. Rely solely on source system validation to ensure data quality before Salesforce receives the data
   • D. Create a trigger to reject all records that do not match a predefined pattern

   Explanation: Defense-in-depth data quality requires both platform-layer validation (Validation Rules enforce business constraints at the point of entry regardless of source) and duplicate prevention (Duplicate Rules with Matching Rules detect and handle duplicate records during API upsert operations). Relying solely on source systems is fragile, and triggers add complexity without declarative benefits when the platform features can handle these requirements.

8. 8. A Salesforce org has an Account object with 30 million records and users frequently filter by a custom text field called 'Region_Code__c'. Queries on this field are timing out. The Data Architect recommends:

   • A. Create a Roll-Up Summary field to aggregate the Region_Code__c values
   • B. Request Salesforce Support to create a custom index on Region_Code__c(correct)
   • C. Create a Skinny Table on the Account object
   • D. Add Region_Code__c to the search layout and enable SOSL queries

   Explanation: Custom indexes created by Salesforce Support allow selective queries on fields in LDV objects. For a custom text field like Region_Code__c with relatively few distinct values (low cardinality), a custom index can dramatically improve query performance. Skinny tables improve join performance but require a log of frequently queried fields. SOSL does not help with SOQL-based report/query timeouts.

9. 9. What is the primary purpose of a Skinny Table in Salesforce?

   • A. To store a subset of frequently queried fields from a large object, improving read performance by eliminating joins(correct)
   • B. To archive old records from a large object to reduce storage costs
   • C. To enforce field-level security on sensitive data in large tables
   • D. To replicate data from external systems into Salesforce for reporting

   Explanation: Skinny Tables are internal Salesforce database tables that contain a subset of frequently accessed fields from a standard or custom object. They eliminate costly joins in the underlying database, significantly improving query performance for reports and list views on LDV objects. They are created and managed by Salesforce Support.

10. 10. A company needs to model a many-to-many relationship between Products and Campaigns in Salesforce. What is the recommended approach?

    • A. Create a Lookup field on Product pointing to Campaign and another Lookup on Campaign pointing to Product
    • B. Create a Junction Object with two Master-Detail relationships, one to Product and one to Campaign(correct)
    • C. Use a Text Area (Long) field on Product to store comma-separated Campaign IDs
    • D. Enable the Many-to-Many Relationship feature in Object Manager

    Explanation: Many-to-many relationships in Salesforce are modeled using Junction Objects — a custom object with two Master-Detail relationships pointing to the two related objects. This enables roll-up summaries, cascading deletes, and proper relationship traversal in SOQL. Storing IDs in text fields breaks relational integrity and is an anti-pattern.

11. 11. A Data Architect is reviewing SOQL queries for performance in a high-volume org. Which two query patterns should be flagged as problematic? (Choose 2)

    • A. Using a leading wildcard in a LIKE clause: WHERE Name LIKE '%Corp'(correct)
    • B. Filtering on an indexed field with high selectivity: WHERE ExternalId__c = '12345'
    • C. Using a negative operator in a filter: WHERE Status__c != 'Closed'(correct)
    • D. Using a date literal: WHERE CloseDate = THIS_MONTH

    Explanation: Leading wildcards (LIKE '%term') prevent index usage, causing full table scans on LDV objects. Negative operators (!=, NOT IN, NOT LIKE) are non-selective and cannot use indexes efficiently. Filtering on high-selectivity indexed fields and using date literals are both performant query patterns supported by Salesforce indexes.

12. 12. Cross-object formula fields in Salesforce can traverse a maximum of how many relationships?

    • A. 3 levels
    • B. 5 levels(correct)
    • C. 10 levels
    • D. Unlimited levels

    Explanation: Cross-object formula fields can reference fields on related objects by traversing up to 5 levels of Master-Detail or Lookup relationships. Exceeding this limit requires Apex or Flow-based solutions to surface data from deeply nested objects.

13. 13. An org uses a polymorphic Lookup field (WhoId on Task) which can reference either Contact or Lead. A data architect needs to query all Tasks linked to Contacts. Which SOQL clause is required?

    • A. WHERE WhoId.Type = 'Contact'
    • B. WHERE Who.Type = 'Contact'
    • C. TYPEOF Who WHEN Contact THEN ... END(correct)
    • D. WHERE RecordType.Name = 'Contact'

    Explanation: SOQL supports the TYPEOF clause for polymorphic relationship fields like Who (WhoId) and What (WhatId) on Activity objects. The syntax 'SELECT TYPEOF Who WHEN Contact THEN ...' allows querying and retrieving different fields based on the referenced object type. Using '.Type' in a WHERE clause is not valid SOQL syntax for polymorphic fields.

14. 14. A company integrating data from three source systems wants to use Salesforce as the system of record for Account data. Each source system has its own unique account identifier. Which Salesforce feature enables reliable upsert operations to prevent duplicate Accounts?

    • A. Workflow Rules with field update actions
    • B. External ID fields with upsert API calls(correct)
    • C. Duplicate Rules with custom matching algorithms
    • D. Person Account configuration

    Explanation: External ID fields marked as External ID allow the Bulk API and SOAP/REST API upsert operations to match records by an external system's identifier. If a record with the same External ID exists, it is updated; otherwise, a new record is inserted. This is the standard MDM pattern for avoiding duplicates during integration-based data loads.

15. 15. A Duplicate Rule is configured with the action 'Allow' and 'Alert'. When a user attempts to save a record that matches a duplicate, what happens?

    • A. The record is blocked and cannot be saved
    • B. The record is saved and the user receives a warning but is not blocked(correct)
    • C. The record is merged automatically with the matching duplicate
    • D. The record is quarantined in a duplicate holding queue

    Explanation: When a Duplicate Rule action is set to 'Allow' with 'Alert', users see a warning message identifying potential duplicates but are permitted to save the record regardless. The 'Block' action prevents saving. Salesforce does not automatically merge records; merging requires manual action or custom automation.

16. 16. A Data Architect is designing a Matching Rule for the Account object. Which two standard matching criteria are available in Salesforce Matching Rules? (Choose 2)

    • A. Exact match on a specified field value(correct)
    • B. Fuzzy match using the Edit Distance algorithm for name fields(correct)
    • C. Phonetic match using Soundex for address fields
    • D. Machine learning-based semantic similarity matching

    Explanation: Salesforce standard Matching Rules support Exact match (field values must match exactly) and Fuzzy match (using algorithms like Edit Distance / Levenshtein distance for name similarity). Phonetic matching is not a standard out-of-box option in Matching Rules, and ML-based matching requires third-party solutions.

17. 17. An enterprise uses Salesforce as its MDM hub. The 'golden record' for each customer must be maintained when merging duplicate Accounts. Which statement about the Salesforce merge functionality is true?

    • A. The merge process always retains all field values from the master record without exception
    • B. The user can select which field values to retain from any of the duplicate records during the merge wizard(correct)
    • C. Only records created by the same user can be merged
    • D. Merging Accounts automatically merges all related Contacts into one

    Explanation: During the Account (or Contact/Lead) merge process, users designate one record as the master (whose ID and system fields are retained) but can individually select which field values to keep from any of the merged records. Related records (Contacts, Opportunities, Cases, etc.) are reparented to the master record. Contacts are not merged — they are reparented.

18. 18. A company needs to track individual consumers (B2C) in Salesforce alongside business accounts. Contacts associated with a business account should not be mixed with individual consumer records. What feature should the Data Architect recommend?

    • A. Record Types on the Contact object
    • B. Person Accounts(correct)
    • C. Individual object
    • D. Lead conversion for all individual consumers

    Explanation: Person Accounts in Salesforce merge Account and Contact into a single record type, allowing individual consumers (B2C) to be represented as Accounts without a separate Contact. This keeps B2C individuals separate from B2B business accounts while leveraging the full Account relationship model. The Individual object is used for marketing consent tracking, not as a primary data model for consumers.

19. 19. A multi-org Salesforce implementation needs an enterprise MDM strategy. Which two design principles should guide the architect? (Choose 2)

    • A. Designate a single authoritative system of record for each data domain to avoid conflicting updates(correct)
    • B. Use bi-directional sync between all systems for every field to keep data consistent everywhere
    • C. Assign ownership of Customer data to the CRM and Product data to ERP, matching systems to their domain strengths(correct)
    • D. Replicate all data from every system into Salesforce so that Salesforce becomes the sole system of record for everything

    Explanation: MDM best practice assigns a single authoritative system of record per data domain to prevent conflicting updates and reconciliation challenges. Domain-based ownership (CRM owns customer data, ERP owns product/financial data) aligns each system with its core strength. Bi-directional sync for all fields creates circular update loops and conflict resolution nightmares. Centralizing all data in Salesforce ignores the specialized capabilities of other enterprise systems.

20. 20. Which Salesforce tool is recommended for initial large-scale data loads of millions of records from an external system?

    • A. Data Import Wizard
    • B. Bulk API 2.0 via Data Loader(correct)
    • C. REST API with synchronous calls
    • D. Manual CSV import via Setup

    Explanation: Bulk API 2.0 (accessed via Data Loader or direct API calls) is optimized for processing large volumes of records asynchronously. It can handle millions of records efficiently in batch jobs with higher governor limits than the standard REST/SOAP API. Data Import Wizard supports only up to 50,000 records. REST API with synchronous calls has lower per-transaction limits and is not suited for millions of records.

21. 21. During a data migration, a Data Architect needs to load Opportunities before loading related OpportunityLineItems. This requirement reflects which data migration principle?

    • A. Parent-before-child loading order
    • B. Parallel batch loading for efficiency
    • C. Using External IDs as foreign keys for child records
    • D. Both A and C are required principles(correct)

    Explanation: Data migration must follow parent-before-child loading order because child records (OpportunityLineItems) require the parent Opportunity ID to exist first. Additionally, using External IDs on parent records as foreign keys in child record loads allows the Bulk API upsert to resolve parent-child relationships without needing to look up Salesforce IDs separately. Both principles apply together.

22. 22. A Data Architect is planning a migration of 5 million Account records. Which two pre-migration steps are critical for a successful outcome? (Choose 2)

    • A. Deduplicate and cleanse source data before loading to minimize duplicates in Salesforce(correct)
    • B. Perform a pilot load of 1,000-10,000 records to validate mappings and transformations(correct)
    • C. Disable all Validation Rules and triggers during the full migration load, then re-enable afterward
    • D. Load all 5 million records at once to minimize migration window time

    Explanation: Pre-migration data cleansing and deduplication prevents downstream data quality issues that are expensive to fix post-migration. Pilot loads with a small representative sample validate field mappings, transformation logic, and error rates before committing to a full load. While disabling Validation Rules is sometimes done for migrations, it risks loading invalid data and is not universally recommended as a 'critical step'; doing a pilot load is the better safeguard. Loading all records at once without testing is a high-risk approach.

23. 23. A Salesforce org needs to display real-time inventory data from an SAP system without replicating the data into Salesforce. Which integration approach is most appropriate?

    • A. Nightly Bulk API load from SAP to a custom Inventory object in Salesforce
    • B. Salesforce Connect with an OData 4.0 External Data Source pointing to the SAP system(correct)
    • C. Platform Events published from SAP and consumed by Salesforce Flow
    • D. Salesforce Data Loader scheduled every 15 minutes from SAP

    Explanation: Salesforce Connect (formerly Lightning Connect) using External Objects and an External Data Source with OData 4.0 protocol allows Salesforce to display data from external systems in real time without storing it in Salesforce. This is ideal for large, frequently changing datasets like inventory that should remain in the system of record (SAP). Platform Events are for event-driven messaging, not read-only data display.

24. 24. A Report Type in Salesforce defines the relationship between objects used in a report. When a Report Type is configured as 'A with or without B', what does this mean for the records displayed?

    • A. Only records from object A that have at least one related B record are shown (inner join)
    • B. All records from object A are shown, regardless of whether they have related B records (left outer join)(correct)
    • C. Only records from object B that have a related A record are shown
    • D. Records from both A and B are shown even if they have no relationship to each other

    Explanation: 'A with or without B' is equivalent to a left outer join: all records from the primary object (A) are included in the report, and related B records are shown when they exist. This contrasts with 'A with B', which is an inner join showing only A records that have at least one related B record. Understanding this distinction is critical for designing accurate report types.

25. 25. A company wants to use CRM Analytics (formerly Tableau CRM / Einstein Analytics) for advanced data analysis. Which two capabilities differentiate CRM Analytics from standard Salesforce Reports? (Choose 2)

    • A. CRM Analytics can connect to and analyze data from external data sources outside Salesforce(correct)
    • B. CRM Analytics supports predictive analytics and AI-powered insights using Einstein Discovery(correct)
    • C. CRM Analytics can display up to 2,000 records per chart, matching standard report limits
    • D. CRM Analytics dashboards can only be built by System Administrators

    Explanation: CRM Analytics distinguishes itself from standard Reports by: (1) supporting external data connectors (S3, Snowflake, Redshift, etc.) allowing analysis of non-Salesforce data; (2) integrating with Einstein Discovery for AI-powered predictions, recommendations, and statistical insights within dashboards. Standard Reports are limited to Salesforce data and do not offer predictive analytics. CRM Analytics can visualize millions of rows, not just 2,000, and dashboards can be built by any user with the Analytics permission.