SF-PD2 Practice Test 17 — 15 Questions

Question 1

A developer is writing a test class for an integration service. Which approach is required to test HTTP callouts without actually making a request to the external system?

Accepted Answer

Use Test.setMock(HttpCalloutMock.class, new MyMock());. The HttpCalloutMock interface is the standard way to simulate HTTP responses in Apex test classes. By implementing this interface and using Test.setMock(), the developer instructs the platform to intercept the callout and return a pre-defined HttpResponse object. This allows for testing various scenarios, such as successful responses and error codes, without relying on external services or network connectivity.

Answer

Use a try-catch block to catch the callout error and bypass the mock.

Answer

Write a dummy endpoint in the external system and point the test to it.

Answer

Use the System.runAs() method to execute the callout as a system user.

Question 2

An organization wants to implement an orchestration layer that manages complex business processes spanning multiple objects and external systems. Which tool is most appropriate for managing stateful, long-running processes?

Accepted Answer

Salesforce Orchestrator to coordinate multi-user and multi-system tasks.. Salesforce Orchestrator is designed specifically for complex, long-running business processes that involve multiple steps, users, and system interactions. Unlike basic flows or triggers, it handles state management across various stages and ensures that dependencies are met, providing a robust, visual way to monitor and coordinate complex workflows that would otherwise require significant custom development to manage state and timing.

Answer

Apex Triggers, by updating a custom 'Status' field on the object.

Answer

Flow Builder using standard autolaunched flows.

Answer

Scheduled Apex jobs running in a nightly batch process.

Question 3

Refer to the exhibit. A developer encounters this error while performing a bulk update of 200 Account records. What is the root cause of this exception?

Accepted Answer

The developer is performing individual DML operations inside a loop instead of bulkifying.. The error indicates that the code is executing DML operations inside a loop rather than performing bulk DML on a collection. In Salesforce, DML operations are limited to 150 per transaction. This is a critical architectural violation because it prevents code from scaling to meet the demands of bulk processing, causing runtime failures during batch updates or heavy user activity, which leads to poor system reliability.

Answer

The trigger logic is attempting to update the same record more than 150 times.

Answer

The batch size in the data loader is set too high for the current trigger logic.

Answer

The org-wide daily DML limit has been exceeded due to high transaction volume.

Question 4

An enterprise application requires integrating an external REST service that processes high-volume transactions asynchronously. The integration framework must handle potential connection timeouts and ensure robust error logging. Which implementation strategy meets these architectural requirements?

Accepted Answer

Implement a Queueable Apex class with Database.AllowsCallouts, leveraging the Finalizer interface to capture failures and execute recovery logic.. Using Queueable Apex with the Database.AllowsCallouts interface and implementing the Finalizer interface provides a robust framework for asynchronous callouts. This combination ensures proper error handling, transaction tracking, and the ability to chain subsequent jobs if timeouts or transient connectivity issues occur in enterprise systems.

Answer

Execute synchronous callouts inside a scheduled Apex class running every minute to process transaction records sequentially.

Answer

Invoke the external REST service directly within a trigger handler using standard synchronous HTTP methods wrapped in a try-catch block.

Answer

Configure an outbound message workflow rule that pushes XML payloads to an enterprise service bus endpoint synchronously.

Question 5

Refer to the exhibit. A developer encounters this error message while deploying an updated trigger to a production environment. What is the most effective approach to diagnose and resolve this deployment failure?

Accepted Answer

Examine the detailed deployment error logs to identify the failing test method or trigger logic, fix the root cause, and re-run validation.. Trigger execution failures during deployments typically stem from missing test data or conflicting custom validation rules running against test records. Developers must examine the full stack trace in the debug log or CLI output to identify the exact line causing the exception, ensuring test classes provide comprehensive mock data that satisfies all enterprise automation requirements.

Answer

Delete the OrderTrigger from the package manifest file, deploy the remaining components, and reinstall the trigger manually through the Salesforce UI.

Answer

Increase the Salesforce API version in the package.xml manifest to version 60.0 to bypass legacy execution blocks.

Answer

Run sf org logout and re-authenticate with the production environment using a different system administrator credential.

Question 6

Which TWO statements are true regarding the use of 'System.debug()' in a production environment?

Accepted Answer

They can expose sensitive information if not properly filtered.. System.debug() statements are generally discouraged in production because they consume log space and can inadvertently expose sensitive data. While they are useful for debugging, they should be removed or wrapped in conditional logic. Efficient log management is vital for maintaining high performance and ensuring that production environment overhead remains minimal during peak business hours and critical transactional windows.

Answer

They have no performance impact on the execution time of the transaction.

Answer

They should always be left in the code to assist with future support cases.

Answer

They are automatically stripped by the Salesforce compiler in production.

Question 7

A developer is writing an Apex trigger on the Account object that performs a SOQL query inside a loop to retrieve related Contacts. To adhere to performance best practices and avoid governor limits, what is the most efficient pattern to implement?

Accepted Answer

Collect related IDs in a Set, query all Contacts once, and store them in a Map for lookup.. Retrieving data inside a loop creates an N+1 query problem, which rapidly consumes SOQL limits and degrades performance. By collecting IDs into a Set and performing a single bulkified query before processing the records, the developer reduces the total number of round-trips to the database. This pattern is essential for maintaining application scalability and ensuring the trigger remains performant as the data volume grows within the production environment.

Answer

Use the Database.getQueryLocator method within the loop to retrieve records.

Answer

Move the SOQL query into a static method that is called by the trigger.

Answer

Increase the SOQL query limit by using the @ReadOnly annotation on the method.

