SALESFORCE-PD1 Process Automation And Logic Practice Test 6 — 15 Questions

Question 1

An enterprise application requires real-time integration where outgoing callouts must be triggered from an Apex trigger. What architectural pattern must the developer use?

Accepted Answer

Future method annotated with @future(callout=true) invoked from an after trigger.. Triggers cannot make direct synchronous callouts, so they must invoke an asynchronous mechanism like a future method with callout=true.

Answer

Batch Apex execute method without queueing.

Answer

Direct synchronous HTTP callout inside the before insert trigger.

Answer

Validation rule containing an endpoint URL.

Question 2

A developer has a trigger that updates related child records. To prevent recursive trigger execution when updates ripple through child triggers, what is a standard best practice design pattern?

Accepted Answer

Using a static boolean flag in a utility class to track execution state.. Using a static boolean flag in a helper class is the classic pattern to prevent recursive trigger execution in Salesforce.

Answer

Using Flow Builder instead of Apex triggers for all child records.

Answer

Disabling all triggers via Custom Settings permanently.

Answer

Wrapping every DML statement in a try-catch block.

Question 3

Which feature allows administrators to invoke an Apex method from a Flow?

Accepted Answer

@InvocableMethod. The @InvocableMethod annotation exposes Apex methods to flows and process builder.

Answer

@RemoteAction

Answer

@future

Answer

@AuraEnabled

Question 4

A developer needs to write a test class for a Batch Apex job. Which method must be called to verify that the batch job executes correctly?

Accepted Answer

Database.executeBatch() enclosed by Test.startTest() and Test.stopTest(). Database.executeBatch inside Test.startTest() and Test.stopTest() executes the batch job in test context.

Answer

Test.runBatch()

Answer

Test.enqueueJob()

Answer

System.runAs()

Question 5

A developer needs to ensure that a custom logging operation runs asynchronously and can be monitored using job IDs. Which interface is best suited?

Accepted Answer

Queueable. Queueable Apex provides job IDs upon enqueueing, allowing for tracking and monitoring.

Answer

Schedulable

Answer

Database.AllowsCallouts

Answer

Database.Batchable

Question 6

What is a key advantage of using Queueable Apex over future methods?

Accepted Answer

Queueable Apex allows passing sObjects and custom Apex types as member variables.. Queueable Apex supports non-primitive data types and job chaining.

Answer

Queueable Apex executes synchronously on the user thread.

Answer

Queueable Apex has no governor limits.

Answer

Queueable Apex cannot make callouts.

Question 7

A developer writes a Queueable Apex job that queries 50,000 records, performs calculations, and updates them. During testing, the job hits a heap size limit. What is the standard asynchronous heap size limit in Apex?

Accepted Answer

12 MB. The asynchronous transaction heap size limit is 12 MB, compared to 6 MB for synchronous transactions.

Answer

50 MB

Answer

36 MB

Answer

6 MB

Question 8

A developer needs to abort a scheduled Apex job programmatically from within a test class or maintenance script. Which method should be used?

Accepted Answer

System.abortJob(). System.abortJob(jobId) cancels a scheduled or flex-queued asynchronous job.

Answer

System.cancelJob()

Answer

apexJob.terminate()

Answer

Database.stopBatch()

Question 9

Which TWO actions can be performed inside a before insert Apex trigger without causing a runtime exception? (Choose two.)

Accepted Answer

Modifying field values on records in Trigger.new directly without a DML statement.. Option A is correct because in a before insert trigger the records in Trigger.new are not yet committed, so you can assign new field values directly on those sObject instances (e.g., rec.MyField__c = 'X') and Salesforce persists them without any DML statement. Option E is correct because calling addError() on a record in Trigger.new during a before insert trigger marks that record as failed, blocks the save, and surfaces the error message to the user, which is a supported pattern in before triggers. Option B is not valid here because Trigger.oldMap is only populated for update and delete events, so in a before insert trigger it is null and accessing it throws a runtime exception. Option C is not allowed because Apex triggers cannot make synchronous HTTP callouts directly; callouts must be asynchronous (e.g., via @future or Queueable) or handled after the transaction. Option D is not allowed because performing an explicit update DML on records already in Trigger.new causes a runtime exception (a record in Trigger.new cannot be updated with DML in a before trigger).

Answer

