AIP-C01 Exam Dumps - AWS Certified Generative AI Developer - Professional

Option B is correct because authoritative route and fare calculations must remain outside the language model. AgentCore Gateway can expose backend APIs and Lambda functions as governed tools through a unified interface, allowing the agent to discover and invoke the appropriate service while the deterministic business systems calculate routes, fares, accessibility constraints, and disruptions. Strict tool schemas constrain inputs and outputs, while the model can be limited to interpreting user intent and explaining returned results rather than inventing prices. AgentCore observability provides traces of tool calls and execution paths for regulatory review. New services can be added as Gateway targets without retraining the model. Option A relies on prompt instructions, which cannot guarantee deterministic fares. Option C lets the model synthesize answers from documents. Option D improves orchestration but still does not establish authoritative deterministic tool boundaries. AWS Documentation

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

Option B is the most appropriate solution because it directly aligns with AWS-recommended architectural patterns for building scalable, observable, and resilient generative AI applications on Amazon Bedrock. The requirements clearly distinguish between simple and complex routing decisions, and this option addresses both in an optimal way.

Simple routing based on file extension is latency sensitive. Handling this logic directly in the application code avoids unnecessary orchestration, state transitions, and service calls. This approach ensures that straightforward requests, such as routing images to vision-capable foundation models or text files to language models, are processed with minimal overhead and maximum performance.

For complex routing based on content semantics, AWS Step Functions is specifically designed for multi-step workflows that require analysis, branching logic, and error handling. Semantic routing often requires inspecting meaning, intent, or structure before selecting the appropriate foundation model. Step Functions enables this by orchestrating analysis steps and applying conditional logic to determine the correct model to invoke using the Amazon Bedrock InvokeModel API.

A key requirement is detailed execution history. Step Functions provides built-in execution tracing, including state inputs, outputs, and error details, which is essential for auditing, debugging, and compliance. Additionally, Step Functions supports native retry and catch mechanisms, allowing the workflow to automatically fall back to alternate foundation models if a primary model invocation fails. This directly satisfies the fallback requirement without introducing excessive custom code.

The other options lack one or more critical capabilities. Lambda-only logic lacks deep observability and structured fallback handling, SQS introduces additional latency and limited workflow visibility, and multiple coordinated workflows increase architectural complexity without added benefit.

Option A is the correct solution because it uses native Amazon Bedrock governance and evaluation capabilities to meet regulatory, performance, and deployment timeline requirements with the least operational overhead.

Amazon Bedrock guardrails provide built-in safety controls that enforce responsible AI policies directly during inference. Custom content filters and toxicity detection protect customer interactions and prevent disallowed investment guidance patterns without requiring custom application logic. Guardrails operate inline and are optimized for low latency, which helps meet the strict 200 ms response-time requirement.

Hallucination detection is addressed through Amazon Bedrock Model Evaluation, which supports automated evaluation at scale using LLM-as-a-judge techniques. This enables the company to detect factual inaccuracies and policy violations systematically, without building custom evaluation pipelines or requiring extensive human review. Evaluation outputs can be surfaced as metrics.

Storing all prompt-response pairs in Amazon DynamoDB provides a low-latency, highly scalable audit store that aligns with financial regulatory requirements. Using TTL enforces data retention policies automatically, reducing compliance risk and storage overhead.

Amazon CloudWatch custom metrics integrate seamlessly with existing compliance dashboards, allowing near–real-time monitoring of safety interventions, hallucination rates, and drift indicators. CloudWatch anomaly detection can be applied to these metrics to surface behavior changes quickly.

Option B relies on custom Lambda logic and S3-based auditing, increasing latency and operational complexity. Option C introduces additional services that increase setup time and may exceed the 60-day deployment window. Option D uses non–Bedrock-native monitoring and adds unnecessary infrastructure layers.

Therefore, Option A provides the most complete, compliant, and low-overhead governance solution for a regulated GenAI financial services application.

Option C is the correct solution because it resolves throttling while preserving performance and avoiding fixed costs during low-traffic periods. Amazon Bedrock supports on-demand inference with usage-based pricing, making it well suited for applications with time-zone–dependent traffic spikes.

Throttling during peak hours typically occurs when inference requests exceed available regional capacity. Cross-Region inference allows Amazon Bedrock to automatically distribute requests across multiple AWS Regions, reducing contention and preventing throttling without requiring reserved or provisioned capacity. This approach ensures continuous operation while maintaining low latency for users in different geographic locations.

Invocation logging and native metrics such as InvocationThrottles, InputTokenCount, and OutputTokenCount provide visibility into usage patterns and capacity constraints. Monitoring these metrics enables teams to validate that traffic distribution is working as intended and that performance remains consistent during peak periods.

Option A introduces fixed hourly costs by relying on provisioned throughput, which directly violates the requirement to avoid unnecessary spend during low-traffic periods. Option B introduces regional failover complexity and reactive behavior instead of proactive load distribution. Option D does not address the root cause of throttling, as distributing traffic across model versions within the same Region does not increase available capacity.

Therefore, Option C best aligns with AWS Generative AI best practices for scalable, cost-efficient, global serverless applications.

