Free PLAT-ARCH-201 Practice Test Questions and Answers (2026)

The Bulk API is designed specifically for asynchronously querying, inserting, updating, or deleting large data sets, including millions of records. It processes data in batches in the background, which avoids the transaction and governor limit timeouts associated with synchronous APIs like the SOAP API. For extracting 1,000,000 records, the Bulk API is the most reliable and performant method recommended by Salesforce, ensuring the job completes successfully without timing out.

A. The SOAP API is synchronous and not designed for large data volumes. A query for 1,000,000 records would almost certainly fail due to query timeouts.

C. GZIP compression reduces the payload size, which improves network transfer speed. While it is a useful feature often used with the Bulk API, it does not by itself solve the server-side processing timeouts that the Bulk API's asynchronous nature addresses.

D. Batch Apex is used for processing large data volumes within Salesforce. It is not the primary tool for exporting data to an external system.

1. Salesforce Developers. (n.d.). Bulk API Developer Guide. "Introduction to the Bulk API". "Bulk API is based on REST principles and is optimized for loading or deleting large sets of data. You can use it to query, insert, update, upsert, or delete a large number of records asynchronously by submitting batches."

2. Salesforce Architects. (n.d.). Architect's Guide to Large Data Volumes. "Data Extraction Strategies". This guide explicitly recommends the Bulk API for extracting large volumes of data from Salesforce. (See section on "API-Based Extractions").

Standard Field History Tracking is limited to a maximum of 20 fields per object. To track 100 fields, a custom audit trail solution is required. This is typically implemented using an Apex trigger on the Opportunity object that fires on update. The trigger logic then populates a custom object. Two common patterns for this custom object are: storing a complete copy (snapshot) of the record whenever it changes (A), or storing individual field changes with their old and new values in a dedicated "Field Change" custom object (B). Both are valid architectural approaches to overcome the platform limit.

C. Analytic Snapshots are used for historical trend reporting by capturing and storing aggregated report results over time, not for granular, transactional field-level auditing.

D. This action is impossible. The Salesforce platform enforces a hard limit of 20 fields per object for standard Field History Tracking.

1. Salesforce Help. (2024). Track Field History for Standard and Custom Objects. "You can select up to 20 standard and custom fields per object to track." This confirms the platform limitation that necessitates a custom solution.

2. Apex Developer Guide. (2024). Trigger Context Variables. The use of Trigger.oldMap and Trigger.newMap within an Apex trigger is the fundamental mechanism that enables a custom audit solution by allowing comparison of old and new field values.

3. Salesforce Architects. (2023). Salesforce Well-Architected - Composable: Platform Capabilities. This resource discusses knowing platform limits and designing custom solutions when those limits are reached. A custom audit trail is a classic example of such a solution.

The Bulk API's serial mode processes batches one at a time, which is specifically designed to prevent record lock contention. The scenario of inserting millions of orders (child records) distributed across various accounts (parent records) presents a high risk of multiple batches trying to update the same parent account simultaneously in parallel mode, causing lock exceptions. Therefore, choosing serial mode is the recommended strategy for a data load with a high potential for parent-child record locking, ensuring the job completes successfully without errors, albeit more slowly.

A. The number of batches in a job does not determine the need for serial mode; the nature of the data and potential for lock contention does.

C. The number of batches per job is a configuration detail, not a reason to choose serial mode over parallel mode.

D. If lock exceptions were already "eliminated and managed" (e.g., by pre-sorting data), parallel mode could be used. Serial mode is chosen precisely because there is a potential for unmanaged lock exceptions.

1. Salesforce Developer Documentation, Bulk API Developer Guide, "Introduction to Processing Batches". The guide states, "Processing jobs in serial mode can minimize lock contention."

2. Salesforce Developer Documentation, Bulk API Developer Guide, "Walkthrough: Process Records in a Job in Serial Mode". This section explicitly recommends serial mode "if you're experiencing lock timeouts when you process jobs in parallel mode."

3. Salesforce Architects, Record-Locking Cheatsheet. This document explains that lock contention occurs when multiple transactions attempt to update the same record or related parent records, a situation that serial mode is designed to mitigate during data loads.

