Pass the Amazon Web Services AWS Certified Professional AIP-C01 Questions and answers with CertsForce

Option D is the best fit because it implements a reliable event-driven MLOps workflow that automates retraining and redeployment with clear orchestration, auditability, and production-grade error handling. The requirement is explicit: whenever a new file is uploaded to Amazon S3, the system must retrain and then redeploy the model used by a web application. A common AWS pattern is to use an S3 event notification to trigger an AWS Lambda function, which then starts a controlled workflow. In option D, Lambda serves as the event handler that reacts immediately to the S3 upload event and passes the necessary context (bucket, object key, dataset version) into an AWS Step Functions Standard state machine.

Step Functions Standard is appropriate for model retraining pipelines because training and deployment steps can be long-running and benefit from durable state, retries, and failure handling. It provides execution history, making it easier to troubleshoot why a particular retraining run failed and to prove which dataset version produced which model version. This operational visibility is critical when the dataset is “growing rapidly” and retraining is frequent.

Within the workflow, Amazon SageMaker Pipelines is the right service to run the ML lifecycle stages in a repeatable way: data processing (if needed), training, evaluation/quality checks, model registration, and deployment to an endpoint used by the application. SageMaker Pipelines is purpose-built for CI/CD-style ML, supporting automated redeployments when a new approved model artifact is produced. By calling a pipeline execution from Step Functions, the company can add governance gates (for example, only deploy if evaluation metrics meet thresholds), and can apply consistent rollback and notification steps when deployment fails.

The other options are weaker: A confuses inference with retraining and does not provide deployment orchestration. B adds unnecessary webhook complexity and describes an awkward event bus configuration. C introduces Autopilot/Data Wrangler, which may be useful but adds extra moving parts and is not required to meet the trigger-and-redeploy requirement.

The correct combination is A, B, and D because these three options collectively satisfy the mandatory requirements for structured extraction, PII redaction before inference, regional human review, data residency, auditability, and high-scale availability with managed AWS services.

Option A is essential because Amazon Textract is the AWS-managed service designed to extract structured data from scanned documents such as forms, tables, and financial statements. Textract provides confidence scores, and Amazon Augmented AI (A2I) is purpose-built to route low-confidence extractions to human reviewers. Deploying Textract and A2I within the same Region ensures that the human review loop remains regionally constrained, meeting strict data residency requirements for applicants.

Option B satisfies the requirement to redact PII before inference by using AWS Lambda preprocessing. It also adds Amazon Bedrock guardrails to enforce safety controls on model outputs. Region-specific IAM roles ensure that only authorized principals in the correct Region can access the extracted data and invoke downstream services, strengthening residency enforcement and auditability.

Option D ensures that source documents are stored in Amazon S3 in the same Region as the applicant. Object metadata and tagging provide an auditable trail, supporting compliance reporting and traceability. S3 also provides the durability and availability needed to support 99.9% application availability as part of a well-architected pipeline.

Option C is not the correct approach for structured extraction from scans. Option E adds useful quality validation but is not strictly required to meet the stated requirements compared to A, B, and D. Option F is unrelated to the extraction/redaction/residency workflow requirements.

Therefore, A, B, and D are the best three choices to meet all stated requirements with minimal operational overhead.

Options A and E are correct because the failure pattern is caused by exceeding the model’s usable context window and by sending too much raw customer data directly to the FM. Amazon Bedrock Knowledge Bases follows the RAG pattern by splitting source content into manageable chunks, converting chunks into embeddings, storing them in a vector index, and using semantic similarity to retrieve relevant content for a user query. This supports option E because the application can index customer purchases, profiles, and review-related information, then retrieve only the most relevant records for the current recommendation request instead of stuffing all raw data into one prompt.

Option A is also correct because chunking and staged synthesis are standard ways to handle inputs that exceed an FM’s context capacity. Processing smaller segments avoids context-length-exceeded errors, and a final synthesis call can combine intermediate findings into a complete recommendation. This is especially useful when the company says it wants the system to consider all customer data, not merely truncate older or less important data. Amazon Bedrock Knowledge Bases also lets teams configure how content is chunked for storage and retrieval, which supports a structured approach rather than an oversized one-shot prompt.

Option B is not sufficient because truncating “less important” data conflicts with the requirement to consider all customer data. Option C violates the implied design direction because the company wants to use Knowledge Bases, and simply choosing a larger context model does not solve long-term growth of customer histories. Option D is technically incorrect: model parameters such as max_tokens control output generation limits, not the model’s maximum context window, and different Claude models have model-specific maximum values. You cannot use additionalModelRequestFields to bypass the FM’s context limit.

==========

Option B provides the strongest modular architecture for an integration-heavy agentic workload. Strands supports hierarchical agents-as-tools patterns in which a coordinating agent delegates specialized work to independent agents, allowing integrations and domain logic to be added or modified without creating one increasingly complex agent. AgentCore Gateway exposes tools through standardized MCP interfaces so agents can discover and invoke internal or external capabilities through a unified connectivity layer. AWS Step Functions supports callback tasks that pause execution until a human or external process returns a task token, making it suitable for the required human approval checkpoint. Option A requires custom model hosting and approval UI development. Option C is primarily a batch data-processing architecture rather than real-time agent orchestration. Option D can function initially, but a single agent becomes less modular and maintainable as the number of tools and business domains expands. Strands Agents

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

Option B provides the strongest match among the listed alternatives because it combines managed speaker identification, multimodal generative analysis, and a native search-oriented datastore without unnecessary custom orchestration.