Accessing Trigger.oldMap to compare previous values.

Answer

Performing an immediate synchronous HTTP callout to an external REST service.

Answer

Executing an explicit update DML statement on records in Trigger.new.

Question 10

Which TWO tools or features should a developer consider when choosing between Flow Builder and Apex for business logic automation? (Choose two.)

Accepted Answer

Apex is better suited for complex algorithmic logic, advanced error handling, and reusable utility classes.. Option A is correct because Apex is the programmatic choice for complex algorithmic logic, advanced error handling (try/catch, custom exceptions, savepoints), and reusable utility classes that can be invoked across triggers, classes, and even Flows via @InvocableMethod. Option B is correct because Flow Builder is declarative, so administrators can build and modify record-triggered, screen, and scheduled flows quickly without code, improving maintainability and reducing dependency on developers. Option C is wrong because Flows can absolutely call subflows and invocable Apex actions. Option D is wrong because Apex triggers are not universally slower than record-triggered flows; performance depends on implementation, and Apex is often faster for bulk and complex operations. Option E is wrong because large nightly asynchronous batch processing is a classic Apex use case (Batch Apex, Queueable, Schedulable), not a Flow Builder requirement.

Answer

Flows cannot trigger subflows or call invocable actions.

Answer

Apex triggers execute significantly slower than record-triggered flows in all scenarios.

Answer

Flow Builder is required when processing millions of records nightly in asynchronous batches.

Question 11

Which THREE statements are true regarding asynchronous Apex governor limits and execution behavior? (Choose three.)

Accepted Answer

Asynchronous Apex jobs execute in their own separate transaction with independent governor limits.. Asynchronous jobs have higher limits (heap, CPU time), run in separate transactions, and can be monitored via AsyncApexJob.

Answer

Future methods can be chained indefinitely without any depth limitations.

Answer

Batch Apex jobs cannot make external web service callouts.

Question 12

Which TWO features are characteristic of Flow Builder compared to Apex triggers? (Choose two.)

Accepted Answer

Flows provide a visual canvas for building automation logic without writing code.. Flow Builder is declarative, provides visual debugging, and allows point-and-click creation.

Answer

Flows execute entirely on client-side browsers.

Answer

Flows require compilation into bytecode and deployment via metadata APIs or developer toolchains.

Answer

Flows cannot interact with custom objects or custom fields.

Question 13

Which THREE actions can cause a governor limit exception during a poorly optimized trigger execution? (Choose three.)

Accepted Answer

Exceeding the maximum synchronous heap size of 6 MB by loading massive attachments into collections.. Option B is correct because Apex enforces a 6 MB synchronous heap limit, and loading large attachments or bulky data into collections can exceed that heap size and throw a LimitException. Option C is correct because performing DML inside a loop issues one DML statement per record, quickly breaching the 150 DML statement synchronous governor limit. Option E is correct because a SOQL query inside a loop over Trigger.new executes one query per record, exceeding the 100 synchronous SOQL query limit. Option A is not a governor-limit violation: calling a future method from a scheduled Apex execute method is allowed (scheduled Apex can call future methods), and it does not itself cause a limit exception. Option D is not a limit issue: Trigger.old is simply null/unavailable in an insert trigger, which is a runtime behavior rather than a governor limit exception.

Answer

Invoking a future method directly from a scheduled Apex class execute method.

Answer

Accessing Trigger.old in an insert trigger.

Question 14

Which TWO triggers are executed during a record merge operation in Salesforce? (Choose two.)

Accepted Answer

Before Delete and After Delete triggers on the losing record.. Merging records deletes the loser record (firing delete triggers) and updates the winner record (firing update triggers).

Answer

Before Insert and After Insert triggers on the losing record.

Answer

Undelete triggers on both records.

Answer

Lead conversion triggers instead of merge triggers.

Question 15

Which TWO best practices should developers follow when implementing Queueable Apex chaining? (Choose two.)

Accepted Answer

Ensure that chained jobs handle governor limits and bulk data efficiently in each execution context.. Chaining queueable jobs should be conditional to avoid infinite loops and should monitor flex queue limits.

Answer

Chain multiple queueable jobs simultaneously within a single synchronous transaction without limits.

Answer

Use future methods inside queueable execute methods instead of chaining queueable jobs.

Answer

Hardcode all job IDs to ensure static binding between jobs.