SALESFORCE-PD1 Testing Debugging And Deployment Practice Test 3 — 15 Questions

Question 1

Which tool is best suited for running all tests in an org and viewing the code coverage percentages?

Accepted Answer

Developer Console. The Developer Console includes a Test menu with 'Run All Tests' and 'Run Tests' options, and its Tests tab displays pass/fail results alongside org-wide code coverage percentages per class and overall. It is the built-in tool designed for developers to execute Apex tests and inspect coverage without deploying or using external utilities. Setup's Apex Test Execution page can run tests but coverage viewing is more limited, and Change Sets and Workbench are not test-running tools.

Answer

Salesforce Setup Menu

Answer

Change Sets

Answer

Workbench

Question 2

Which TWO of the following are valid ways to execute Apex unit tests in Salesforce?

Accepted Answer

Developer Console. Apex unit tests can be executed through several methods, most notably the Developer Console, the Apex Test Execution page in Setup, and the Salesforce CLI (sfdx force:apex:test:run or sf apex test run).

Answer

Object Manager settings

Answer

User Management settings

Answer

Change Sets menu

Question 3

Which TWO of the following are limitations when deploying using the Metadata API?

Accepted Answer

Components must be defined in a package.xml manifest. Option A is correct because the Metadata API requires a package.xml manifest to specify which components are retrieved or deployed, making the manifest a mandatory part of any deployment operation. Option C is correct because when deploying to a production org via the Metadata API, Apex tests are run automatically (unless explicitly skipped with the appropriate deploy options), which is a built-in behavior and thus a limitation on how deployments can be performed. Option B is incorrect because the Metadata API does not bypass governor limits; deployments are still subject to platform limits. Option D is incorrect because the Metadata API supports a wide range of metadata types beyond Apex Classes, such as custom objects, layouts, and profiles. Option E is incorrect because Metadata API deployments do not require manual review by Salesforce Support.

Answer

It allows bypassing governor limits during deployment

Answer

It can only be used for Apex Classes

Answer

It requires a manual review by Salesforce Support

Question 4

Which TWO of the following are required to successfully use the 'Test.startTest()' and 'Test.stopTest()' pattern for testing batch Apex?

Accepted Answer

Assertions must be placed after the Test.stopTest() call. Option D is correct because Test.stopTest() forces all asynchronous work queued during the test to execute synchronously, so any assertions verifying the batch's results must be placed after Test.stopTest() to see the committed effects. Option E is correct because the batch job must actually be enqueued via Database.executeBatch (or System.scheduleBatch) between Test.startTest() and Test.stopTest(); the start/stop block only governs limits and forces async execution of work submitted within it, so without calling executeBatch inside the block the batch never runs. Option A is not required — a batch class can be defined as an inner class or in the same file as the test, since Apex allows multiple top-level classes per file. Option B is not required — @isTest(SeeAllData=true) only affects data visibility and is unrelated to the startTest/stopTest pattern. Option C is not required — the global modifier is only needed for classes exposed across namespaces or via the API, not for batch classes invoked from a test in the same namespace.

Answer

The batch class must be implemented in a separate file

Answer

The test must be annotated with @isTest(SeeAllData=true)

Answer

The batch class must have a global access modifier

Question 5

Which TWO of the following are true about the 'Debug Log' settings in the Setup menu?

Accepted Answer

Trace flags have an expiration date and time. Logs can be set for users, and the duration of those log traces is limited.

Answer

Debug logs can only be generated for the System Administrator profile

Answer

Setting a trace flag on a user consumes API calls

Answer

Logs can be set to last for an infinite duration

Question 6

A developer deploys a new Apex class to production using the Salesforce CLI and a manifest file. The deployment succeeds, but a scheduled Apex job that calls this class now fails at runtime with a 'System.TypeException: Invalid conversion' error that never appeared in the sandbox. The sandbox and production have identical Apex code and API versions, but production has several record types and picklist values that are not present in the sandbox. Which action should the developer take to most reliably reproduce and diagnose the failure before redeploying?

Accepted Answer

Create a full sandbox from production and run the scheduled job's logic there to reproduce the data-dependent error.. The error stems from production-specific data and configuration not present in the sandbox. A Full sandbox is an exact replica of production, including all records, record types, and picklist values. Reproducing the scheduled job there allows the developer to observe the same TypeException, inspect the actual data causing the invalid conversion, and validate a fix under identical conditions before redeploying.

Answer

Run the Apex test class associated with the scheduled job in the sandbox with SeeAllData=true.

Answer

Increase the debug log level for Apex Code to FINEST in production and rerun the scheduled job.

Answer

Use the Developer Console in production to execute anonymous Apex that mimics the scheduled job.

Question 7

A developer wrote an Apex test class that inserts 200 Account records and then queries them to verify a trigger populated a custom field. The test fails with a System.LimitException: Too many SOQL queries: 101 error. The test class uses @isTest(SeeAllData=false) and contains a single test method. Which change should the developer make to resolve the error while preserving the test's intent?

Accepted Answer

Refactor the trigger to perform a single SOQL query outside the loop and use a Map to correlate records.. The Too many SOQL queries error occurs when a trigger performs a SOQL query inside a loop, causing the number of queries to scale with the number of records. The correct fix is to bulkify the trigger by moving the query outside the loop and using a Map to correlate records, which reduces the query count to one. This maintains the test's validation of the trigger's behavior while staying within governor limits.

