Microsoft Certified: Power Platform Developer Associate · AB-400
Test your free AB-400 learning scope
Sign in to practice every question included in the free learning topics, review explanations, and save your results.
How free practice works
Build confidence before your next step
Your account keeps attempts, review data, and the free study tools connected.
- 1
Sign in or register
Create a free account before starting a test.
- 2
Answer included questions
Practice questions from the included free learning topics.
- 3
Review your results
See explanations and knowledge-domain feedback immediately.
Your free test
Practice the included free learning topics
Each attempt selects from the questions inside the administrator-selected free learning topics.
Public question sample
Preview the question format
See the answer and explanation before starting your own practice test. This sample remains the same while it is available.
An integration submits a top-level Create request for a Shipment row in a standard Dataverse table. Custom code must also update a related Booking row. Both Dataverse changes must commit or roll back together. A carrier service must be notified only after those changes commit. Notification can complete later, and carrier failures must not reject shipment creation.
Which implementation should you choose?
- A.Use a synchronous PreOperation plug-in to update Booking and a synchronous PostOperation plug-in to notify the carrier.
- B.Use a synchronous PreValidation plug-in to update Booking and an asynchronous PostOperation plug-in to notify the carrier.
- C.Use an asynchronous PostOperation plug-in to update Booking and then notify the carrier.
- D.Use a synchronous PreOperation plug-in to update Booking and an asynchronous PostOperation plug-in to notify the carrier.Correct answer
Why this is correct
A synchronous PreOperation plug-in runs within the Shipment Create transaction, allowing a propagated exception to roll back both Dataverse changes. An asynchronous PostOperation plug-in runs after the record operation completes and outside that transaction, placing carrier notification after commit. Synchronous PostOperation still participates in the transaction: it follows the main operation, not the transaction's commit.
Subject coverage
Knowledge domains covered in this subject
These weights describe the full subject blueprint. Free-test questions are selected randomly from the available question pool.
Build Microsoft Power Platform solutions (15–20%)20%
Extend the user experience (25–30%)25%
Extend Microsoft Power Platform (35–40%)40%
Develop integrations (10–15%)15%