The most effective and efficient solution for systematically monitoring, measuring, and improving data quality in Salesforce is to leverage a specialized third-party tool from the AppExchange. These applications are purpose-built to handle tasks like identifying incomplete records, preventing duplicates, standardizing data, and providing dashboards to track quality metrics over time. Building a custom solution would be time-consuming and complex, while manual reporting is not scalable for ongoing monitoring. AppExchange solutions provide a robust, pre-built framework to address the executives' requirements directly.

B. Generating reports on sample data is a reactive, manual spot-check. It does not provide the continuous, comprehensive monitoring and measurement that is required.

C. While technically possible, building a data quality monitoring system with custom objects and fields is a significant development effort, reinventing functionality readily available in AppExchange apps.

D. Exporting data to an external system addresses analysis but fails to solve the core problem of improving data quality at the source, within Salesforce itself.

1. Salesforce AppExchange. A search for "Data Quality" or "Data Governance" reveals numerous established applications designed for monitoring, cleaning, and managing data within Salesforce.

2. Salesforce Architects, Salesforce Architect's Handbook for Data Management, "Data Governance Framework". This guide often discusses the "Build vs. Buy" decision, where specialized AppExchange packages are recommended for complex, standard needs like data quality management.

3. Trailhead, Data Quality, "Data Management Strategy". This module emphasizes the importance of tools for maintaining data quality, with the AppExchange being the primary source for such tools.

The requirement is to enforce a business rule during a delete operation that is conditional on the user's identity relative to the record owner. Standard sharing and profiles cannot meet this specific conditional logic. Validation rules do not execute on delete operations. Therefore, the only appropriate tool is a "before delete" Apex trigger. The trigger can compare the ID of the current user (UserInfo.getUserId()) with the record's OwnerId. If they do not match, the trigger can prevent the deletion by adding an error to the record using the .addError() method.

B. Setting sharing to Public Read Only would prevent non-owners from editing, which violates a stated requirement that all users can edit all contacts.

C. Removing the delete permission from the profile would prevent users from deleting any contact, including the ones they own, failing the requirement.

D. Validation rules do not fire on record deletion, only on insert and update operations, so they cannot be used to prevent a delete.

1. Apex Developer Guide. (2024). Triggers. "Triggers can be defined for top-level standard objects... and custom objects. They can be set to execute before or after database operations such as insert, update, delete...".

2. Apex Developer Guide. (2024). Triggers and Order of Execution. The documentation on the order of execution explicitly shows that validation rules are not part of the delete transaction steps, while "before delete" triggers are the first step.

3. Salesforce Help. (2024). Validation Rules. "Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record." This confirms their scope is limited to save (insert/update) operations.

Performance testing on the multi-tenant Salesforce platform requires strict governance to protect shared resources. Salesforce mandates that customers must create a formal performance test plan and submit it for approval before execution. This ensures the proposed test does not negatively impact other customers. Furthermore, performance testing is most critical for applications with significant custom code (Apex, Visualforce, LWC) or those that interact with large data volumes (LDV). These are the scenarios most likely to encounter governor limits, slow query performance, or other scalability bottlenecks.

A. Performance testing in production is strictly controlled and generally prohibited unless explicitly approved by Salesforce for very specific scenarios; it is not a mandatory step for all applications.

D. Sandbox performance is not representative of production. Sandboxes have different hardware, data volumes, and configurations, so results cannot be directly extrapolated to the production environment.

1. Salesforce Help, Requesting a Performance Test. This document explicitly states, "Before you run a performance test against your Salesforce org, you must request our approval... Submit your test plan at least two weeks before your planned test."

2. Salesforce Architects, Best Practices for Improving Visualforce Performance, "Performance Testing". This article notes that sandboxes are not performance-matched to production environments.

3. Salesforce Developers, Performance Testing. This guide outlines the process and states, "Salesforce requires that you get approval before you conduct any performance testing on the Salesforce.com service." It also highlights the need to test for LDV scenarios.

Millions of historical records should be summarized or removed from the transactional warehouse. Batch Apex can aggregate data into a custom object, then delete source rows. For long-term retention without consuming data storage, Lightning Platform Data Archive (Big-Object-based archiving feature) off-loads older records while keeping them queryable, eliminating both storage growth and report performance issues.

B. Reporting Snapshots capture max 2,000 rows per run—unsuitable for millions of records.

C. Data Loader is a manual, offline process and not scalable or automated for continual archiving.

1. Apex Developer Guide, Summer ’24, “Example: Archiving Old Data with Batch Apex,” p.918.

