AIP-C01 practice question: Prompt templates, versioning and governance (Bedrock Prompt Management)

Foundation Model Integration, Data Management, and Compliance A free question from our original AIP-C01 practice exam. Try it, then open the answer to see why each option is right or wrong.

An online bank has five teams that each write prompts for summarizing customer messages, drafting replies and classifying complaints. Today the prompts are copied into each team's code, so the same instruction exists in several slightly different versions.

Audit asks which prompt version produced which reply, and the compliance team must approve each change before any app uses it. A bad change must be rolled back within minutes, without a redeployment of every app.

The prompts use shared variables such as customer name, product type and language, which all teams fill in the same way.

Which TWO actions should the team combine to meet these requirements? (Choose two.)

Choose two answers.

A. Keep each prompt in the team's Lambda code, and tag each release in Git, so that the version of every prompt can be traced to a commit.
B. Create the prompts in Amazon Bedrock Prompt Management with declared input variables, and publish an immutable prompt version for each change that compliance approves.
C. Store the prompt text in a shared S3 bucket, overwrite the file each time a prompt changes, and have every app read the newest file at startup, so all teams always use the same wording.
D. Let each team store its prompts in its own DynamoDB table with no fixed schema, so teams can add or rename fields quickly, and read the latest item in each app.
E. Keep the approved prompt version ARN for each app in AWS AppConfig, deploy changes with a staged strategy and a CloudWatch alarm, and have apps read it through the AppConfig agent.

Show the answer and explanation

Answers: B, E

A. Wrong: Git tags trace code history, but the prompts would still be duplicated across five codebases, and every change would need a redeployment. The shared variables and fast rollback requirements are not met.
B. Right: Prompt Management holds one shared template per task with variables that every team fills in the same way. Each published version is fixed, so audit can match a reply to the exact prompt version that produced it. Learn more: Create and manage prompts with Prompt management (opens in a new tab)
C. Wrong: Overwriting the file erases the earlier versions, so audit cannot see which prompt produced a reply. Apps also read at startup, so a rollback needs a restart of each app.
D. Wrong: Each team's table has its own fields, so variables are not shared in a consistent way. No approval step or version history is built in, so the compliance requirement is not met.
E. Right: Apps read the version ARN at runtime, so moving to a new prompt version or back to an earlier one is a configuration deployment, not an app redeployment. AppConfig can roll back automatically when the alarm fires, which meets the minutes-long rollback target. Learn more: Working with deployment strategies (opens in a new tab)

Explanation

Prompt Management gives one shared template per task with variables, and its immutable versions let audit trace each reply to an approved prompt. AppConfig then controls which version each app uses, so a rollout or rollback is a configuration change with alarm-based rollback instead of a redeployment. Code-held prompts, overwritten files and per-team tables each lose version history, sharing or control.

AIP-C01 practice question: Prompt templates, versioning and governance (Bedrock Prompt Management)

Explanation

Study

Keep practicing