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

Question 1

A developer is using Salesforce CLI to create a temporary environment for feature development and testing that includes all source code and shape settings. Which CLI command should the developer use to create this temporary environment?

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

Accepted Answer

sf org create scratch. sf org create scratch creates a scratch org based on a definition file.

Answer

sf org login web

Answer

sf org create sandbox

Answer

sf project retrieve start

Question 2

A developer is deploying a profile and custom fields using an Unmanaged Change Set. Upon deployment, some custom field permissions fail to apply correctly in production. What is the most likely cause of this behavior?

Accepted Answer

Field-level security settings on profiles are sometimes omitted or overridden if the target profile already exists and has conflicting security configurations.. Profiles and permission sets in change sets require careful component selection, and field-level security is often best handled via permission sets or post-deployment steps.

Answer

Unmanaged change sets require manual XML editing prior to upload.

Answer

Change sets do not support the deployment of custom fields under any circumstances.

Answer

Profiles cannot be included in outbound change sets.

Question 3

A developer has written a Lightning Web Component and Apex controller, and wants to deploy only these specific metadata components to a production org using Salesforce CLI without relying on change sets. Which command is appropriate?

Accepted Answer

sf project deploy start. sf project deploy start deploys source files from a local project directory to a target org.

Answer

sf apex run

Answer

sf org open

Answer

sf project convert mdapi

Question 4

A developer needs to verify code coverage across an entire Apex organization before deploying code to production. What is the minimum overall Apex code coverage required by Salesforce for production deployment?

Accepted Answer

75%. Salesforce requires a minimum of 75% overall Apex code coverage for deployment to a production organization.

Answer

100%

Answer

50%

Answer

85%

Question 5

A developer wants to inspect the code coverage of individual classes directly within the Salesforce Developer Console. Under which tab can the developer view this breakdown?

Accepted Answer

Tests tab. The Tests tab in the Developer Console displays test execution status, test results, and code coverage percentages by class.

Answer

Query Editor tab

Answer

DOM Inspector tab

Answer

Logs tab

Question 6

Which TWO actions occur automatically when Test.stopTest() is called in an Apex unit test? (Choose two.)

Accepted Answer

All asynchronous queued processes (future, batch, queueable) are run synchronously.. Option A is correct because Test.stopTest() forces all asynchronous Apex that was queued during the test—future methods, batch jobs, and queueable jobs—to execute synchronously before the method returns, allowing the test to assert on their results. Option D is correct because Test.stopTest() also flushes pending asynchronous communications, including email sent via Messaging.sendEmail, so that the messages are dispatched and can be verified with Limits.getEmailInvocations() or by querying EmailMessage records. Option B is wrong because Test.stopTest() does not log out the running user; the test continues executing in the same session context. Option C is wrong because no custom objects are deleted or recreated; test data isolation is handled by the test's own transaction rollback, not by schema changes. Option E is wrong because Test.stopTest() does not commit data to production—all test data changes are rolled back after the test completes.

Answer

The user session is automatically logged out.

Answer

All custom objects in the organization are deleted and recreated.

Answer

The database is permanently committed to production.

Question 7

Which TWO practices are considered best practices when writing Apex unit tests in Salesforce? (Choose two.)

Accepted Answer

Create all required test data within the test method or test setup method.. Using Test.startTest/stopTest and avoiding SeeAllData=true are essential Apex testing best practices.

Answer

Hardcode record IDs directly from the sandbox into assertions.

Answer

Query production records directly in every assertion to verify live system status.

Answer

Use @isTest(SeeAllData=true) on all test classes to ensure maximum compatibility with production data.

Question 8

Which THREE items are best practices when setting up test data using @TestSetup methods? (Choose three.)

Accepted Answer

Perform time-consuming operations or bulk data generation once to avoid hitting governor limits in separate test methods.. Option A is correct because @TestSetup runs once per test class and its resulting data is available to every test method, so performing expensive or bulk data generation there conserves governor limits (DML statements, CPU time, SOQL queries) that would otherwise be consumed repeatedly in each test method. Option C is correct because creating parent records such as Accounts in @TestSetup lets individual test methods query those records and build child records (for example Contacts or Opportunities) against them, which is the intended pattern for reusable seed data. Option E is correct because Salesforce wraps each test method in its own transaction and rolls back any changes made during that method, so modifications to @TestSetup records in one test method do not leak into another; the @TestSetup data is restored to its original state for the next method. Option B is not a best practice because record IDs are assigned at runtime and hardcoding them makes tests brittle and non-portable across orgs; tests should query the records instead. Option D is not a best practice because callouts are not allowed in @TestSetup (and generally not in test methods without a mock), so external REST callouts would fail; seed data should be created locally or via mock callouts.

