nerdexam
Amazon

AIP-C01 · Question #50

A company deploys multiple Amazon Bedrock-based generative AI (GenAI) applications across multiple business units for customer service, content generation, and document analysis. Some applications…

The correct answer is C. Create custom Amazon CloudWatch dashboards that combine native Amazon Bedrock token and D. Create dashboards that show token usage trends and patterns across the company's FMs by. The combination of Options C and D delivers comprehensive, real-time observability for Amazon Bedrock workloads with the least operational overhead by relying on native integrations and managed services. Amazon Bedrock publishes built-in CloudWatch metrics for model invocations…

Deployment, Operations, and Optimization

Question

A company deploys multiple Amazon Bedrock-based generative AI (GenAI) applications across multiple business units for customer service, content generation, and document analysis. Some applications show unpredictable token consumption patterns. The company requires a comprehensive observability solution that provides real-time visibility into token usage patterns across multiple models. The observability solution must support custom dashboards for multiple stakeholder groups and provide alerting capabilities for token consumption across all the foundation models that the company's applications use. Which combination of solutions will meet these requirements with the LEAST operational overhead? (Select TWO.)

Options

  • AUse Amazon CloudWatch metrics as data sources to create custom Amazon QuickSight
  • BUse CloudWatch Logs Insights to analyze Amazon Bedrock invocation logs for token
  • CCreate custom Amazon CloudWatch dashboards that combine native Amazon Bedrock token and
  • DCreate dashboards that show token usage trends and patterns across the company's FMs by
  • EImplement Amazon EventBridge rules to capture Amazon Bedrock model invocation events.

How the community answered

(59 responses)
  • A
    15% (9)
  • B
    32% (19)
  • C
    44% (26)
  • E
    8% (5)

Explanation

The combination of Options C and D delivers comprehensive, real-time observability for Amazon Bedrock workloads with the least operational overhead by relying on native integrations and managed services. Amazon Bedrock publishes built-in CloudWatch metrics for model invocations and token usage. Option C leverages these native metrics directly, allowing teams to build centralized CloudWatch dashboards without additional data pipelines or custom processing. CloudWatch alarms provide threshold-based alerting for token consumption, enabling proactive cost and usage control across all foundation models. This approach aligns with AWS guidance to use native service metrics whenever possible to reduce operational complexity. Option D complements CloudWatch by enabling advanced, stakeholder-specific visualizations through Amazon Managed Grafana. The zero-ETL integration allows Bedrock and CloudWatch metrics to be visualized directly in Grafana without building ingestion pipelines or managing storage layers. Grafana dashboards are particularly well suited for serving different audiences, such as engineering, finance, and product teams, each with customized views of token usage

Topics

#Generative AI Observability#Amazon Bedrock Monitoring#CloudWatch#Data Lake Analytics

Community Discussion

No community discussion yet for this question.

Full AIP-C01 Practice