AWS Certified Professional AIP-C01 Updated Exam

Option D is correct because troubleshooting a RAG application requires observability across retrieval, generation, and ingestion rather than monitoring infrastructure resources in isolation. Amazon OpenSearch Service exposes search and indexing latency metrics, while Amazon Bedrock publishes InvocationLatency and other inference metrics through CloudWatch. CloudWatch anomaly detection continuously analyzes historical metric behavior and establishes expected-value bands, allowing abnormal latency or ingestion behavior to be identified without maintaining rigid static thresholds. This makes it suitable for detecting gradual performance degradation before a fixed alarm threshold is crossed. Option A is reactive and monitors only part of the pipeline. Option B incorrectly treats instance restarts as a general performance remedy. Option C lacks end-to-end correlation and uses static thresholds that do not adapt to changing workload patterns. AWS Documentation

================

Option A is the correct solution because it uses native Amazon S3 metadata mechanisms to create a consistent, queryable, and model-friendly metadata framework with minimal complexity. S3 system metadata automatically records object creation and modification timestamps, providing reliable and consistent temporal context without additional processing.

Custom user-defined metadata is the appropriate mechanism for storing structured attributes such as author information. These key-value pairs are stored directly with the object, remain consistent across uploads, and can be accessed programmatically by downstream indexing or retrieval systems used by GenAI applications.

S3 object tags are ideal for domain classification because they are designed for lightweight categorization, filtering, and access control. Tags can be standardized across the organization to ensure consistent research domain labeling and can be consumed by search indexes or knowledge base ingestion pipelines without requiring access to the full document body.

Together, system metadata, user-defined metadata, and object tags provide a clean separation of concerns: timestamps for temporal context, metadata for authorship, and tags for classification. This structure allows foundation models to reason about document context (such as recency, domain relevance, and authorship) based on metadata alone, improving retrieval precision and reducing unnecessary token usage.

Options B, C, and D misuse features like Object Lock, access points, Storage Lens, or event notifications for purposes they were not designed for, adding complexity without improving metadata quality or model understanding.

Therefore, Option A best satisfies the metadata consistency, context enrichment, and low-overhead requirements for GenAI-driven document analysis.

Option B is the correct solution because AWS AppConfig is specifically designed to support dynamic configuration management with safe rollout, validation, and rollback, which are explicit requirements in the scenario.

By storing the active model provider configuration in AWS AppConfig, the company can switch between Amazon Bedrock model providers in real time without redeploying Lambda code. AppConfig supports deployment strategies such as canary releases, linear rollouts, and immediate deployments, allowing safe and controlled changes. If a configuration causes issues, AppConfig supports automatic rollback, reducing operational risk.

AWS AppConfig also supports schema validation, ensuring that configuration values such as model identifiers, provider names, or inference parameters are valid before being applied. This prevents misconfiguration from impacting production workloads.

Option A uses Parameter Store, which lacks native rollout strategies, validation, and automated rollback, making it unsuitable for safe real-time switching. Option C requires manual routing changes and code coupling, increasing operational overhead and deployment risk. Option D introduces unnecessary complexity by hosting configuration files in Amazon S3 when AppConfig already supports native hosted configurations.

Therefore, Option B provides the most robust, scalable, and low-maintenance solution for dynamic model switching in a serverless Amazon Bedrock inference architecture.

Option C directly addresses both retrieval relevance and performance scalability. Fixed token chunking breaks semantic continuity in legal texts, causing incomplete context retrieval and degraded response quality. By switching to semantic chunking—based on legal arguments, clauses, or sections—the application preserves contextual integrity, improving retrieval accuracy and reducing hallucinations.

Regenerating embeddings aligned with the new chunk structure also improves vector search efficiency, reducing unnecessary comparisons and helping control latency as the dataset scales.

Option A increases cost and latency without fixing the core issue. Option B removes dynamic reasoning, which defeats the purpose of a legal RAG system. Option D discards vector semantics entirely and is unsuitable for nuanced legal research. Therefore, Option C is the correct and scalable solution.