Tooling API

Explanation:

The Tooling API is specifically designed for interacting with Salesforce development and testing environments, making it the best choice for retrieving code coverage and test results.

Why Tooling API?

Provides access to Apex test execution results, including code coverage metrics.
Can query objects like ApexTestResult, ApexCodeCoverage, and ApexTestQueueItem.
Ideal for CI/CD integrations and custom monitoring tools (like the Java app in question).

Why Not the Other Options?

A) SOAP API – General-purpose but not optimized for accessing test results and coverage data.
B) Analytics REST API – Used for Einstein Analytics, not Apex testing metrics.
C) Metadata API – Used for deploying and retrieving metadata, not runtime test data.

Key Reference:
Salesforce Tooling API Documentation

Relevant Objects:
ApexTestResult – Test execution status.
ApexCodeCoverage – Code coverage percentages.
ApexTestQueueItem – Queued test runs.

Implementation Example (Tooling API Query for Test Results):

SELECT Id, Outcome, MethodName FROM ApexTestResult WHERE AsyncApexJobId = 'JobId'

SELECT NumLinesCovered, NumLinesUncovered FROM ApexCodeCoverage WHERE ApexClassOrTriggerId = 'ClassId'

This makes the Tooling API the clear choice for integrating test coverage reporting into a custom Java application.

Use Bulk API to process jobs in parallel mode.

Explanation

This question addresses the crucial topic of data migration performance when moving large volumes of data from a legacy CRM into Salesforce, as part of a transformation journey. The key requirement is to optimize the data load performance. The recommended solution must leverage the most efficient native Salesforce integration tool specifically designed for high-volume data operations, which requires understanding the different processing modes available.

Correct Option: ✅

A. Use Bulk API to process jobs in parallel mode.
The Bulk API is the foundational technology designed by Salesforce for loading or querying a large number of records asynchronously. Using the parallel mode maximizes throughput by allowing multiple batches of data to be processed concurrently, significantly reducing the overall data migration time. This is the standard and most performant approach for high-volume data migration that requires optimization.

Incorrect Option: ❌

B. Contact Salesforce support to schedule performance load.
While Salesforce support can offer guidance or assist with very specific, complex performance issues, the standard, architecturally sound solution for optimizing a self-managed data load is to leverage the platform's features, like the Bulk API. Relying on Salesforce support for a basic operational optimization is not the primary approach an architect would recommend to meet the requirement.

C. Use Bulk API to process jobs in serial mode.
The Bulk API in serial mode processes one batch at a time, preventing potential database contention and locking issues. However, serial mode is significantly slower than parallel mode and is typically only used as a fallback when parallel mode results in high contention errors, not as the primary approach to optimize and maximize data load performance.

D. Use Bulk API to process jobs in high performance mode.
The term "high performance mode" is not a standard, documented setting or option for the Salesforce Bulk API. The available and supported processing modes are Parallel and Serial. Therefore, this option refers to a non-existent feature and is technically incorrect in the context of official Salesforce integration architecture.

Reference:
Salesforce Bulk API Documentation
“The Bulk API is based on REST principles and is optimized for loading or deleting large sets of data. You can use it to insert, update, upsert, or delete many records asynchronously by submitting batches which are processed in the background.”
Introduction to Bulk API 2.0 and Bulk API
Work with Batches

Determine data access prevention requirements, then identify system constraints.

Explanation:

Before recommending a solution to prevent former employees from accessing Salesforce, the architect must understand the business and technical requirements that drive the solution. This includes knowing what data access needs to be blocked, any frequency requirements for syncing deactivations, and potential system constraints that may affect implementation. Proper assessment ensures the chosen integration method is both secure and efficient.

Correct Option:

✅ D. Determine data access prevention requirements, then identify system constraints.
The primary goal is to prevent ex-employees from accessing Salesforce, so understanding data access prevention requirements is essential first.
After identifying the requirements, the architect should review system constraints such as API limits, middleware capabilities, or batch processing schedules to ensure the solution can be implemented reliably.
This approach ensures both security compliance and practical feasibility before implementing an integration.

Incorrect Options:

