Question 54 — AB-620 Case Study Set
Paideffort is evaluating whether to implement the following architecture immediately:
topic:
input: Topic.ComplianceQuestion
powerAutomateFlow:
actions:
- callRegulatoryApi
- returnResults
topicContinuation:
- transformResults
- createGenerativeAnswers
The flow would contain only the same single API call currently performed by the HTTP request node. The future release, however, will aggregate three systems, apply regional rules, remove superseded records, and rank the final results. Which architecture decision best balances current simplicity with the planned evolution? (Select one answer)
Keep the direct HTTP request and Power Fx transformation now, then move retrieval into a Power Automate flow when the multi-system processing is introduced.
Move the single API request into a Power Automate flow immediately because every Custom data integration should use a flow.
Keep all future multi-system processing directly in the topic because Power Automate adds no value when more than one source is involved.
Replace both designs with the Foundry agent because generative reasoning is required whenever regulatory data comes from multiple systems.
Correct answers
Keep the direct HTTP request and Power Fx transformation now, then move retrieval into a Power Automate flow when the multi-system processing is introduced.
Explanations
Correct Answer:
Keep the direct HTTP request and Power Fx transformation now, then move retrieval into a Power Automate flow when the multi-system processing is introduced.
Explanation:
Paideffort's current phase has one straightforward API call and a simple transformation, so the direct HTTP pattern is efficient and easy to maintain. The future phase introduces aggregation, connector usage, filtering, regional business rules, and ranking. At that point, a Power Automate flow provides a more appropriate orchestration layer and avoids duplicating complex retrieval logic across topics.
Wrong Answers:
Move the single API request into a Power Automate flow immediately because every Custom data integration should use a flow.
Paideffort doesn't currently need the additional orchestration layer. HTTP retrieval is suitable when one call can be reshaped directly with Power Fx.
Keep all future multi-system processing directly in the topic because Power Automate adds no value when more than one source is involved.
The future requirements are precisely the type of aggregation and business-rule complexity for which a flow becomes easier to build and maintain.
Replace both designs with the Foundry agent because generative reasoning is required whenever regulatory data comes from multiple systems.
The retrieval, filtering, ranking, and field mapping can remain deterministic. Paideffort can reserve the generative component for synthesizing the final grounded response rather than using it to replace structured integration logic.