Free Amazon Web Services AIF-C01 Practice Exam with Questions & Answers | Set: 3

AWS documentation identifies hallucinations as a known limitation of generative AI models, particularly when used in business and production environments. Hallucinations occur when a model generates outputs that are unrelated, incorrect, fabricated, or unsupported by the input data or provided context. These outputs often appear confident and fluent, which can make them difficult to detect without additional validation.

Generative AI models, including large language models, operate using probabilistic token prediction based on patterns learned during training. AWS explains that these models do not have true reasoning or factual grounding unless explicitly provided with context or external knowledge. As a result, when prompts are ambiguous, incomplete, or outside the model’s training distribution, the model may produce responses that are irrelevant or misleading.

This behavior presents a risk for business use cases such as customer support, reporting, or decision-making systems. AWS highlights hallucinations as a key challenge that must be mitigated through techniques such as Retrieval Augmented Generation (RAG), prompt engineering, human review, and output validation.

The other options are not correct. Interpretability refers to the ability to understand model decisions, not incorrect outputs. Data bias relates to skewed or unfair training data. Nondeterminism refers to variability in outputs, not relevance or correctness.

AWS consistently categorizes hallucinations as a primary disadvantage of generative AI, making this the correct answer.

The best solution is Amazon Bedrock Knowledge Bases, which allows for the seamless integration of structured and unstructured internal documents—such as PDFs, CSVs, and extracted image text—into a retrieval-augmented generation (RAG) pipeline. According to AWS documentation, Bedrock Knowledge Bases offer a no-code or low-code setup to link your enterprise data with foundation models for context-aware responses, without needing to fine-tune or retrain models. The system indexes documents in an Amazon S3 bucket, creates embeddings, and stores them in a vector store. At inference time, the model retrieves relevant context and incorporates it into its response. This approach provides dynamic and up-to-date responses while maintaining data privacy, with minimal operational overhead. Unlike fine-tuning or building a model from scratch in SageMaker, which requires considerable compute resources and model management, Bedrock Knowledge Bases are serverless and easy to configure. It is designed exactly for internal knowledge AI assistants.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Knowledge Bases

AWS Generative AI Best Practices – RAG Patterns for Enterprise Search

The verified answer is A. Amazon Bedrock Guardrails. The requirement is to prevent a deployed foundation model from returning answers about a specific unwanted topic: politics. AWS documentation states that Amazon Bedrock Guardrails provides configurable safeguards to help you build safe generative AI applications. It also explains that guardrails provide safety and privacy controls across foundation models and help detect and filter undesirable content in user inputs and model responses. Most importantly for this question, AWS specifically identifies denied topics as a guardrail capability. With denied topics, you can define a set of topics that are undesirable in the context of your application, and the filter helps block them if they are detected in user queries or model responses. That exactly matches the scenario because the company wants political questions blocked before answers are sent to users.

Amazon Bedrock Agents is incorrect because agents are used to build applications that can reason, orchestrate tasks, call APIs, and connect to knowledge sources or action groups. Agents do not primarily exist to block topic categories in model input or output. Amazon SageMaker Clarify is incorrect because AWS describes SageMaker Clarify as a service for fairness, model explainability, feature attribution, and bias detection. It is useful for understanding model behavior and detecting bias, but it is not the correct control for filtering political responses from a generative AI application.

Amazon SageMaker Model Monitor is also incorrect because it monitors deployed model quality, data quality, bias drift, and feature attribution drift. Monitoring can identify problems after deployment, but it does not directly enforce real-time content filtering for foundation model responses. The question asks for a solution that ensures political answers are not sent to users. AWS Bedrock Guardrails is purpose-built for that control by applying safeguards to FM inputs and outputs.

The most direct business KPI for sales performance is conversion rate (percentage of users who purchase after AI assistant interaction).

Number of interactions (B) shows engagement, not sales impact.

Sentiment analysis (C) shows customer satisfaction but not revenue impact.

NLU accuracy (D) is a technical metric, not a business outcome.

???? Reference:

AWS Generative AI Use Cases – Measuring Business Value

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon SageMaker Model Cards provide a structured way to document:

Approved training datasets

Intended use cases

Ethical considerations and limitations

Compliance with internal policies and governance standards

Model Cards are a Responsible AI governance tool, enabling transparency and accountability throughout the model lifecycle.

Why the other options are incorrect:

Catalog (A) organizes ML assets but does not enforce ethical or policy documentation.

Clarify (B) detects bias and explainability issues but does not govern approved data usage.

Model Registry (C) manages model versions and approvals but does not document ethical intent.

AWS AI document references:

Amazon SageMaker Model Cards Documentation

AWS Responsible AI Practices

AI Governance on AWS

The verified answer is D. Amazon Nova Premier. The decisive requirement is the combination of a 1 million-token context window, multimodal document understanding, chart analysis, and video input. AWS documentation identifies Amazon Nova Premier as the most capable multimodal Amazon Nova understanding model. It supports text, image, and video inputs and generates text output. AWS also lists Amazon Nova Premier with a 1M context window, while Amazon Nova Pro and Amazon Nova Lite support 300k, and Amazon Nova Micro supports 128k and is text-only. Because the company’s legal documents are up to 1 million tokens long, Nova Premier is the only listed option that satisfies the context-length requirement.