❌ A. Determine inbound integration requirements, then identify frequency.
While knowing inbound integration details is useful for syncing HR data, this does not address the core requirement, which is preventing access to data. Focusing solely on integration ignores the security aspect.

❌ B. Determine data access prevention requirements, then identify frequency.
Identifying frequency before assessing system constraints may lead to a solution that fails due to technical limitations like API limits or processing delays. System constraints are critical to practical implementation.

❌ C. Determine data volume requirements, then identify the loading schedule.
Data volume and loading schedules are relevant for bulk data operations, but this question focuses on access control, not mass data transfer. This approach does not address the security requirement.

Reference:
Salesforce Security Guide
Integration Patterns Overview

Request-Reply: Enhanced External Services invokes a REST API.

Explanation

A Lightning flow requires real-time, synchronous retrieval of user preferences from an external REST service when a button is clicked. The integration must be low-code, support OpenAPI 2.0 definitions, handle simple Boolean/string responses, and return data immediately into the flow for conditional logic—favoring a request-reply pattern with declarative API invocation.

✅ Correct Option: C – Request-Reply: Enhanced External Services invokes a REST API
Uses Enhanced External Services to import OpenAPI 2.0 JSON directly into Salesforce.
Enables no-code registration of the REST endpoint with named credentials for security.
Allows flow to invoke the service synchronously and capture Boolean/string responses instantly.
Returns data in real-time for use in screen elements or decision logic within the same flow.

❌ Incorrect Option: A – Fire and Forget: Process-driven platform events publishes events on Salesforce Event Bus
One-way asynchronous pattern—cannot return response to the flow.
No mechanism to receive or display external data in real-time.
Unsuitable for user-triggered, interactive preference checks.

❌ Incorrect Option: B – Remote Call-In: Salesforce REST API with REST Composite Resources
Describes inbound integration into Salesforce—not calling out to external systems.
REST Composite is for batch operations within Salesforce, not external callouts.
Wrong direction and irrelevant to the requirement.

❌ Incorrect Option: D – Data Virtualization: Salesforce Connect map data external REST data in external objects
Designed for virtual data access via External Objects—not ideal for transient preference checks.
Requires OData, not native REST/OpenAPI; adds unnecessary schema mapping.
Data appears as records, not suitable for real-time flow variable assignment.

📚 Reference:
Enhanced External Services
Invoke External Service from Flow

Use request and reply.

Explanation

This is a real-time, synchronous process where the support agent cannot complete the transaction without an immediate response from the core banking system. The agent creates a record in Salesforce and must wait to receive the new bank account ID from the external system to provide it to the customer. The integration pattern must support this two-way, immediate communication directly within the user's transaction.

✅ Correct Option

D. Use request and reply.
This pattern is ideal because it facilitates a direct, real-time call from Salesforce to the core banking system. When the agent saves the record, Salesforce sends a request (a callout) containing the account data. The banking system processes this, generates the new account ID, and sends it back in the reply. This allows the agent to receive and provide the new ID to the customer immediately within the same interaction, which is a critical business requirement.

❌ Incorrect Options

A. Use streaming API to generate push topic.
This is a publish-subscribe pattern designed for broadcasting notifications to listening clients, not for processing transactions. It is one-way and asynchronous, meaning the agent would not receive the bank account ID back in real-time to provide to the customer, breaking the required business process.

B. Use outbound message.
Outbound messages are a type of one-way, fire-and-forget notification triggered by a workflow. They are asynchronous and do not support receiving a response directly back into the Salesforce record. The banking system could not send the new account ID back through this channel, making it unsuitable for this real-time requirement.

C. Use salesforce platform event.
Platform events are excellent for decoupled, asynchronous event-driven architectures. While the banking system could subscribe to the event, there is no built-in mechanism for it to synchronously reply with the new account ID. The agent would be left waiting for a separate process to update the record, which is not real-time.

📚 Reference
For official guidance, refer to the Salesforce Architects - Integration Patterns documentation, specifically the "Remote Process Invocation — Request and Reply" pattern. This pattern is designed for scenarios where an immediate response from an external system is required to continue a process, which perfectly matches this use case.