Answer

Hardcode specific record IDs assigned during @TestSetup into downstream test assertions.

Answer

Call external REST callouts inside the @TestSetup method to fetch live seed data.

Question 9

Which TWO conditions must be met for an Apex test method to successfully execute and contribute to code coverage? (Choose two.)

Accepted Answer

The test method must be declared as static.. Option D is correct because Apex test methods must be declared with the static modifier; instance methods are not recognized as test methods and will not be executed by the test framework or counted toward code coverage. Option E is correct because the method must be annotated with @isTest (or be inside a class annotated with @isTest) so the Apex runtime identifies it as a test method eligible for execution and coverage tracking. Options A, B, and C are incorrect: test methods take no parameters, there is no TestInterface to implement, and test methods must return void rather than an Integer.

Answer

The test method must accept a List of SObjects as a parameter.

Answer

The test class must implement the TestInterface interface.

Answer

The test method must return an Integer value representing success.

Question 10

Which TWO tools or APIs can a developer use to deploy metadata between Salesforce organizations? (Choose two.)

Accepted Answer

Outbound and Inbound Change Sets. Change Sets and the Metadata API (via CLI or IDEs) are primary tools for metadata deployment.

Answer

Data Loader

Answer

Apex Anonymous Windows

Answer

Process Builder

Question 11

A developer is writing an Apex test class and needs to reset governor limits before executing a block of asynchronous code testing. Which method should the developer use?

Accepted Answer

Test.startTest(). Test.startTest() and Test.stopTest() bracket the test section, resetting governor limits for the execution block within them and forcing any asynchronous calls to run synchronously.

Answer

Test.resetLimits()

Answer

Test.runAs()

Answer

Limits.reset()

Question 12

Where should a developer look in the Salesforce user interface to inspect detailed system debug logs generated during a specific transaction?

Accepted Answer

Setup > Custom Code > Debug Logs. Debug logs are accessed via Setup by navigating to Custom Code > Debug Logs or via the Developer Console.

Answer

Setup > Monitor > Logs

Answer

Setup > Environments > Logs

Answer

Setup > Process Automation > Debug Logs

Question 13

An Apex trigger performs a callout to an external web service and a developer is writing a unit test for this trigger. How should the developer handle the callout during the test execution?

Accepted Answer

Use Test.setMock(HttpCalloutMock.class, new MockHttpResponseGenerator()). Apex runtime throws an exception if a callout is attempted in a test without being mocked. The developer must implement the HttpCalloutMock interface and use Test.setMock().

Answer

Use System.runAs() to execute the test under a user with API Enabled permissions

Answer

Wrap the trigger logic inside a Test.startTest() and Test.stopTest() block without mocks

Answer

Set the remote site setting dynamically inside the test method before the trigger fires

Question 14

An asynchronous @future method is called from within an Apex test method. When are the statements inside the @future method actually executed during the test run?

Accepted Answer

After the Test.stopTest() method is executed. Asynchronous methods called in tests are queued and executed synchronously after the Test.stopTest() statement.

Answer

Immediately when the line invoking the @future method is reached

Answer

At the end of the test method automatically without needing Test.stopTest()

Answer

In a separate transaction concurrently while the test method continues running

Question 15

When calling Test.startTest() and Test.stopTest(), what happens to the governor limits?

Accepted Answer

Governor limits are reset to zero for the code between the two calls.. Test.startTest() and Test.stopTest() create a fresh governor limit boundary for the code executed between them. Any limits consumed before startTest() are not counted against the code inside the block, and the block gets its own set of limits (e.g., 100 SOQL queries, 150 DML statements). This allows developers to test code that would otherwise exceed limits when combined with test setup data creation.

Answer

Governor limits are increased by a factor of 10.

Answer

Test.stopTest() forces an immediate deployment.

Answer

Governor limits are ignored entirely.