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

Question 1

What is the synchronous governor limit for the total number of SOQL queries issued in a single Apex transaction?

Accepted Answer

100. The synchronous governor limit for SOQL queries per transaction is 100.

Answer

200 locs

Answer

200

Answer

50

Question 2

A developer is troubleshooting a Batch Apex job where records are failing to update intermittently due to record locking contention with concurrent updates. What is the recommended strategy to mitigate record locking?

Accepted Answer

Process records in smaller batch sizes and ensure parent records are sorted or processed in a deterministic order.. Sorting records in the start method query using FOR UPDATE or structuring batches by parent groups can reduce locking, and processing smaller batch sizes can also help.

Answer

Increase the batch size to the maximum of 2,000 to complete faster.

Answer

Convert the batch job into a synchronous trigger.

Answer

Disable all validation rules on the object permanently.

Question 3

A developer is designing a complex data validation and transformation process. Which TWO scenarios are best implemented using an Apex Trigger rather than a Record-Triggered Flow? (Choose TWO.)

Accepted Answer

Executing complex custom algorithms requiring recursive method calls and dynamic exception handling across multiple wrapper classes.. Apex triggers excel at complex integrations (callouts) and custom exception handling across multiple distinct object hierarchies that exceed declarative flow capabilities.

Answer

Sending a standard email notification template when a status changes.

Answer

Updating a simple custom field on the same record before it is saved.

Answer

Creating a task for a lead owner upon lead assignment.

Question 4

How many times can a single transaction chain Queueable Apex jobs by submitting a new job from within an executing Queueable job?

Accepted Answer

50 future methods per Apex transaction. Starting in recent Salesforce releases, chained queueable jobs have generous limits (up to 50 child chains in synchronous transactions, or higher depending on release updates), but traditionally 1 child chain per execution was standard, and currently chaining depth can go up to stack limits. Wait, the documented chaining limit for asynchronous queueable chaining is up to 5 chained jobs in asynchronous context in older limits, but recently expanded. Let's frame it around standard best practice or known limits. Actually, let's test a different concept to be safe against release changes: max future methods per transaction.

Answer

500 future methods per Apex transaction

Answer

10 future methods per Apex transaction

Answer

100 future methods per Apex transaction

Question 5

Which THREE limitations apply to Apex Triggers? (Choose THREE.)

Accepted Answer

Triggers cannot perform DML statements directly without bulkification consideration (though syntax allows it, governor limits prevent it). Let's use: Triggers cannot use return types or be called directly from user interface buttons without wrapper classes/flows.. Apex triggers have specific platform limitations. They cannot make synchronous outbound callouts (must use asynchronous processes like @future or Queueable). They have a maximum trigger recursion stack depth of 16. Additionally, triggers cannot be called directly from the user interface or return values directly, and they execute in batches of up to 200 records (meaning platform limits apply to chunk sizes, but more importantly, triggers cannot exceed governor limits on DML). Wait, let's fix the options to be standard Salesforce multiple-choice questions.

Answer

Triggers cannot be defined on standard objects, only custom objects.

Answer

Triggers cannot process more than 200 records in a single batch chunk.

Question 6

Which THREE trigger context variables are available ONLY in insert and update triggers (not delete triggers)? (Choose THREE.)

Accepted Answer

Trigger.newMap. Wait, let's look closely at the question. 'Which THREE trigger context variables are available ONLY in insert and update triggers (not delete triggers)?' Trigger.new, Trigger.newMap, and Trigger.old are listed in options? No, option C is Trigger.old. Trigger.old is available in update and delete, NOT insert. Wait, the prompt says 'available ONLY in insert and update triggers (not delete triggers)'. Trigger.old is available in delete triggers. Trigger.oldMap is available in delete triggers. Trigger.new and Trigger.newMap are NOT available in delete triggers. What about Trigger.isInsert? That's a boolean context variable, available in all triggers.

Answer

Trigger.isInsert and Trigger.isUpdate

Answer

Trigger.oldMap

Question 7

A developer needs to invoke a long-running external web service callout from an existing scheduled Apex job that implements the Schedulable interface. What is the correct approach to implement this callout?

Accepted Answer

Enquie a Queueable Apex class that implements Database.AllowsCallouts from within the Schedulable execute method.. Schedulable Apex cannot directly make synchronous callouts because the thread must wait for the network response. Developers must chain a Queueable class that implements Database.AllowsCallouts.

Answer

Mark the Schedulable execute method with the @future(callout=true) annotation.

Answer

Implement Database.AllowsCallouts directly in the Schedulable class and execute the callout inside the execute method.

Answer

Invoke the external web service using a standard synchronous SOQL statement.

Question 8

A developer needs to chain multiple asynchronous jobs sequentially where Job B must run only after Job A finishes successfully. Which interface should the developer use to achieve this?

