How to store Amazon Bedrock model invocation logs

AI Services / Amazon Bedrock

An AI practitioner is using an Amazon Bedrock base model to summarize session chats from the customer service department. The AI practitioner wants to store invocation logs to monitor model input and output data. Which strategy should the AI practitioner use?

  1. Configure AWS CloudTrail as the logs destination for the model.
  2. Enable invocation logging in Amazon Bedrock. Source Reference Answer
  3. Configure AWS Audit Manager as the logs destination for the model.
  4. Configure model invocation logging in Amazon EventBridge.

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The question tests knowledge of native Amazon Bedrock monitoring features versus general AWS logging services, with the common trap being the confusion between CloudTrail (control plane) and Bedrock Invocation Logging (data plane).

Amazon Bedrock provides a native feature to enable invocation logging for monitoring model input and output data. The community consensus confirms that enabling this built-in feature is the direct and correct strategy for storing these specific logs.

Community Discussion (3 comments)

Jessiii 👍 1 Selected: B
B. Enable invocation logging in Amazon Bedrock: Amazon Bedrock provides a built-in option to enable invocation logging. This feature allows you to capture and store detailed logs for model invocations, including input and output data, which helps you monitor and analyze the performance and behavior of the model.
Moon 👍 1 Selected: B
B: Enable invocation logging in Amazon Bedrock. Explanation: Amazon Bedrock provides the ability to log model invocations, including input and output data, for monitoring and troubleshooting purposes. By enabling invocation logging in Amazon Bedrock, the AI practitioner can store logs securely and use them to analyze model behavior and performance.
Blair77 👍 2 Selected: B
B - The question mentions using an Amazon Bedrock base model, and invocation logging is a feature specifically designed for Amazon Bedrock.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Option B is correct because Amazon Bedrock includes a built-in 'Invocation Logging' feature specifically designed to capture and store model input and output data. This feature allows practitioners to monitor model performance, troubleshoot issues, and ensure compliance by securely storing these detailed logs.

Why the Other Options Are Wrong

AWS CloudTrail (Option A) primarily logs API calls made to the service (control plane), not the actual payload data of model invocations. AWS Audit Manager (Option C) is used for continuous auditing against frameworks, not for raw invocation storage. EventBridge (Option D) handles event routing but does not inherently provide the persistent storage mechanism for model inputs/outputs in the way Bedrock's native logging does.

Community Comment Notes

Comments [1], [2], and [3] unanimously support Option B, highlighting that invocation logging is a specific feature within Bedrock. They emphasize that this capability is essential for capturing the detailed input/output data required for monitoring and analysis.

Official Reference

Exam Strategy

Always distinguish between control plane logging (CloudTrail) and data plane/logging-specific features when dealing with managed AI services like Bedrock. If the question asks about storing model inputs/outputs, look for the service's native logging configuration first.

Related Analysis

Practice All AIF-C01 Questions

Access 100 questions with complete answers and detailed explanations.

View Full AIF-C01 Practice Test →

← Back to AIF-C01 Study Guide