Amazon Transcribe speaker diarization distinguishes speakers and assigns identifiers such as spk_0 , spk_1 , and so forth. Its output includes speaker labels and timestamps, allowing individual statements to be associated with particular speakers and positions in the meeting timeline.

Anthropic Claude models on Amazon Bedrock support multimodal prompts that combine text and images. The application can therefore supply speaker-attributed transcript segments together with extracted presentation/video frames and instruct the model to generate summaries that associate spoken comments with relevant visual information. AWS ' s Claude Messages API documentation explicitly supports mixed image-and-text input.

Amazon OpenSearch Service is appropriate for storing the enriched meeting records and supporting document indexing and full-text searching. It provides substantially more natural full-text retrieval than attempting to create a custom indexing layer over DynamoDB.

A uses Transcribe and Rekognition effectively, but it states that a Lambda function itself “generates” the summaries without specifying a generative model and requires custom correlation logic. C chains BDA, Transcribe, Rekognition, DynamoDB, and Bedrock, increasing service count and operational complexity; DynamoDB also does not natively satisfy the full-text-search requirement. D similarly depends on DynamoDB plus a custom indexing mechanism.

Current AWS capabilities make Bedrock Data Automation even more capable than the wording of C suggests: BDA can produce video summaries, scene-level summaries, detected video text, full audio transcripts, and speaker identification. However, among the supplied choices , B remains the cleanest architecture satisfying multimodal GenAI analysis, diarization, scalable managed processing, and native searchable storage.

==========

Option B is correct because Amazon Bedrock Knowledge Bases supports structured document metadata that can be stored separately from the text and used as filters during retrieval. Case type, jurisdiction, and case outcome are ideal filterable metadata attributes, while author and version fields preserve provenance for returned documents. AWS documentation confirms that S3 knowledge-base data sources can use sidecar metadata files and that metadata remains available for filtering even when it is excluded from the embedding. This gives the application precise semantic retrieval plus structured constraints without custom extraction at query time. Option A lacks structured filtering. Option C adds unnecessary Comprehend processing. Option D embeds metadata inside document text, which does not provide reliable field-level filtering and adds unnecessary agent-side extraction complexity. AWS Documentation

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

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 B is correct because the symptoms indicate context-window pressure rather than a compute-memory or Lambda-timeout problem. Large documents should be split into manageable chunks while preserving semantic continuity across boundaries. Amazon Bedrock Knowledge Bases supports chunking strategies, including semantic chunking and overlap-oriented approaches, so relevant context can be retained without sending an entire long report to the model at once. Monitoring InputTokenCount provides evidence of context utilization and helps identify when requests approach model limits. Diagnostic logging can then locate where truncation occurs. Option A increases timeouts but does not enlarge the model context window. Option C adds sequential orchestration that can jeopardize the 10-second target. Option D increases infrastructure resources, but host memory does not change a foundation model’s maximum context window and adds unnecessary cost. AWS Documentation

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

Option C is the correct solution because it enforces privacy controls at inference time, not at ingestion time, which is required when different user roles require different visibility into the same underlying data.

Using an S3 Lifecycle configuration ensures that documents older than 3 years are automatically removed, guaranteeing that the knowledge base references only compliant, recent medical reports. Scheduling Lambda-based syncs keeps the knowledge base aligned with the bucket contents without introducing complex per-upload orchestration.

The most important requirement is role-based PII exposure. Amazon Bedrock guardrails support dynamic application at inference time, allowing the system to select a guardrail configuration based on the authenticated user’s Amazon Cognito group. Surgeons can receive full responses, while engineers receive responses with PII masked—without duplicating data or maintaining multiple knowledge bases.

This approach preserves a single source of truth for medical reports while enforcing privacy through response-level controls. It also maintains full auditability of access and redaction behavior.

Option A permanently removes PII and violates surgeon access requirements. Option B redacts data inconsistently and couples privacy logic to ingestion. Option D doubles storage, increases cost, and introduces data drift risk.

Therefore, Option C best meets privacy, compliance, scalability, and operational efficiency requirements.

Option C best addresses both core problems: hallucinated recommendations that do not exist in the catalog and slow response times, while keeping operational overhead low. The most direct way to prevent the model from recommending unavailable products is to ground generation on authoritative product catalog data at inference time. An Amazon Bedrock knowledge base is designed for this pattern by ingesting domain data, chunking content, creating embeddings, and re trieving the most relevant catalog entries when a user asks for recommendations. Implementing Retrieval Augmented Generation ensures the foundation model receives only approved, catalog-backed context and can cite or base its output on those retrieved items. This sharply reduces the likelihood of inventing products, because the response is conditioned on retrieved catalog records rather than relying on the model’s parametric memory.

The requirement also notes that most interactions are unique. That makes response caching far less effective, because there are fewer repeated prompts to benefit from cached outputs. Instead, improving the retrieval and model invocation path is the better optimization. Using the PerformanceConfigLatency parameter set to optimized prioritizes lower latency behavior for model inference, helping meet faster recommendation generation without requiring the company to build and operate additional infrastructure.

The other options do not solve the root cause as reliably. Prompt engineering and streaming can improve perceived latency, but they do not guarantee catalog-only recommendations because the model can still hallucinate items. Guardrails can help detect or block certain undesired outputs, but without consistent catalog grounding they do not ensure every recommendation is derived from the company’s product data. Building a custom OpenSearch validation and caching layer increases operational complexity, and caching is misaligned with predominantly unique interactions.

Alright, after comparing List B (txt file) against List A (Word file) , I have identified the unique questions. These questions cover scenarios or architectural configurations that were not present in the existing list.

Here are the unique questions from List B, formatted as requested: