SALESFORCE-PD1 Practice Test 6 — 10 Questions

Question 1

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 2

How can a developer inspect the state of a private variable within a class during unit testing?

Accepted Answer

Use the @TestVisible annotation.. The @TestVisible annotation allows a test method in the same class or a test class in the same namespace to access private or protected members of the annotated class without changing the member's visibility for production code. This preserves encapsulation in production while enabling white-box testing of internal state. It can be applied to private variables, methods, and inner classes.

Answer

Change the class to @isTest.

Answer

There is no way to inspect private variables.

Answer

Make the variable public.

Question 3

Which SLDS utility class should a developer use to add a standard margin around a container?

Accepted Answer

slds-m-around_medium. SLDS spacing classes follow the pattern slds-m-{sides}-{size}.

Answer

slds-grid

Answer

slds-padding_medium

Answer

slds-margin-all

Question 4

A developer needs to implement a custom logging framework. Which Apex data type should be used to represent a variable that can store any primitive value, sObject, or collection dynamically?

Accepted Answer

Object. The Object data type is the base data type in Apex and can hold any value, including primitives, sObjects, and collections.

Answer

Any

Answer

Variant

Answer

Dynamic

Question 5

A developer is writing a custom wire adapter or working with custom data in LWC and needs to manually provision data or force a refresh of wire data. Which function should be imported from lightning/uiRecordApi or related wire modules?

Accepted Answer

refreshApex. refreshApex is used to imperatively refresh data provisioned by an Apex wire adapter.

Answer

reloadRecord

Answer

updateRecordCache

Answer

getRecordRefresh

Question 6

When should a developer use a record-triggered flow instead of a scheduled path in a flow?

Accepted Answer

When actions need to occur instantly upon record creation.. Record-triggered flows execute immediately upon record creation or update, whereas scheduled paths run at a specific time offset.

Answer

When processing millions of historical records nightly.

Answer

When making external web service callouts synchronously.

Answer

When actions need to execute 30 days after a contract is signed.

Question 7

What happens if a test class has a method annotated with @testSetup that fails to insert data?

Accepted Answer

The entire test class fails to execute.. When a method annotated with @testSetup fails — for example, because a DML insert throws an exception — the entire test class is aborted and no test methods execute. The @testSetup method runs once before all test methods in the class, so its failure prevents the shared test data from being created and the platform marks the whole class as failed.

Answer

The test execution proceeds, but without data.

Answer

The platform ignores the @testSetup failure.

Answer

Only the first test method fails.

Question 8

A developer needs to pass a custom SObject record with related child lists into an asynchronous execution context. Which asynchronous Apex feature supports passing non-primitive types such as custom Apex objects or sObject collections?

Accepted Answer

Queueable Apex. Queueable Apex supports member variables of non-primitive types, including sObjects and custom classes.

Answer

Scheduled Apex

Answer

Future methods

Answer

Trigger asynchronous execution blocks

Question 9

What is the result of a compilation error in an Apex class during deployment?

Accepted Answer

The deployment fails entirely.. When Apex code contains a compilation error (syntax error, invalid reference, missing dependency), the deployment of that component fails. In a Change Set or Metadata API deployment, a compilation failure causes the entire deployment to fail—Salesforce does not partially deploy a class with errors or skip it silently. The deployment must be corrected and retried.

Answer

The class is deployed without the code.

Answer

The class is deployed with warnings.

Answer

The class is skipped.

Question 10

A developer is creating a Visualforce page that overrides the standard Account View action. Which attribute must be included in the <apex:page> tag to ensure standard controller functionality?

Accepted Answer

standardController="Account". The standardController attribute on <apex:page> binds the page to a Salesforce standard controller for a specific object, giving the page access to that object's fields, standard actions, and record context. When overriding a standard action like Account View, the page must declare standardController="Account" so the platform knows which object's standard controller to instantiate and how to pass the record Id. Without it, the page has no controller and cannot leverage standard save, view, or record-binding behavior.

Answer

controller="Account"

Answer

object="Account"

Answer

recordId="Account"