Question 8

A developer needs to prevent a recursive trigger execution when updating parent records. What is the most robust way to handle this in Apex?

Accepted Answer

Use a static Boolean variable in a utility class to flag execution.. Recursion control is a critical design pattern in Apex to prevent 'Maximum trigger depth exceeded' errors. By utilizing a static Boolean variable in a utility class, the developer can track the state of the execution across the current transaction. This allows the trigger logic to bypass subsequent executions, ensuring that the business logic only fires when necessary, maintaining data integrity and system stability.

Answer

Use an instance variable in the Trigger Handler class.

Answer

Check the context of the transaction using the 'Limits.getTriggerDepth()' method.

Answer

Wrap all trigger logic in a try-catch block to suppress errors.

Question 9

A developer is creating a custom exception to handle business logic errors. What is the correct way to declare this exception so it can be caught specifically in a try-catch block?

Accepted Answer

public class MyException extends Exception {}. Defining a custom exception class extending the built-in 'Exception' class is the standard practice in Apex. This allows developers to catch specific business errors separately from system errors like NullPointerExceptions. Proper exception handling is critical for maintaining clean, readable code and ensuring that users receive meaningful feedback when operations fail during complex business processes or integration calls.

Answer

public class MyException implements Exception {}

Answer

public exception MyException {}

Answer

public static exception MyException = new Exception();

Question 10

A developer is experiencing performance issues with a Visualforce page that includes multiple complex components and a large amount of data. The page uses a standard controller with several extensions. Which technique should the developer use to reduce the view state size and improve page load time?

Accepted Answer

Mark non-essential controller variables with the 'transient' keyword.. Visualforce view state can significantly impact performance, as it is sent back and forth between the client and server. Minimizing the data stored in the view state is essential. Using the transient keyword on variables that do not need to persist across postbacks is a primary optimization technique for Visualforce developers.

Answer

Replace the standard controller with a custom controller using 'without sharing'.

Answer

Wrap all input fields in an <apex:actionRegion> component.

Answer

Increase the 'apiVerson' in the Visualforce page metadata to the latest version.

Question 11

Refer to the exhibit. A developer encounters a 'Maximum stack depth reached' error. What is the most likely cause of this recursive error?

Accepted Answer

The trigger logic performs a DML operation that causes the same trigger to fire again.. This error indicates infinite recursion, where a trigger fires, updates a record, and that update triggers the same logic again. The stack trace shows the method calling itself. This is a common issue in Salesforce triggers and must be handled using static boolean flags or check variables to ensure that logic only executes once per transaction, preventing circular loops that exhaust system resources.

Answer

The code is using a SOQL query inside a loop, exceeding the limit.

Answer

The trigger is processing too many records in a single batch, exceeding 200.

Answer

The code is attempting to access a field that does not exist in the current scope.

Question 12

During a deployment, a developer notices that existing Apex tests are failing, even though the new code changes are unrelated to the failing tests. What is the most likely cause?

Accepted Answer

The tests depend on existing data in the environment that has changed.. This scenario suggests that existing tests are dependent on specific org data or state that was altered, or they are fragile due to hardcoded dependencies. Salesforce tests must be independent and self-contained to avoid such side effects. This highlights the critical importance of test data isolation and the avoidance of relying on existing production records, which are unreliable for consistent testing and can lead to unexpected failures during deployment.

Answer

The deployment package deleted existing tests that were required for coverage.

Answer

The Salesforce platform automatically updates existing Apex code, causing regressions.

Answer

Deployment always triggers a full system reset of the production database.

Question 13

When designing a high-performance integration, what is the best practice for handling data updates to avoid record locking issues?

Accepted Answer

Sort data by record ID before performing bulk DML operations.. Sorting data by ID before performing bulk updates is the most effective way to prevent record locking contention. When records are processed in a consistent order, multiple threads or processes are less likely to conflict, as they will attempt to lock records in the same sequence. This simple optimization prevents 'Unable to lock row' errors, which are common in high-volume, multi-threaded integration environments.

Answer

Process records in random order to distribute load.

Answer

Perform all updates using a single user account.

Answer

Disable all triggers during the bulk data update process.

Question 14

A developer wants to ensure that a Lightning Web Component is only available for use on Record Pages for the Account and Contact objects in the Lightning App Builder. How should the developer configure the component's metadata file?

Accepted Answer

Define lightning__RecordPage and use in .. The component's metadata file (.js-meta.xml) defines where and how a component can be used within the Salesforce UI. The 'target' tags specify the application context, while the 'targetConfigs' section allows for more granular control, such as restricting the component to specific objects. This ensures a better admin experience by preventing misplacement.

Answer

Use the @isTest(SeeAllData=true) annotation in the JavaScript controller.

Answer

Add the objects to the 'scoped' attribute of the component's template tag.

Answer

Set the isExposed flag to false and list the objects in a custom property.

Question 15

A developer wants to use Platform Cache to improve the performance of a high-traffic Visualforce page that performs expensive SOQL queries and calculations. The data is specific to each user and should persist across multiple requests within the same session. Which type of cache should the developer use?

Accepted Answer

Session Cache, because it is dedicated to an individual user's session.. Platform Cache is divided into Org Cache and Session Cache. Session Cache is specifically designed to store data associated with a single user's session. This is ideal for scenarios where data is expensive to compute but unique to a user, as it prevents redundant processing across multiple page loads or requests within that session.

Answer

Org Cache, because it allows all users to share the same cached data.

Answer

Distributed Cache, because it automatically syncs data across all instances.

Answer

Metadata Cache, because it is optimized for SOQL query result sets.