Free Amazon Web Services AIP-C01 Practice Exam with Questions & Answers | Set: 4

For a 3-week proof-of-concept in a regulated field like healthcare, Retrieval Augmented Generation (RAG) is more efficient and safer than fine-tuning. RAG allows the use of anonymized patient records without risking the leak of sensitive data into the model ' s permanent memory. To evaluate accuracy quantitatively and rapidly, the " LLM-as-a-judge " pattern is recommended. Using a strong judge model to score the outputs of multiple candidate FMs provides objective metrics (e.g., factual alignment, completeness) that manual qualitative feedback (Option C) cannot scale to provide within the timeline. Fine-tuning (Option B) typically takes longer than 3 weeks to properly data-prep and validate for clinical accuracy.

Option D is the correct solution because Amazon Q Developer customizations are designed to incorporate organization-approved knowledge and coding guidance without requiring per-project changes. A customization can point Amazon Q Developer to curated internal sources such as approved libraries, coding standards, architectural patterns, and proprietary techniques. This allows the assistant’s suggestions to align with company policies and preferred implementations consistently across teams and repositories.

The key requirement is that the company does not want to make project-level modifications. Options A, B, and C all require adding files or repositories into the project workspace, which directly violates this constraint. They also rely on developer behavior to “use workspace context,” which is harder to enforce and can lead to inconsistent adherence to standards.

With a customization, the organization centrally manages and updates approved resources. This reduces operational overhead because updates to libraries, patterns, or guidelines propagate automatically to developers using the customization, without requiring changes to each project. This is especially valuable for a new team, where consistent enforcement of approved practices is important to reduce compliance risk, security issues, and inconsistent code style.

Additionally, customizations support governance by allowing the company to standardize how Amazon Q Developer responds, ensuring that suggestions reflect approved internal content rather than generic public patterns.

Therefore, Option D best satisfies the requirement for centralized enforcement of approved resources with minimal ongoing management and no project-level modifications.

The first option labeled B is the correct solution because it fully satisfies both private connectivity and fine-grained cross-account data governance requirements using AWS-native services.

Creating interface VPC endpoints for Amazon Bedrock runtimes ensures that all inference calls remain on the AWS private network and never traverse the public internet. Running AWS Lambda functions in private subnets enforces network isolation, and using IAM conditions that restrict access to specific VPC endpoints and roles prevents unauthorized inference calls.

For the governed data lake, AWS Lake Formation LF-tag–based access control is the recommended AWS mechanism for enforcing cross-account, column-level permissions. LF-tags allow the company to define data access policies once and apply them consistently across accounts, databases, tables, and even individual columns. This is required for sensitive customer records and is not achievable with S3 bucket policies or IAM alone.

The second option labeled B uses a NAT gateway, which violates the private connectivity requirement. Option C uses public Bedrock endpoints and only database-level grants, which are insufficient. Option D relies on IAM path-based policies, which cannot enforce column-level access and introduces public fallback paths.

Therefore, the first option labeled B is the only solution that meets all networking, security, and data governance requirements.

The least operational overhead approach is to use managed Amazon Bedrock model evaluation workflows with datasets stored in Amazon S3 , and then publish results into Amazon CloudWatch for dashboards. That is exactly what options B and C combine.

Step B correctly places standardized evaluation inputs in Amazon S3 and focuses on granting the evaluation workflow the right permissions to read those datasets. In practice, the key requirement is controlled access to the S3 objects used as evaluation datasets. Establishing IAM permissions and private access patterns (such as using VPC connectivity patterns where applicable to the organization’s networking posture) is aligned with enterprise requirements and avoids building custom storage or data distribution systems for evaluators.

Step C then operationalizes the evaluation lifecycle with minimal infrastructure: a scheduled AWS Lambda function starts evaluation jobs using the S3 dataset location, and a second Lambda function checks job status and pushes results and operational signals to CloudWatch . This meets the platform requirement to surface accuracy metrics in dashboards because CloudWatch metrics/logs can be visualized in dashboards and queried through CloudWatch Logs Insights . It also supports continuous, standardized comparisons across models without requiring developers to run ad-hoc experiments.

The alternatives introduce more operational burden. D and E rely on Amazon SageMaker -based tooling, notebook jobs, and open source evaluation frameworks, which require more environment management, dependency control, scaling considerations, and maintenance over time. A includes CORS, which is primarily a browser-access concern and does not address how Bedrock-managed evaluation jobs securely access S3 in the typical service-to-service pattern.

