Salesforce Updated PDI Exam Questions and Answers by arjan

Database.insert(records, false):

The Database.insert() method with the allOrNone parameter set to false allows for partial success.

If some records in the list fail due to validation rules, triggers, or other errors, the method will still attempt to insert the remaining valid records.

The false parameter ensures that records that fail will not roll back the transaction for the others.

Why not the other options?

A. Database.insert(records, true):

The true parameter makes the operation transactional (all or none). If any record fails, all records will roll back.

B. insert records:

The insert DML statement behaves like Database.insert(records, true) by default and rolls back all records if any error occurs.

C. insert(records, false):

This syntax is invalid in Apex.

References:

Apex DML Operations Documentation

Database Methods

Why Queueable Class?

Queueable Apex supports callouts and allows chaining to process one record at a time efficiently.

The trigger detects when the Order__c status changes to "Placed" and enqueues the Queueable class to perform the callout.

Why Not Other Options?

B. Batchable class: Batch jobs are ideal for bulk processing but not suited for single REST callouts.

C. Flow with invocable method: Flows are less efficient and limited in handling callouts for large-scale operations.

D. @future method: While it supports asynchronous callouts, it does not allow chaining, making Queueable more suitable.

Queueable Apex: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_queueing_jobs.htm

References: