• ¿Documento equivocado? Cámbialo gratis
  • Escrito por estudiantes que aprobaron
  • Inmediatamente disponible después del pago
  • Leer en línea o como PDF
Vender
¿Dónde estudias?
Tu idioma
Document preview thumbnail
Vista previa 3 fuera de 18 páginas
Otro

AB-400 Power Platform Developer Associate PDF Practice

Document preview thumbnail
Vista previa 3 fuera de 18 páginas

Download the Latest AB-400 Power Platform Developer Associate PDF Practice For Preparation– Verified by Experts. Get fully prepared for the exam with this comprehensive PDF from PassQuestion. It includes the most up-to-date exam questions and accurate answers, designed to help you pass the exam with confidence.

Vista previa del contenido

Microsoft AB-400 Exam

Extending Microsoft Power Platform
Solutions with Code and AI
https://www.passquestion.com/ab-400.html




35% OFF on All, Including AB-400 Questions and Answers


Pass AB-400 Exam with PassQuestion AB-400 questions and
answers in the first attempt.

https://www.passquestion.com/






,1.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.
Answer: D
Explanation:
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.
A - Incorrect: The Booking update has the required transaction boundary, but synchronous
PostOperation still runs inside the Create transaction. The carrier call would occur before commit,
violating the required notification timing.
B - Incorrect: For this top-level request, PreValidation precedes the main transaction, so its Booking
update does not share the required rollback boundary. A nested operation invoked by a transactional
extension can already be in a transaction at PreValidation, but that exception does not apply here.
C - Incorrect: Asynchronous PostOperation runs after Shipment creation completes. A subsequent failure
updating Booking cannot roll back the original Shipment creation, so the two Dataverse changes are not
atomic.
D - Correct: Synchronous PreOperation keeps the Booking update within the original Create transaction.
Asynchronous PostOperation places carrier notification outside that transaction and after successful
completion, satisfying both boundaries.

2.A standard Dataverse Order table has a decimal Amount column. Both the model-driven app and a
Web API integration must receive an error before an Order with a negative Amount is committed.
An active business rule has this configuration:
Scope: All Forms
Condition: Amount < 0
Action: Show an error message on Amount
The model-driven form blocks a save with Amount = -10. An ordinary Dataverse Web API Create request
with Amount = -10 succeeds.
The architect considers the existing validation sufficient for both callers.
Which revision corrects the enforcement gap?
A. Change the business rule's scope to the main Order form, retaining its condition and error action.
B. Change the business rule's scope to Entity, retaining its condition and error action.




, C. Keep the business rule and add an OnSave JavaScript check for negative amounts to all Order forms.
D. Keep the business rule and add an asynchronous PostOperation plug-in on Order Create to check for
negative amounts.
Answer: B
Explanation:
The same negative amount is blocked through the form but accepted through the Web API. The active
rule's condition works, but its scope does not cover both callers. All Forms scope applies to model-driven
forms; Entity scope also applies on the server. Changing the scope therefore provides server
enforcement while retaining the supported numeric condition and error action. An asynchronous server
check addresses a different boundary: it runs after the record operation completes and cannot reject the
original Create request.
A - Incorrect: A specific-form scope applies only to that model-driven form. Assigning the rule to the main
Order form narrows its form coverage and does not enforce it for Web API requests.
B - Correct: Entity scope applies to model-driven forms and the server. The numeric condition and error
action can remain declarative, so changing the scope supplies the missing enforcement boundary
without requiring custom code.
C - Incorrect: An OnSave script provides client-side validation when the relevant form event runs. Direct
Web API requests do not execute that form event, so the integration remains unprotected.
D - Incorrect: An asynchronous PostOperation plug-in runs after the record operation completes, outside
the original transaction. It can detect a negative amount afterward, but it cannot prevent that amount
from being committed by the original Create request.

3.A Power Platform app calls an HTTP-triggered Azure Function to generate a report that normally takes
six minutes. The app requires the initiating call to return within three seconds. Users must later retrieve
either the report or failure details, including after the function host has restarted.
The six-minute processing duration is within the selected hosting plan's execution limit.
Which implementation should you choose?
A. Generate the report in the HTTP-triggered function, persist its outcome, and return a request ID with
the report after processing ends.
B. Queue the request and return a request ID after enqueueing succeeds. Use a queue-triggered worker
to persist status and outcomes in durable storage for a status endpoint.
C. Queue the request and return a request ID after enqueueing succeeds. Use a queue-triggered worker
to keep status and outcomes in process memory for a status endpoint.
D. Start report processing as a background task in the HTTP-triggered function and return a request ID
immediately. Have that task persist status and outcomes in durable storage for a status endpoint.
Answer: B
Explanation:
The report cannot finish within the initiating call's three-second deadline. Successful queue submission
can be acknowledged with a request ID while a queue-triggered worker performs the work. A status
endpoint backed by durable status and outcome data lets the app retrieve the report or failure details
after host restarts. The initial acknowledgment means accepted, not completed. The worker must still
respect its hosting plan's execution limit.
A - Incorrect: The hosting plan permits six minutes of processing, but waiting for the report before
returning violates the app's three-second response deadline. Persisting the outcome does not shorten

Información del documento

Subido en
14 de noviembre de 2026
Número de páginas
18
Escrito en
2026/2027
Tipo
Otro
Personaje
Desconocido
Gratis
Descarga

¿Documento equivocado? Cámbialo gratis Dentro de los 14 días posteriores a la compra y antes de descargarlo, puedes elegir otro documento. Puedes gastar el importe de nuevo.
Escrito por estudiantes que aprobaron
Inmediatamente disponible después del pago
Leer en línea o como PDF

Vendido
71
Seguidores
0
Artículos
117
Última venta
10 horas hace



Por qué los estudiantes eligen Stuvia

Creado por compañeros estudiantes, verificado por reseñas

Calidad en la que puedes confiar: escrito por estudiantes que aprobaron y evaluado por otros que han usado estos resúmenes.

¿No estás satisfecho? Elige otro documento

¡No te preocupes! Puedes elegir directamente otro documento que se ajuste mejor a lo que buscas.

Paga como quieras, empieza a estudiar al instante

Sin suscripción, sin compromisos. Paga como estés acostumbrado con tarjeta de crédito y descarga tu documento PDF inmediatamente.

Student with book image

“Comprado, descargado y aprobado. Así de fácil puede ser.”

Alisha Student

Preguntas frecuentes