The correct action is Enable invocation logging in Amazon Bedrock. This setting captures both model input and output payloads so the team can store requests and responses for audit and troubleshooting without building custom pipelines.

Enable invocation logging in Amazon Bedrock is a native Bedrock capability that records invocation payloads and writes them to configured destinations so you get full request and response context for debugging and compliance. Enabling this feature meets the requirement directly because Bedrock produces the logs and preserves the model I O data.

Configure AWS CloudTrail as the logs destination for the model is incorrect because CloudTrail focuses on control plane API activity and management events and it does not capture full model request or response bodies.

Configure model invocation logging in Amazon EventBridge is incorrect because EventBridge is an event routing service and not a feature that itself captures or stores detailed invocation payloads.

Send model logs directly to Amazon CloudWatch Logs is insufficient on its own because CloudWatch Logs is a destination and does not create invocation payload logs unless invocation logging is enabled in the Bedrock service.

Full AWS Practitioner Certification Question