Answer

Wrap the record insertion and the verification query inside Test.startTest() and Test.stopTest().

Answer

Use Test.loadData() to insert the 200 Account records from a static resource instead of DML.

Answer

Reduce the number of inserted Account records to a smaller batch, such as 20, so the trigger executes fewer times.

Question 8

A developer is preparing to deploy a set of Apex classes, Visualforce pages, and custom objects from a sandbox to production using the Metadata API. The deployment must succeed on the first attempt. Which two actions should the developer take before deploying? (Choose two.)

Accepted Answer

Use a package.xml manifest to specify the components to retrieve and deploy.. Successful deployment via the Metadata API requires a package.xml manifest to specify components and ensuring Apex test coverage of at least 75% in production. The manifest defines what is deployed, and coverage is a mandatory production requirement. The other actions are either validation steps or incorrect practices like manual creation of objects, which can cause conflicts.

Answer

Set the checkOnly parameter to true in the deploy call to validate the deployment without saving.

Answer

Manually create all custom objects in production before deploying the Apex classes.

Answer

Run the Apex Test Execution page in the Developer Console to identify failing tests.

Question 9

A developer needs to debug an Apex trigger that is not firing as expected when a new Case is created from the Salesforce UI. The developer wants to see detailed information about the trigger's execution, including variable assignments and SOQL queries. Which tool should the developer use to capture this information in real time?

Accepted Answer

Developer Console's Logs tab with the appropriate debug levels set for Apex Code and Workflow.. The Developer Console's Logs tab is designed for real-time debugging of Apex, allowing developers to set granular debug levels and view detailed execution logs, including variable assignments and SOQL queries. It is the most efficient tool for this scenario. Setup Audit Trail and Apex Test Execution do not provide the needed execution details, and Setup Debug Logs are less interactive.

Answer

Setup Audit Trail to review recent configuration changes.

Answer

Debug Logs in Setup with a trace flag set for the running user.

Answer

Apex Test Execution page to run a test class that creates a Case.

Question 10

A developer is writing a unit test for an Apex class that calculates discounts based on Account revenue. The test needs to verify that a custom exception, DiscountException, is thrown when the revenue is negative. Which approach should the developer use to assert that the exception is thrown?

Accepted Answer

Use a try-catch block, catch the specific DiscountException, and call System.assert(false) after the method call to ensure the exception was thrown.. To assert that a specific exception is thrown, the test should call the code inside a try block, catch the expected exception type, and include a System.assert(false) immediately after the call within the try block. If the exception is thrown, the catch block executes and the assertion is skipped. This pattern ensures the test passes only when the expected exception occurs.

Answer

Use a try-catch block and call System.assert(false) in the catch block to fail the test if no exception is thrown.

Answer

Use the ApexTestException annotation and specify the expected exception class.

Answer

Use a try-catch block and call System.assert(true) in the catch block to indicate the exception was caught.

Question 11

A developer wants to test an asynchronous future method. Where must the developer place the asynchronous code execution so that it runs synchronously and within the test context?

Accepted Answer

Between Test.startTest() and Test.stopTest(). Test.startTest() and Test.stopTest() bracket the code block where asynchronous processes like future methods, batch jobs, and queueables are forced to execute synchronously.

Answer

Inside a System.runAs() block

Answer

Within a try-catch block

Answer

Inside a Database.executeBatch block

Question 12

A developer is analyzing a debug log and notices that it is truncated because it exceeded the maximum file size limit. Which action should the developer take to capture only the relevant Apex code execution details without exceeding the limit?

Accepted Answer

Adjust the Trace Flag log levels to reduce verbosity for unnecessary categories like Database and Workflow.. Refining log categories and levels ensures only necessary debug statements are recorded, preventing truncation.

Answer

Increase the maximum log file size in company profile settings.

Answer

Disable all validation rules in the org temporarily.

Answer

Switch the debug log perspective to 'Development Harvester'.

Question 13

A developer receives a System.LimitException: Too many SOQL queries: 101 when running a complex unit test. The test class inserts a large volume of test records that inadvertently cause a trigger to execute multiple queries inside a loop. What is the most effective way to reset the governor limits specifically for the code being tested?

Accepted Answer

Wrap the test assertion code between Test.startTest() and Test.stopTest().. Test.startTest() resets all governor limits for the code executed immediately following it, up until Test.stopTest().

Answer

Mark the test method with @isTest(SeeAllData=true).

Answer

Wrap the trigger logic in a Database.setSavepoint() block.

Answer

Use Limits.getLimitQueries() inside the test method.

Question 14

A developer is writing a unit test that executes under a specific user context to verify sharing rules. Which method should the developer use to specify the user for the subsequent test operations?

Accepted Answer

System.runAs(). System.runAs() enables developers to run test methods under a specific user context to verify record-level security and sharing rules.

Answer

UserInfo.setUserId()

Answer

Database.setSavepoint()

Answer

Test.setCurrentUser()

Question 15

A developer is writing a test method that performs a callout to an external REST service. Which interface must the developer implement to provide mock responses during the unit test execution?

Accepted Answer

HttpCalloutMock. HttpCalloutMock is the interface implemented to supply a mock HTTP response during test context when callouts are made.

Answer

InstallHandler

Answer

Schedulable

Answer

Database.Batchable