SF-PD2 Testing, Debugging, and Deployment Practice Test 7 — 15 Questions

Question 1

A developer is writing a test class for a service that makes callouts to an external web service. The test method needs to simulate the callout response without making an actual HTTP request. (Choose two.)

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Implement the HttpCalloutMock interface and use Test.setMock(HttpCalloutMock.class, mock).. To simulate callouts in Apex tests, developers can use HttpCalloutMock for HTTP callouts or WebServiceMock for SOAP callouts. Both require implementing the respective interface and registering the mock with Test.setMock. This intercepts the callout and returns a controlled response. Test.startTest and Test.stopTest do not simulate callouts, and SeeAllData does not affect callouts.

Answer

Use @isTest(SeeAllData=true) to access external data.

Answer

Use Test.startTest() and Test.stopTest() to isolate the callout.

Answer

Set the callout to run asynchronously to avoid the callout limit.

Question 2

A developer is debugging an Apex class that is failing in production. The developer wants to capture debug logs for a specific user without affecting other users. Which tool should be used to set up a trace flag for that user?

Accepted Answer

Setup Debug Logs. To capture debug logs for a specific user, a developer should use the Debug Logs page in Setup. There, they can create a trace flag for that user, specifying the log levels and duration. This isolates the logging to that user, avoiding impact on others. Other tools like Developer Console are for personal debugging, and Audit Trail is for configuration changes.

Answer

Setup Audit Trail

Answer

Workbench

Answer

Developer Console

Question 3

A developer is preparing a managed package for release and needs to validate that the package's Apex code does not exceed the per-transaction limits enforced by the platform. The developer wants to run the packaged test suite in a scratch org and see the exact number of SOQL queries and DML statements consumed during each test. Which approach best satisfies this requirement?

Accepted Answer

Run the tests with the Salesforce CLI using sf apex run test with the --result-format json flag and parse the limits object for each test result.. The JSON result format from sf apex run test attaches a limits object to each test result, exposing the exact SOQL and DML counters consumed by every test method. Parsing that structured output gives the developer the precise, per-test governor limit data required to prove a managed package stays within platform limits before release, which the other approaches cannot deliver.

Answer

Query the ApexTestResult object with SOQL after the run and read the StackTrace field for each record.

Answer

Enable debug logs at the FINEST level for the running user and read the cumulative limits as they appear at the bottom of each log.

Answer

Run the tests with the Salesforce CLI using sf apex run test with the --result-format human flag and inspect the output for limit usage.

Question 4

An integration test in a sandbox must verify that a callout to an external pricing service returns a parsed response. The test class currently attempts the real callout and fails with a 'Methods defined as TestMethod do not support Web service callouts' error. Which change should the developer make?

Accepted Answer

Implement HttpCalloutMock and register it with Test.setMock() before the code under test invokes the callout.. Apex tests are isolated from external systems, so any callout must be replaced with a mock. Implementing HttpCalloutMock and registering it via Test.setMock() lets the code under test receive a controlled response, allowing the developer to assert on parsing, status handling, and error branches without a live service.

Answer

Wrap the callout in Test.startTest() and Test.stopTest() so the platform permits external requests.

Answer

Add the @future(callout=true) annotation to the method performing the callout.

Answer

Grant the running user the 'Make Callouts in Tests' permission in the test class profile.

Question 5

A developer is deploying a new Lightning web component that calls an Apex controller method. The deployment to production fails because the Apex class is not covered by tests. The developer needs to ensure the Apex class meets the 75% test coverage requirement and that the tests are robust. Which two actions should the developer take to achieve this? (Choose two.)

Accepted Answer

Write test methods that cover all branches of the Apex controller, including positive and negative scenarios.. To meet coverage requirements and ensure robust tests, the developer should write test methods that cover all branches, including positive and negative scenarios, and include assertions that validate outcomes and exception handling. These actions ensure that the Apex controller's logic is thoroughly exercised and verified, which is essential for production deployment.

Answer

Use @TestVisible private methods to expose internal logic for testing without altering the public API.

Answer

Create test data using Test.loadData() with a static resource to ensure consistent data across test methods.

Answer

Use Test.startTest() and Test.stopTest() to reset governor limits and isolate the test data.

Question 6

A developer is troubleshooting a production issue where a trigger occasionally exceeds CPU time limits. The developer wants to capture detailed debug logs for a specific user without slowing down the entire org, and then analyze the log to identify the slowest operations. Which combination of Salesforce tools should the developer use?

Accepted Answer

Debug Logs with a user-specific trace flag, then the Analysis perspective in the Developer Console. A user-specific trace flag generates debug logs only for that user, keeping overhead contained while capturing the problematic transaction. The Developer Console's Analysis perspective then parses the log and ranks operations by execution time, exposing the slowest SOQL, DML, and method calls. This focused capture and analysis directly targets the CPU time issue without impacting other users.

Answer

Event Monitoring via the EventLogFile object, then Workbench to query the logs

Answer

Setup Audit Trail to identify the user, then Apex Replay Debugger to step through the log

Answer

Apex Profiler in VS Code with the Apex extension, then the Timeline view

Question 7

A developer is debugging why a trigger fires twice for a single record save in a sandbox. The trigger is defined on Account with `before insert, after insert` and the class uses a static Boolean guard variable to prevent recursion. Logs show two separate transactions. Which explanation best fits this behavior?

Accepted Answer

A second DML operation on the same Account was performed by another process, such as a workflow field update or a related-record trigger, producing a distinct transaction.. Static variables live only for one transaction, so a guard cannot stop a trigger from firing again when the same record is saved in a new transaction. Workflow field updates, process-driven updates, or DML from a related object's trigger each create a new context, which is why the logs show two distinct transactions and the trigger runs twice.

Answer

The developer should add `with sharing` to the trigger to prevent the second execution.

Answer

The static Boolean guard is reset between the before and after phases of the same transaction, allowing the logic to run again.

Answer

The trigger was deployed twice, so the platform executes both copies for every save.

Question 8

A developer is writing a test class for a service that makes callouts to an external web service. The test method needs to simulate the callout response without making an actual HTTP request. (Choose two.)

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Use Test.setMock with an implementation of HttpCalloutMock that returns different responses based on the request endpoint. HttpCalloutMock registered with Test.setMock intercepts callouts during tests and returns the response the mock defines. By inspecting the request endpoint or body, the mock can return a success payload for one path and an error status for another, letting the test validate both branches. This keeps production code free of test-specific branches and satisfies the no-real-callout rule.

Answer

Use HttpRequest and Http directly in the test class to simulate the external service response

Answer

Use Test.isRunningTest to conditionally return hardcoded responses from the service class instead of performing the callout

Answer

Use Test.startTest and Test.stopTest to wrap the callout and rely on the test context to intercept external requests

Question 9

A developer is writing an Apex test class for a service that calls an external REST endpoint via a callout. The test must verify the parsing logic without hitting the external system, and it must also assert that the service throws a custom exception when the endpoint returns a 500 status. Which combination of techniques is required?

Accepted Answer

Use HttpCalloutMock to return a 200 response for the happy path, and use Test.setMock with a separate mock returning a 500 response to assert the exception.. Tests cannot perform real callouts, so HttpCalloutMock injected via Test.setMock supplies a controllable HttpResponse. Using one mock that returns status 200 exercises the parsing logic, while a second mock returning status 500 drives the error branch so the custom exception can be asserted, covering both paths with no external dependency.

Answer

Use a WebServiceMock implementation, since WebServiceMock is the only interface that supports simulating HTTP responses in tests.

Answer

Use Test.setMock with HttpCalloutMock and set the mock's response status to 500 for both the happy path and the error path.

Answer

Use Test.isRunningTest within the service to branch around the callout logic and return hardcoded values.

Question 10

A developer needs to give a CI service account the ability to run the Apex test suite in a production org without interactive login, and the pipeline must not store a user's personal password. Which authentication approach should the developer configure?

Accepted Answer

Authenticate the CI job with a connected app using the JWT bearer flow and authorize the integration user in advance.. The JWT bearer flow with a connected app and a pre-authorized integration user provides headless, passwordless authentication for CI, since the pipeline signs a JWT with a certificate instead of storing user credentials. This satisfies the requirement to run Apex tests in production without interactive login or a personal password.

Answer

Store the integration user's username and password in an encrypted pipeline variable and authenticate with sf org login web.

Answer

Use the SOAP login call with the integration user's credentials and a security token appended to the password.

Answer

Generate a personal access token in the org's setup and pass it to the CLI with the sf org login access-token command.

Question 11

A developer is writing an Apex test method for a service class that makes a callout to an external REST API. The test must not perform the actual callout. The developer creates a static resource containing the JSON response and writes a mock class that implements HttpCalloutMock. Which statement must the developer include in the test method to register the mock before the callout is executed?

Accepted Answer

