County analysts who are not professional developers need to compose internal research assistants from approved prompt steps. Which development approach fits that requirement?
Select an answer to reveal the explanation.
Short Explanation
Prompt Flows are the Lego kit for analysts—snap approved steps together without becoming full-time engineers. Counties get governed research assistants without turning every policy person into a Lambda developer.
Full Explanation
County analysts who are not professional developers still need to compose internal research assistants from approved prompt steps. Amazon Bedrock Prompt Flows fit that requirement: low-code assembly of governed multi-step FM workflows without writing custom application code for every research path. Flows keep prompts, tools, and sequencing inside an administrable construct so policy teams can iterate under IT governance rather than becoming Lambda engineers.
Requiring every analyst to hand-author production Lambda and IAM policies before asking a question fails by concept: it blocks legitimate research with infra expertise they do not have and increases misconfiguration risk. Disabling prompt tooling and allowing only raw unrestricted Bedrock console chats with no flows fails governance—no repeatable steps, weak auditability, and easy drift from approved procedures. Training a classical random-forest model on spreadsheets and abandoning foundation models fails the stated GenAI research-assistant need entirely.
Exam caveat: Prompt Flows reduce code burden but do not remove the need for IAM least privilege, data classification, and human review of prompts that touch sensitive county records. “Approved prompt steps” implies versioning and change control; unmanaged personal console chats are not a substitute for flows when consistency and audit matter.
Operational check: have a non-developer analyst assemble a multi-step research flow from approved nodes, run it against a sanitized knowledge source, confirm outputs stay within allowed tools, and verify an admin can review flow versions and permissions without granting the analyst broad IAM write access to production Lambdas.