SALESFORCE-PD1 Testing Debugging And Deployment — 10 Questions

Question 1

A developer wants to view real-time debug log streaming in their local environment using the Salesforce CLI. Which command should the developer execute?

Accepted Answer

sf apex log tail. The sf apex log tail command streams debug logs to the terminal in real time.

Answer

sf apex run test

Answer

sf project deploy start

Answer

sf org display

Question 2

A developer has written a test method that requires a large volume of test data to be set up. To avoid writing duplicate data setup code across multiple test methods in the same class, which annotation should the developer use?

Accepted Answer

@TestSetup. The @TestSetup annotation is the correct choice because it allows for the creation of test data once per test class, which is then available to all test methods in that class. The provided explanation incorrectly discusses @TestVisible instead of @TestSetup.

Answer

@isTest(SeeAllData=true)

Answer

@TestVisible

Answer

@Future

Question 3

A developer needs to write a unit test to verify that a trigger correctly inserts related Task records when a custom object record is created. Which annotation should the developer place on the test class method to ensure it runs correctly and can access existing org data if needed?

Accepted Answer

@isTest. The @isTest annotation identifies a method or class as containing unit tests. Using @isTest(SeeAllData=true) is sometimes required when legacy data must be accessed, though best practice is to create test data locally.

Answer

@ReadOnly

Answer

@TestVisible

Answer

@TestSetup

Question 4

A developer is preparing to deploy metadata changes from a sandbox to a production org using Outbound Change Sets. Where must the administrator or developer establish the connection between the two organizations?

Accepted Answer

Deployment Settings in the target org. Deployment connections for change sets must be authorized and configured in Deployment Settings in the target production org.

Answer

Connected Apps in the production org

Answer

Named Credentials in both orgs

Answer

Remote Site Settings in the source org

Question 5

A developer runs unit tests in the Developer Console and notices that one test method fails when run as part of the entire test class, but passes successfully when run in isolation. What is the most likely cause of this issue?

Accepted Answer

Test data pollution caused by another test method modifying shared records without resetting state.. When tests run together in a class, they share the same transaction context and any data created by one test method can leak into another unless isolated. If one test method modifies or deletes records that another test method depends on—without using Test.startTest/stopTest or proper data setup—the dependent test fails in the full run but passes in isolation because the polluting test never executed. This is classic test data pollution.

Answer

The Developer Console caches old test results automatically.

Answer

The test class lacks the @isTest annotation.

Answer

Governor limits are permanently exhausted for the entire session.

Question 6

A developer is writing a unit test and needs to assert that a specific custom exception was thrown during invalid input processing. Which pattern should the developer use?

Accepted Answer

Wrap the target code in a try block, add Assert.fail('Expected exception') after the target code, and catch the exception.. While Option A is a common manual pattern in older Apex unit tests, modern Apex testing frameworks (and most modern unit testing frameworks in other languages) provide dedicated methods for exception assertion (e.g., Assert.throws in Apex). The question lacks a platform identifier, making the specific syntax references (like Limits.getScriptStatements) confusing.

Answer

Use Test.expectException() before calling the method.

Answer

Check Limits.getScriptStatements() after the method call.

Answer

Use System.assert(false, e.getMessage()) inside the catch block.

Question 7

Which THREE statements are true regarding Salesforce debug logs? (Choose three.)

Accepted Answer

Debug logs can capture database operations, Apex code execution, and workflow rule evaluations.. Option A is correct because Salesforce debug logs record a wide range of event categories, including database operations (SOQL/DML), Apex code execution, and workflow rule evaluations, all controlled by log levels. Option C is correct because trace flags are the mechanism that sets log levels and an expiration duration for a specific user, Apex class, or trigger, and logging only occurs when a trace flag applies. Option D is correct because each debug log file is capped at a maximum size (typically 20 MB in the Developer Console or 5 MB via the API), and once that limit is reached, older log lines are dropped or the log is truncated. Option B is incorrect because developers can view, filter, and download debug logs directly in the Salesforce Developer Console. Option E is incorrect because debug logs are automatically purged after a limited retention period (generally 24 hours in production) and are not stored indefinitely.

Answer

Developers cannot view debug logs inside the Salesforce Developer Console.

Answer

Debug logs are stored indefinitely in production without automatic purging.

Question 8

Which THREE features are supported in Salesforce scratch orgs? (Choose three.)

Accepted Answer

Installing unlocked and managed packages for testing.. Scratch orgs support source tracking, custom configurations, and feature activation.

Answer

Permanent production status with unlimited user licenses.

Answer

Directly modifying standard Salesforce platform source code.

Question 9

Which TWO circumstances will cause an Apex unit test method to fail? (Choose two.)

Accepted Answer

A System.assert() or Assert.areEqual() statement evaluates to false.. Uncaught exceptions and failed system assertions cause test method failures.

Answer

The test method executes in read-only mode.

Answer

The test class code coverage is exactly 75%.

Answer

The test method finishes executing with zero assertions.

Question 10

A developer wants to ensure that test methods in a managed package upgrade test all triggers and classes, and needs to bypass existing organization test data to use only packaged data. Which annotation parameter should be used?

Accepted Answer

@testSetup. The @isTest(SeeAllData=true) annotation allows test methods to access organization data, but by default tests do not see org data. To ensure standard test isolation or handle specific packaged test visibility, developers manage data appropriately. However, the exact mechanism to ignore org data when strict isolation is desired is the default @isTest behavior. Wait, let's frame it as testing legacy code: when using @isTest(SeeAllData=true), tests can access org data. If a developer needs to insert test data without using setup objects, @TestSetup is used. Let's make the question about @TestSetup efficiency.

Answer

@future(isTest=true)

Answer

@testVisible

Answer

@isTest(seeAllData=true)