AIP-C01 Exam Dumps - Amazon Web Services AWS Certified Professional Questions and Answers

Option C best satisfies the requirements because it combines application-aware observability, metric baselining, anomaly detection, and correlated alerting using fully managed AWS services with minimal operational overhead. Amazon CloudWatch Application Insights is designed to automatically monitor application health by analyzing metrics, logs, and events across EC2-based workloads. This aligns directly with the need to detect intermittent performance issues and deviations from expected behavior.

By publishing custom metrics using the CloudWatch embedded metric format, the application can track generative AI–specific signals such as recommendation quality indicators, token usage, request volume, and response latency from Amazon Bedrock foundation model calls. Adding di mensions such as request type or user segment enables fine-grained visibility into which workloads or customer groups are impacted when recommendation quality degrades.

A critical requirement is detecting degradation compared to established baselines and generating alerts within 10 minutes. CloudWatch anomaly detection automatically builds statistical models of normal behavior for time-series metrics and flags deviations without requiring manually tuned thresholds. This capability is well suited for monitoring foundation model behavior, which can vary subtly over time. When anomalies are detected, CloudWatch alarms can trigger notifications with contextual metric data quickly, meeting the alerting requirement.

CloudWatch Logs Insights complements the metric-based view by enabling log pattern analysis and correlation. Engineers can query application logs and model response logs to identify recurring error patterns or shifts in output behavior that explain why recommendations no longer align with user preferences. Application Insights further correlates metrics and logs to surface probable root causes, reducing mean time to resolution.

The other options lack one or more critical elements. Option A focuses on infrastructure-level metrics without baseline anomaly detection. Option B emphasizes tracing and auditing but does not provide automated performance deviation analysis. Option D offers flexibility but requires significantly more development and operational effort than a native CloudWatch-based solution.

Option B is the correct solution because Amazon Bedrock provisioned throughput is only used when the application explicitly invokes the provisioned model ARN, not the base foundation model ID. In the provided code, the application is calling the standard model identifier (anthropic.claude-v2), which routes requests to on-demand capacity instead of the purchased provisioned throughput.

When the CreateProvisionedModelThroughput API is used, Amazon Bedrock returns a provisioned model ARN that represents the reserved capacity. Applications must reference this ARN in the modelId parameter when invoking the model. If the base model ID is used instead, Bedrock treats the request as on-demand traffic, which explains why CloudWatch metrics show unused provisioned capacity alongside throttled on-demand requests.

Option A would increase capacity but would not fix the root cause because the application is not using the provisioned resource at all. Option C adds resiliency but does not ensure usage of provisioned throughput and would still incur throttling. Option D changes the response delivery mechanism but does not affect capacity routing.

Therefore, Option B directly resolves the throttling issue by correctly routing traffic to the reserved capacity and ensures that the company benefits from the provisioned throughput it has purchased.

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 A is correct because Amazon Bedrock Guardrails provides a native sensitive-information filter for personally identifiable information. The filter can detect supported PII types and use the MASK action so detected values in model requests or responses are replaced with placeholders such as the PII type. This directly satisfies the requirement to mask PII from foundation model responses with minimal operational effort. It avoids creating and maintaining an additional preprocessing pipeline. Option B can detect or redact PII with Amazon Comprehend, but it requires Lambda logic and data-processing workflows before Bedrock invocation. Options C and D require scanning, copying, and segregating objects across S3 buckets and still do not directly enforce response masking. For response-level protection in Bedrock, the managed Guardrails capability is the simplest and most purpose-built control. AWS Documentation

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

Option C is the technically supportable choice under current AWS documentation. Amazon Bedrock prompt caching does not provide semantic caching for differently worded or cross-language questions; it reuses cached prompt content through matching prompt prefixes or defined cache checkpoints. Therefore, Option B ' s assumption that Bedrock prompt caching automatically recognizes semantically equivalent multilingual queries is incorrect, even though many supported models provide a 5-minute prompt-cache TTL. ElastiCache for Redis OSS supports application-controlled cache entries and TTLs, while Global Datastore provides managed cross-Region replication and low-latency geographic reads. A multilingual semantic fingerprint can normalize equivalent requests to a shared cache key before inference. Options A and D similarly lack built-in semantic equivalence handling, while DAX is specifically a DynamoDB caching layer. Thus, C is the viable architecture among the listed choices.

Amazon Bedrock Prompt Management is the purpose-built service for prompt lifecycle management. it provides native version control , allowing developers to test and compare variants side-by-side. Use of parameterized variables ensures that a single prompt structure can be consistently reused across different sub-applications (assistants vs. graders) while still being tailored to the specific context. To " integrate into the main application " with minimal overhead, Amazon Bedrock Flows provide a managed orchestration layer. Flows allow developers to link managed prompts with AWS services (like knowledge bases or Lambda functions) without writing complex state-machine logic in Step Functions (Option B). This combination ensures consistent, auditable, and easily deployable prompt assets across the university ' s diverse use cases.

AWS Glue Data Catalog and its associated crawlers are the standard AWS tools for automatic discovery and centralized cataloging of datasets. For the generated summaries, storing them in Amazon S3 allows the use of object tags for metadata (like source IDs), making them easily queryable. The critical requirement for " tamper-evident, immutable audit logs " is met by enabling Bedrock model invocation logging to an S3 bucket protected by S3 Object Lock (compliance mode). To further guarantee that logs have not been altered, AWS CloudTrail log file integrity validation uses cryptographic hashes to provide non-repudiation and a verifiable audit trail. This combination covers data management, metadata attribution, and high-standard security compliance.

Option D is correct because it separates the United States and European workloads and uses the correct Amazon Bedrock inference pattern for European data residency. AWS documentation states that geographic cross-Region inference keeps data processing within specified geographic boundaries such as US, EU, and APAC, and is intended for organizations with data residency and compliance requirements. The regional availability documentation further explains that a geographic profile routes within a defined geography and that prompts and outputs may move within that geography but not outside it. This directly satisfies the requirement that European customer data must be processed only in Europe-based AWS Regions.

Provisioned throughput is appropriate for the US workload because the system has a demanding and predictable performance target: 1,000 transactions per second with sub-500 ms response times. Provisioned capacity is generally used when an application needs reserved throughput and consistent performance rather than depending only on on-demand capacity. Automatic scaling based on utilization metrics supports changing demand while maintaining performance. EventBridge and Lambda can coordinate failover workflows or routing updates when connectivity disruptions occur, supporting high availability across Regions.

Option A is not the best answer because it includes a global inference profile. AWS documentation states that global cross-Region inference can route requests across supported commercial AWS Regions worldwide and has no geographic data-residency restriction. AWS explicitly notes that organizations with data residency or compliance requirements should assess whether global cross-Region inference fits their framework because requests may be processed in other supported commercial Regions. That conflicts with the European data processing requirement.

Option B uses separate Regional provisioned throughput, but it relies on a custom Application Load Balancer approach for Bedrock routing and does not use the Bedrock geographic inference profile that is designed for EU data residency. Option C uses response streaming, which improves perceived response latency for text generation but does not guarantee sub-500 ms fraud-processing latency or European-only processing. Therefore, option D is the most complete AWS-aligned solution.

When a foundation model fails to include specific required content or fails to integrate it coherently, prompt engineering techniques like output indicators or " wrappers " are highly effective. By explicitly defining where the promotional message should appear (e.g., " The response must end with the following message: [PROMO TEXT] " ) or providing an example output structure, the developer reinforces the constraint within the model ' s generation path. This is more direct and less computationally expensive than generating multiple variants and reranking them (Option B) or adding complex post-processing layers (Option C). Guardrails (Option A) are intended for filtering harmful content rather than enforcing specific promotional copy insertion.

Amazon Bedrock AgentCore Observability is the best fit because the requirement is specifically for built-in Amazon Bedrock visibility into agent interactions, tool behavior, and failures without custom instrumentation. AWS documentation states that AgentCore provides built-in metrics, logs, and traces for AgentCore modular services, and that this data can be viewed in Amazon CloudWatch. AgentCore observability also supports sessions, traces, and spans, where traces represent full request-response cycles and spans represent operations inside a trace. This directly matches the need to analyze multi-agent interactions, tool invocations, latency, throttling, and error behavior during peak traffic.

Option A is also correct because Amazon Bedrock AgentCore integrates with AWS X-Ray for distributed tracing of AI agents and tools. AWS X-Ray support helps follow requests across service boundaries and identify performance bottlenecks in agent and tool execution. CloudWatch provides curated GenAI observability views for AgentCore and can show operational health, metrics, traces, sessions, and error breakdowns. This gives the developer end-to-end visibility with minimal additional overhead because the core telemetry is service-provided rather than extracted through a custom pipeline.

Option B is incorrect because Container Insights focuses on container infrastructure and would not provide native visibility into Bedrock AgentCore agent reasoning paths or tool-level traces. Polling APIs with Lambda adds custom logic and operational overhead. Option C is incorrect because a custom ETL pipeline, DynamoDB storage, and QuickSight reporting do not satisfy the “built-in Amazon Bedrock capabilities” and “minimal overhead” requirements. Option D starts correctly with AgentCore Observability, but then adds custom Lambda processing and Grafana, which introduces unnecessary custom instrumentation and processing. Therefore, option A is the most AWS-aligned solution.

==========