2. Salesforce White Paper “Designing Record Archiving & Purge Strategies,” v2, 2021, §4 “Lightning Platform Data Archive.”

3. Salesforce Help Article 000337449, “Reporting Snapshot row limit (2,000 rows).”

The key requirements are consolidating data from multiple Salesforce orgs and applying advanced AI-driven analytics. CRM Analytics (formerly Einstein Analytics) is the Salesforce-native tool designed specifically for these purposes. It includes built-in connectors that can pull data from multiple local and remote Salesforce orgs into a single dataset. Furthermore, its integrated Einstein Discovery capabilities provide the AI-driven analytics and predictive insights that management has requested. This makes it the most comprehensive and fitting solution among the choices.

A. Standard reports and dashboards are limited to a single Salesforce org and cannot consolidate data from multiple orgs.

B. While a third-party tool might work, a native Salesforce solution like CRM Analytics is typically the recommended architectural choice for its deep integration and feature set.

D. A custom Python script is an off-platform solution that would require significant development, maintenance, and security considerations, making it less ideal than the purpose-built platform tool.

1. Salesforce Help, Connect to Data in CRM Analytics, "CRM Analytics connectors let you bring data from external data sources, such as applications, data warehouses, and database services, into CRM Analytics. CRM Analytics provides a prebuilt connector for pulling data from your local Salesforce org and other remote Salesforce orgs."

2. Salesforce Help, Einstein Discovery, "Einstein Discovery augments your business intelligence with statistical modeling and machine learning to identify, surface, and visualize insights into your business data."

Big Objects are a native, low-cost archive store that can hold billions of records and keep them query-able from Salesforce while freeing data storage. Moving cases older than two years into a Big Object via a scheduled batch satisfies the “on-demand” requirement and retains seamless UI access.

Alternatively, surfacing the data by using Salesforce Connect with Heroku External Objects lets Service agents view historical cases in real time without persisting them in core data storage; Bulk API hard-delete then removes the originals from the Case table. Both strategies meet the 2-to-7-year, 5-million-records-per-year scale, and deliver agent visibility with minimal storage cost.

A – Moves data but keeps it inside the org; custom objects count against data storage and won’t scale to tens of millions of rows.

B – Direct database access forces users outside Salesforce UI and lacks native security/sharing; requirement is “available to Service agents” inside SF.

1. Salesforce “Big Objects Developer Guide”, Spring ’24, Section “When to Use Big Objects”.

2. Salesforce “Architect’s Guide to Large Data Volumes”, p.20, “Archive with Big Objects”.

3. Salesforce “Salesforce Connect—OData 4.0 and Heroku External Objects”, Implementation Guide, Chap. 2 “Surfacing External Data”, Example Archive Pattern.

The hub-and-spoke model is a common integration pattern for managing data across multiple systems, including Salesforce orgs. A middleware solution, such as an Enterprise Service Bus (ESB), is the standard tool for orchestrating this pattern. It acts as a central broker, decoupling the hub from the spokes. This allows for centralized management of data transformation, routing, error handling, and monitoring. It provides a scalable and maintainable architecture compared to building numerous point-to-point integrations, which would create tight coupling and become unmanageable as the number of spokes grows.

B. Develop custom APIs to poll the hub org for change data and push into the spoke orgs.

This creates a brittle, point-to-point integration for each spoke, which is not scalable and lacks the orchestration capabilities of middleware.

C. Develop custom APIs to poll the spoke for change data and push into the org.

This reverses the data flow logic of a hub-and-spoke model, where the hub is typically the central system of record.

D. A backup and archive solution that extracts and restores data across orgs.

These tools are designed for data protection and disaster recovery, not for real-time or transactional data synchronization and orchestration.

1. Salesforce Architects. (n.d.). Salesforce Multi-Org Strategy. Salesforce. (This guide discusses patterns for multi-org architectures, where middleware is a key component for implementing hub-and-spoke integrations).

2. Salesforce Architects. (n.d.). Integration Patterns and Practices. Salesforce. (This document describes various integration patterns, highlighting the role of middleware in orchestrating complex data flows between systems, which is the core of the hub-and-spoke model).

3. Gregor Hohpe & Bobby Woolf. (2003). Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison-Wesley Professional. (This foundational academic text on integration describes patterns like Message Broker, which are implemented by middleware to solve the exact problem described).