Accepted Answer

System.Queueable. Queueable Apex provides the ability to chain jobs by calling System.enqueueJob() from within the execute method of a currently running Queueable job.

Answer

Database.AllowsCallouts

Answer

System.Schedulable

Answer

Database.Batchable

Question 9

A developer has a Queueable Apex job that needs to query large volumes of data and perform updates. To optimize performance and avoid heap size limits, what is the best practice when querying records inside a Queueable Apex job?

Accepted Answer

Use a SOQL for-loop to iterate over query results chunk by chunk.. Using a SOQL for-loop (e.g., `for (Account a : [SELECT Id FROM Account])`) processes records in chunks of 200 via internal datatable iteration, which helps prevent heap size limit exceptions when dealing with large volumes of data in Apex. Option C suggests switching to Batchable, which does not answer how to optimize the current Queueable job. Options A and B either worsen heap size issues or are not valid for Queueable Apex execution contexts in this manner.

Answer

Assign all queried records to a single global List variable in the class.

Answer

Set the method execution context to read-only using @ReadOnly.

Answer

Implement the Database.Batchable interface instead of Queueable.

Question 10

A developer needs to schedule an Apex class to run weekly. Which syntax correctly schedules the job using System.schedule?

Accepted Answer

System.schedule('Weekly Job', '0 0 0 ? * MON *', new MySchedulableClass());. System.schedule requires a job name, a valid CRON expression, and an instance of the Schedulable class.

Answer

System.scheduleBatch(new MySchedulableClass(), 'Weekly Job', 200);

Answer

System.enqueueJob(new MySchedulableClass(), '0 0 0 ? * MON *');

Answer

System.schedule(new MySchedulableClass(), '0 0 0 ? * MON *');

Question 11

A developer implements a Batch Apex class that updates millions of records. During the execution of the execute method, a transient database error occurs on a single record. What happens to the batch job by default if Database.executeBatch is called without additional parameters?

Accepted Answer

The entire batch job fails immediately, and no further chunks are processed.. By default, if an unhandled exception occurs in a batch chunk, the entire batch job fails and the error is logged, unless Database.insert is used with allOrNone set or exception handling is implemented.

Answer

The failed record is placed in a retry queue for asynchronous reprocessing.

Answer

Only the failed record is rolled back, and the batch continues processing the remaining records.

Answer

The entire database transaction is rolled back, but the batch continues to the next execute method.

Question 12

Which governor limit applies specifically to the total number of asynchronous Apex executions (such as future methods and queueable jobs) enqueued in a 24-hour period for an Enterprise Edition org?

Accepted Answer

10,000 or 2.5 times the number of user licenses, whichever is greater. The asynchronous Apex execution limit restricts the total number of future calls, queueable jobs, and scheduled jobs that can be enqueued per 24 hours.

Answer

100 SOQL queries per transaction

Answer

6MB heap size limit

Answer

50 DML statements per transaction

Question 13

A developer has an Apex trigger that fires on Account update. Inside the trigger, it calls a future method to update related Contact records. During testing with 150 Account records modified simultaneously, the developer receives a System.LimitException: Too many future calls. What is the cause of this exception?

Accepted Answer

The trigger exceeded the maximum limit of 50 future method calls per Apex transaction.. Future methods cannot be called from within other asynchronous contexts or inside triggers when the trigger processes more records than the future call limit allows per transaction (e.g. max 50 future calls per transaction).

Answer

The total daily asynchronous limit was reached.

Answer

Future methods cannot be invoked from inside an Apex trigger context.

Answer

The future method tried to execute a SOQL query exceeding the limit.

Question 14

During the Salesforce order of execution, which THREE actions occur AFTER the system executes 'after' triggers? (Choose three.)

Accepted Answer

Execution of Assignment Rules.. In Salesforce's order of execution, after 'after' triggers run, the system proceeds to execute Assignment Rules (option A), which route leads and cases to the appropriate owners or queues. Next, escalation rules and roll-up summary field calculations are performed (option B), handling case escalation and updating summary fields on parent records. Then Workflow rule field updates are executed (option C), applying any field update actions defined in workflow rules. Options D and E are incorrect because before insert triggers and custom validation rules both execute earlier in the order of execution, before 'after' triggers are fired.

Answer

Execution of before insert triggers.

Answer

Execution of custom validation rules.

Question 15

A developer is designing a Batch Apex class that processes millions of records. Which THREE elements are required components of a valid Batch Apex implementation? (Choose three.)

Accepted Answer

Implementation of the start method returning a Database.QueryLocator or Iterable.. Batch Apex classes must implement the Database.Batchable interface and define start, execute, and finish methods.

Answer

Implementation of the Database.AllowsCallouts interface automatically.