AWS documentation also states that Amazon Nova Premier has a supported context length of 1 million tokens, which AWS equates to 1 million tokens of text, 500 images, or 90 minutes of video. The same documentation explains that Nova Premier excels at question answering on long documents. This directly matches the research company’s need to analyze very long legal documents and ingest video summaries for compliance reporting.

Amazon Nova Micro is incorrect because it is a text-only model and has a smaller context window. It cannot process embedded high-resolution charts or video inputs. Amazon Nova Lite is incorrect because it is multimodal, but its context window is 300k, which is below the 1 million-token requirement. Amazon Nova Pro is also incorrect for the same reason: it is highly capable and multimodal, but its context window is 300k rather than 1M. The requirement is not simply “multimodal”; it is long-context multimodal analysis at the 1 million-token scale. Therefore, the only model that fully meets the requirements is Amazon Nova Premier.

The verified answer is C. Use batch inference with Amazon Bedrock. The workload has three decisive characteristics: it is repetitive, it processes a large volume of requests, and it does not require immediate responses. AWS documentation states that with Amazon Bedrock batch inference, users can submit multiple prompts and generate responses asynchronously. It also states that batch inference helps process a large number of requests efficiently by sending a single request and generating responses in an Amazon S3 bucket. That directly matches the weekly generation of exercise routines for all users.

AWS also explains that after the batch job is complete, the output files can be retrieved from Amazon S3, and batch inference can improve model inference performance on large datasets. This is the right architecture for offline or scheduled workloads where immediate response latency is not required.

Amazon Bedrock AgentCore is incorrect because AgentCore is for building, running, and managing agents, tools, memory, gateways, and agent workflows. The problem is not agent orchestration; it is cost-efficient high-volume offline inference.

Real-time inference with Amazon Bedrock on-demand endpoints is incorrect because real-time inference is better for interactive applications where users need immediate responses. The question explicitly says immediate responses are not required.

Real-time inference with SageMaker AI hosted endpoints is also incorrect for the same reason. Hosted endpoints are appropriate for low-latency inference requests, but this workload is scheduled and large-volume.

Therefore, Amazon Bedrock batch inference is the best solution.

Amazon Q Developer is an AI-powered coding assistant integrated into IDEs (e.g., VS Code, JetBrains). It can:

Generate unit tests.

Create documentation.

Suggest code completions.

This is the fastest and most effective solution for this scenario.

???? Reference:

Amazon Q Developer – AWS Documentation

The verified answer is C. Add unified governance, discovery, and collaboration capabilities to Amazon SageMaker AI. The question is not asking only for storage, monitoring, or a basic repository. It asks for a scalable way for employees to find, access, and properly use company data while remaining compliant with policies and standards. AWS documentation for the next generation of Amazon SageMaker states that it simplifies discovery, governance, and collaboration for data and AI. Amazon SageMaker Catalog helps users securely discover and access approved data and assets through semantic search and governance workflows.

This directly matches the company’s requirement. In a rapidly growing multinational organization, data becomes harder to locate, understand, govern, and reuse. Unified governance and catalog capabilities allow teams to publish, discover, request access to, and collaborate on approved assets. AWS also describes Amazon SageMaker Catalog as a way to discover, govern, and collaborate on structured data, unstructured data, AI models, BI dashboards, and applications from a single catalog.

Option A is incorrect because a repository without integration does not solve governance, collaboration, or policy-based access. Option B is incomplete because storage alone does not help employees find or properly use data. Option D is also incomplete because monitoring can detect issues, but it does not provide data discovery, governance workflows, or collaboration features.

The correct solution must combine discovery, access governance, metadata, collaboration, and policy-aligned usage. Therefore, option C is the correct answer.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

The correct technique is fine-tuning, which is explicitly supported by Amazon Bedrock for customizing foundation models using high-quality labeled datasets.

Fine-tuning involves:

Starting with a pre-trained foundation model

Training it further using domain-specific, labeled data

Improving accuracy for specialized tasks, such as product classification, image-based understanding, and specification extraction

In this use case:

The company has labeled data

They want to customize model behavior

They require high accuracy and domain adaptation

These conditions match the definition of fine-tuning, not prompt-only methods.

Why the other options are incorrect:

A. Continued pre-training typically requires massive unlabeled datasets and is not the standard customization method exposed in Amazon Bedrock.

B. Creating an agent orchestrates model interactions and tools but does not customize the model’s learned parameters.

D. Prompt engineering improves responses through prompt design but does not modify the underlying model weights, making it insufficient for deep domain adaptation.

AWS AI document references (for exact extracts):

Amazon Bedrock Documentation — section on Model customization and fine-tuning

AWS Generative AI Study Guide — comparison of prompt engineering vs fine-tuning

Foundation Models on AWS — explanation of fine-tuning with labeled datasets