Therefore, B + C achieves standardized model evaluation, automated scheduling, and dashboard-ready observability with the smallest operations footprint.

Option A is the correct answer because Amazon Bedrock Flows is purpose-built to orchestrate generative AI workflows that combine data access, deterministic transformations, and model invocation with minimal operational overhead. The requirements explicitly state that the workflow must retrieve content from Amazon S3, extract a specific portion of a predefined template, send that portion to an Amazon Bedrock model, and store the model’s response back into the same S3 bucket. Amazon Bedrock Flows natively supports all of these steps.

By configuring S3 action nodes at the beginning and end of the flow, the workflow can retrieve the original communications and persist the reviewed output without custom code. The expression step allows deterministic parsing of a specific portion of the template, which is essential when only part of the message should be reviewed. This avoids relying on generative logic for parsing, which would be less predictable and harder to audit. The agent step is then used specifically for the review task, where the foundation model evaluates or modifies the extracted content.

Option B uses AWS Step Functions, which can achieve similar outcomes but requires more explicit orchestration logic and does not provide GenAI-native constructs such as expressions and agent steps in a single managed experience. Options C and D rely on Amazon Bedrock agents and AWS Lambda functions to handle parsing and data movement, which increases complexity, operational overhead, and maintenance burden.

Because Amazon Bedrock Flows directly integrates S3 actions, parsing expressions, and model review steps in a single managed workflow, Option A best meets the requirements with the least development and operational effort.

Option A is the optimal solution because it provides scalable semantic search, rich metadata filtering, and tight integration with Amazon Bedrock while minimizing operational overhead. Amazon OpenSearch Serverless is designed for high-volume, low-latency search workloads and removes the need to manage clusters, capacity planning, or scaling policies.

With support for vector search and structured metadata filtering, OpenSearch Serverless enables efficient similarity search across 10 million embeddings while applying constraints such as language, publication date, regulatory agency, and document type. This is critical for financial services use cases where relevance and compliance depend on precise filtering.

Integrating OpenSearch Serverless with Amazon Bedrock Knowledge Bases enables a fully managed RAG workflow. The knowledge base handles embedding generation, retrieval, and context assembly, while Amazon Bedrock generates responses using a foundation model. This significantly reduces custom glue code and operational complexity.

Multilingual support is handled at the embedding and retrieval layer, allowing documents in English, Spanish, and Portuguese to be searched semantically without language-specific query logic. OpenSearch’s distributed architecture ensures consistent low-latency responses for real-time customer interactions.

Option B increases operational overhead by requiring database tuning and scaling for vector workloads. Option C does not support advanced metadata filtering, which is a key requirement. Option D introduces unnecessary complexity and is not optimized for large-scale semantic document retrieval.

Therefore, Option A best meets the requirements for performance, scalability, multilingual support, and minimal management effort in an Amazon Bedrock–based RAG application.

Option C best satisfies the requirement for flexible FM testing across environments while minimizing operational complexity and aligning with AWS-recommended deployment practices. Amazon Bedrock supports invoking on-demand foundation models through the FoundationModel abstraction, which allows applications to dynamically reference different models without requiring dedicated provisioned capacity. This is ideal for experimentation and A/B testing in both development and production environments.

Using a single AWS CDK application ensures infrastructure consistency and reduces duplication. Environment-specific configuration, such as selecting different foundation model IDs, can be externalized through parameters, context variables, or environment-specific configuration files. This allows product owners to easily switch between FMs in each environment without modifying application logic.

A single AWS CodePipeline with distinct deployment stages for development and production is an AWS best practice for multi-environment deployments. It enforces consistent build and deployment steps while still allowing environment-level customization. AWS CodeBuild deploy actions enable automated, repeatable deployments, reducing manual errors and improving governance.

Option A increases complexity by introducing multiple pipelines and relies on provisioned models, which are not necessary for FM evaluation and experimentation. Provisioned throughput is better suited for predictable, high-volume production workloads rather than frequent model switching.

Option B creates unnecessary operational overhead by duplicating CDK applications and pipelines, making long-term maintenance more difficult.

Option D directly conflicts with infrastructure-as-code best practices by manually recreating development resources, which increases configuration drift and reduces reliability.

Therefore, Option C provides the most flexible, scalable, and AWS-aligned solution for testing and switching foundation models across development and production environments.