A historic canal-inn keeps losing the good prompt in chat logs. Which AWS feature lets the team store, share, and retrieve a named prompt version?
Select an answer to reveal the explanation.
Short Explanation
Think of losing the good prompt in chat logs. Bedrock Prompt Management stores, shares, and retrieves a named version. Polly and a laptop log are not that shelf.
Full Explanation
Teams that keep “the good prompt” only in chat logs lose reproducibility, sharing, and rollback for the historic canal-inn reservation helper. Amazon Bedrock Prompt Management is the in-scope feature for storing, sharing, and retrieving a named prompt version so the working template has an identity outside ephemeral chats. That correct choice works because operations need a named, retrievable artifact staff can promote, share across roles, and roll back when edits go wrong. A vector store indexes embeddings for similarity search; it is not a prompt versioning or sharing system for human-edited instruction text. Amazon Polly synthesizes speech and does not store prompt versions for the inn. An unnamed laptop chat log provides neither shared access control nor reliable version history across front-desk staff. Exam caveat: storing a prompt version is not the same as validating it—versioned prompts still need evaluation before promotion to the live assistant. Operational check: save the known-good canal-inn prompt under a named version, retrieve it from another workstation or IAM role, and confirm the retrieved text matches the approved template. Restrict who can publish a new prompt version so informal chat edits cannot silently become production.