Salesforce Certified Platform Data Architect Practice Questions

Salesforce Certified Platform Data Architect exam preparation

Salesforce Certified Platform Data Architect practice questions in English: 177 questions with explanations. The mock exam has 60 questions and 105 minutes.

Salesforce Certified Platform Data Architect free question 1 / 10 · Domain 1: Data Modeling/Database Design

When an opportunity is won, you want the opportunity flow to write a record of the win to a custom big object, Win History. Which design matches the considerations in the Big Objects Implementation Guide (Spring '23)?

  1. Have the flow call asynchronous Apex, such as a Queueable class, to write the records
  2. Lock the opportunity record before writing, and group the inserts in synchronous Apex
  3. Commit the insert into Win History in the same transaction as the opportunity update
  4. Use the flow's create records element and write to Win History synchronously, one record at a time
Show the answer and explanation

Answer: A

Why this is correct
The Big Objects Best Practices say that big objects don't support transactions. If you attempt to read or write a big object using a trigger, process, or flow on an sObject, use asynchronous Apex. Asynchronous Apex has features like the Queueable interface that isolates DML operations on different sObject types to prevent the mixed DML error.

Why the other options are wrong
"Use the flow's create records element and write to Win History synchronously, one record at a time" … The guide says big objects don't support transactions and that a trigger, process, or flow on an sObject should use asynchronous Apex to read or write one. Writing synchronously is the opposite of its advice.
"Commit the insert into Win History in the same transaction as the opportunity update" … Big objects don't support transactions, so the insert cannot be committed together with the opportunity update. The guide uses asynchronous Apex, such as Queueable, to isolate the DML and avoid the mixed DML error.
"Lock the opportunity record before writing, and group the inserts in synchronous Apex" … The guide's answer is asynchronous Apex, not locking. A big object has no transaction, so locking the opportunity does not protect the write to the big object as one unit.

Where people trip
A big object holds large volumes of records such as history and usage logs. If you treat it like an ordinary object and write it inside the same transaction, it fails. When a business object's update is the trigger, design the write as an asynchronous step from the start.

Go to the Salesforce Certified Platform Data Architect practice app (10 free questions; purchase unlocks all questions)

See the full practice set