Option B is the correct solution because legal research workloads require both semantic understanding and exact lexical precision, especially for statutes, citations, and domain-specific terminology. A hybrid search architecture directly addresses this need by combining vector similarity search with traditional keyword-based retrieval.

Vector search alone is often insufficient for legal research because exact phrases, citation formats, and jurisdiction-specific terms must be matched precisely. Keyword search ensures high recall and precision for citations and legal terms, while vector search captures deeper semantic relationships between legal concepts, precedents, and arguments. Amazon OpenSearch Service natively supports hybrid search, enabling efficient scoring and ranking without external orchestration.

Applying an Amazon Bedrock reranker model further improves relevance by reordering retrieved documents based on deeper contextual understanding. Reranking is especially valuable in legal research because multiple documents may appear relevant, but only a subset truly addresses the user’s legal question. The reranker optimizes final results before they are passed to the Anthropic Claude FM, improving answer accuracy and reducing hallucinations.

Option A relies on default vector search, which does not reliably handle citations and exact terminology. Option C focuses on query suggestions and post-processing rather than retrieval quality. Option D introduces unnecessary operational complexity by merging results across multiple systems.

Therefore, Option B best meets the requirements for precision, performance, and semantic understanding in a legal research AI assistant.

Option B matches the defining requirement: the company, rather than a managed agent harness, must own the orchestration loop . Amazon Bedrock AgentCore Runtime provides a serverless, purpose-built environment for hosting agents and tools while remaining framework agnostic. AWS explicitly supports agents created with frameworks such as LangGraph, Strands, and CrewAI as well as fully custom agents that use no agent framework.

AWS further distinguishes AgentCore Runtime from its managed harness by stating that with Runtime, the customer brings the agent code and “the orchestration loop is yours.” The custom application can therefore implement proprietary tool-selection logic, complex conversation-state transitions, specialized retry algorithms, proprietary telemetry, validation stages, and any other control-flow behavior required by the business. Runtime supplies infrastructure capabilities such as isolation, scaling, sessions, authentication, and observability plumbing rather than taking ownership of the decision loop.

Amazon Bedrock can separately provide managed foundation-model inference, allowing the company to use Bedrock FMs without deploying or operating model-serving infrastructure.

A is incorrect specifically because of its final statement. AgentCore Policy is an authorization mechanism, not an orchestration or retry engine. AWS documents that Policy evaluates Cedar or Dogwood policies to determine whether tool invocations are permitted or forbidden. It can govern which actions are authorized, but it does not implement an agent ' s tool-selection algorithm or failure-retry strategy.

C relinquishes precisely the orchestration control the company requires by depending on managed behavior. D could provide deterministic workflow coordination but places Step Functions outside the agent loop and is cumbersome for highly dynamic multi-turn agent reasoning, proprietary state transitions, and tool-selection decisions.

Therefore, B preserves complete application-level orchestration control while outsourcing scalable runtime infrastructure and foundation-model inference to AWS.

==========

Option C combines AWS-native capabilities for the three required monitoring dimensions with minimal custom code. Amazon Bedrock model invocation logging can capture request and response information and deliver invocation data to Amazon S3 or CloudWatch Logs. Bedrock Guardrails contextual grounding checks are specifically designed to detect and filter responses that are not sufficiently grounded in supplied source information; AWS explicitly lists summarization as a supported use case. CloudWatch provides token-usage observability, while anomaly-detection mechanisms can establish adaptive baselines instead of requiring manually maintained static thresholds. This enables earlier detection of unusual consumption and potential cost anomalies. Option A requires custom Athena-based hallucination analysis. Option B relies on evaluation jobs and custom Lambda processing rather than near-real-time managed controls. Option D combines services that do not directly provide the required Bedrock-specific hallucination monitoring. AWS Documentation

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

Option D is the correct solution because it directly satisfies all three core requirements: data source registration, metadata-based attribution, and end-to-end audit logging, while remaining service-agnostic and scalable across internal and external data sources.

The AWS Glue Data Catalog is the AWS-native service for registering datasets and managing metadata centrally. It supports structured registration of diverse data sources and enables consistent tagging that can be used to attribute generated content back to its original source. This is essential for GenAI applications that combine multiple datasets and must provide traceability for outputs.

Metadata tags applied within the Glue Data Catalog ensure a consistent attribution framework that downstream systems—such as Retrieval Augmented Generation (RAG) pipelines or evaluation systems—can reference without embedding attribution logic directly in application code. This improves maintainability and governance.

AWS CloudTrail provides immutable audit logs of API activity across AWS services, including data access, metadata changes, and pipeline interactions. CloudTrail logs are critical for compliance and regulatory review because they capture who accessed which data, when, and through which service. This satisfies the requirement to maintain audit logs “throughout the pipeline,” not just at storage or application layers.

Option A introduces Lake Formation, which is primarily intended for fine-grained data lake permissions and is not required solely for traceability. Option B relies on CloudWatch Logs, which does not provide authoritative audit logging across services. Option C limits audit scope to S3 access and does not register or govern all data sources comprehensively.

Therefore, Option D provides the most complete and least intrusive solution for traceable, auditable GenAI data pipelines.