Test.setMock(HttpCalloutMock.class, new MyApiMock());. Test.setMock is the only supported way to inject a mock implementation for HTTP callouts during Apex tests. It must be invoked before the callout is made, typically at the start of the test method. The mock's respond method then supplies the HttpResponse, allowing the developer to test success and error handling without external dependencies.

Answer

HttpCalloutMock mock = new MyApiMock(); Test.startTest(); mock.respond(new HttpRequest());

Answer

Test.setMock(WebServiceMock.class, new MyApiMock());

Answer

Test.loadData(HttpCalloutMock.SObjectType, 'MyApiMock');

Question 12

A developer is writing an Apex test class for a service that calls an external REST API using a Named Credential. The test must not make real callouts, and the developer wants to verify that the correct endpoint and body are sent. Which approach should the developer use?

Accepted Answer

Implement the HttpCalloutMock interface in a test class and register it with Test.setMock(HttpCalloutMock.class, new MockImpl()).. The HttpCalloutMock interface is the designated mechanism for simulating callouts in Apex tests. By implementing it and registering an instance with Test.setMock, the developer can intercept Http.send() calls, return a controlled response, and inspect the HttpRequest to confirm the endpoint and body. This keeps the test isolated, fast, and free of external dependencies, and it aligns with Salesforce best practices for testing callout logic.

Answer

Use Test.isRunningTest() inside the service class to conditionally skip the callout and return a hardcoded response.

Answer

Wrap the callout in Test.startTest() and Test.stopTest() to prevent the callout from executing during the test.

Answer

Set the endpoint in a Custom Setting and use a test-specific value that points to a local mock server.

Question 13

A developer is preparing to deploy a change set from a sandbox to production. The change set includes an Apex class that references a new custom field on Account. The deployment fails with a 'field does not exist' error. What is the most likely cause and the correct action?

Accepted Answer

The custom field was not added to the change set; the developer must add the field to the change set and redeploy.. Change sets require all dependent metadata to be included explicitly. When an Apex class references a custom field that is not in the change set, the target org lacks that field, and the deployment fails at compile time. The solution is to add the custom field to the change set and redeploy. This ensures the field exists before the class is compiled, resolving the dependency error.

Answer

The custom field is not accessible to the deploying user's profile; the developer must grant field-level security and redeploy.

Answer

The custom field's API name was changed in the sandbox; the developer must update the Apex class to use the new API name before deploying.

Answer

The Apex class was deployed before the custom field; the developer must deploy the field first, then the class.

Question 14

A developer needs to debug an Apex trigger that intermittently fails in production with a 'UNABLE_TO_LOCK_ROW' error when multiple users update related records. Which technique should the developer use to capture the detailed execution context and identify the conflicting transaction?

Accepted Answer

Enable debug logs for the triggering user and analyze the log for the row lock error and preceding DML operations.. Debug logs are the primary tool for diagnosing runtime errors like UNABLE_TO_LOCK_ROW. They record the exact DML operations and the order in which they occurred, including the records involved. By enabling a debug log for the affected user, the developer can see which DML statement failed to acquire a lock and what operations preceded it. This information is critical to identify the conflicting transaction and refactor the code to avoid locking contention.

Answer

Run the Apex Test Execution with 'Always Run Asynchronously' enabled to simulate concurrent updates.

Answer

Set up a custom logging object and insert a record at the start of each trigger invocation to track user activity.

Answer

Use the Developer Console's Query Plan tool to analyze the selectivity of the SOQL queries in the trigger.

Question 15

A developer is writing an Apex test class for a controller that uses a Visualforce page with a standard controller. The test must cover pagination logic that relies on the StandardSetController. Which TWO actions should the developer take to ensure the test is reliable and covers the pagination behavior? (Choose two.)

Accepted Answer

Use Test.setCurrentPage() to set the Visualforce page context and then instantiate the StandardSetController with a query locator.. To reliably test pagination with StandardSetController, the test must create enough records to span multiple pages and then invoke the pagination methods. Additionally, setting the Visualforce page context with Test.setCurrentPage() and instantiating the StandardSetController with a query locator ensures the controller operates as it would in a real page. These two actions together exercise the pagination logic and verify the expected behavior across pages.

Answer

Set the page size to a large number so that all test records fit on one page, simplifying the test and avoiding pagination complexities.

Answer

Use Test.startTest() and Test.stopTest() to isolate the pagination logic and reset governor limits between pages.

Answer

Use Test.isRunningTest() in the controller to bypass the query and return a hardcoded list of records for pagination testing.