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

Measuring the model ' s accuracy against a predefined benchmark dataset is the correct strategy to evaluate the accuracy of a foundation model (FM) used in image classification tasks.

Model Accuracy Evaluation:

In image classification, the accuracy of a model is typically evaluated by comparing the predicted labels with the true labels in a benchmark dataset that is representative of the real-world data the model will encounter.

This approach provides a quantifiable measure of how well the model performs on known data and is a standard practice in machine learning.

Why Option B is Correct:

Benchmarking Accuracy: Using a predefined dataset allows for consistent and reliable evaluation of model performance.

Standard Practice: It is a widely accepted method for assessing the effectiveness of image classification models.

Why Other Options are Incorrect:

A. Total cost of resources: Does not measure model accuracy but rather the cost of operation.

C. Number of layers in the neural network: Does not directly correlate with the accuracy or performance of the model.

D. Color accuracy of images processed by the model: Is unrelated to the model’s classification accuracy.

Implementing data lifecycle management that tracks and manages AI training data is the only option that directly addresses governance, traceability, compliance, and audit requirements throughout an AI/ML lifecycle.

AWS treats governance as a responsible AI dimension involving the incorporation of appropriate practices throughout the AI supply chain, including providers and deployers. AWS also emphasizes appropriate collection, use, management, security, and traceability of data.

A practical AWS example is Amazon SageMaker AI Lineage Tracking. AWS states that SageMaker ML Lineage Tracking “creates and stores information about the steps of a machine learning (ML) workflow from data preparation to model deployment.” It enables organizations to track model and dataset lineage and establish governance and audit standards.

For a regulated loan-approval system, an organization should be capable of determining what training data was used, where it originated, how it was processed, which training job consumed it, which model artifact was generated, and how the resulting model progressed toward deployment. AWS lineage entities can associate training datasets with training jobs and subsequent model artifacts, supporting compliance verification and reproducibility.

Option A undermines governance because changing outputs without auditable records reduces accountability and traceability.

Option C is incorrect because performance optimization cannot supersede mandatory regulatory requirements such as approved data residency, retention, and processing controls.

Option D is also incorrect. Synthetic data can sometimes reduce exposure of real personal information, but using synthetic data does not automatically satisfy AI governance requirements. Organizations still need lifecycle controls, documentation, provenance, validation, security, auditing, and regulatory compliance.

Data governance should cover acquisition, storage, processing, access, lineage, retention, deletion, and permitted uses of data throughout the ML lifecycle.

Therefore, the governance-aligned solution is B. Implement data lifecycle management to track and manage AI training data.

===========

Amazon SageMaker Ground Truth lets you create data labeling jobs and can integrate with Amazon Mechanical Turk (a distributed human workforce) to label large unlabeled datasets.

A (batch inference) applies models to already-trained data, not labeling.

B (PyTorch Distributed) is for distributed training, not labeling.

D (OCR) applies only to text extraction from images, not transactions.

E is incorrect; Ground Truth is the service for labeling, not " AI labeling job. "

???? Reference:

AWS Documentation – SageMaker Ground Truth

Comprehensive and Detailed Explanation From Exact AWS AI documents:

AWS CloudTrail records API calls and user activity across AWS services, including:

Who performed an action

What action was taken

When and from where the action occurred

AWS governance guidance identifies CloudTrail as the primary service for audit logging and accountability.

Why the other options are incorrect:

AWS Config (B) tracks configuration changes, not user actions.

Audit Manager (C) assesses compliance but does not record individual actions.

Trusted Advisor (D) provides best-practice recommendations.

AWS AI document references:

AWS CloudTrail Overview

Auditing User Activity on AWS

Governance and Compliance for AI Workloads

The correct answer is Amazon Bedrock PartyRock, a playground for building and experimenting with generative AI apps in a low-cost, no-code environment. PartyRock is designed for innovation and learning. It enables users to try out prompts, LLM apps, and templates using Amazon Bedrock under a free-tier friendly setup. According to AWS, PartyRock abstracts infrastructure and allows rapid prototyping using models from Bedrock providers. This makes it ideal for early experimentation, especially for non-developers or those not ready to invest in full production pipelines. In contrast, Amazon Q Developer is for software engineering tasks, SageMaker JumpStart focuses on deploying ML models, and Q Business targets enterprise knowledge workers. None of those are as cost-effective and experimental-focused as PartyRock.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Documentation – PartyRock Overview

AWS Generative AI Learning Path – Getting Started Tools

The correct answer is A – Explainability. According to AWS Responsible AI documentation, explainability refers to an AI system’s ability to clearly communicate why it produced a given result. In healthcare, clinical decision support systems must provide traceable, understandable reasoning, especially when generating treatment recommendations. AWS highlights explainability as critical for high-impact domains such as medicine because doctors and patients must trust and understand the basis for AI-driven decisions. Tools like Amazon SageMaker Clarify support feature attribution, helping clinicians understand which patient factors (e.g., age, symptoms, lab values) influenced a recommendation. Privacy and security (B) protect data but do not provide rationale. Fairness (C) ensures equitable treatment across demographics but does not explain decisions. Data governance (D) focuses on handling and controlling data, not model decision transparency. Explainability is the AWS principle that ensures clinical users can interpret, validate, and rely on AI-generated recommendations for patient care.

Referenced AWS Documentation:

AWS Responsible AI Whitepaper – Explainability

Amazon SageMaker Clarify – Feature Attribution and Model Insights

Amazon Bedrock Knowledge Bases with Retrieval Augmented Generation (RAG) is the appropriate architecture because it separates frequently changing enterprise information from the foundation model ' s learned parameters. Instead of retraining or fine-tuning the FM every time documentation changes, the application retrieves relevant information from the current knowledge source at query time and supplies that information as context to the model.

AWS specifically states that adding a knowledge base improves cost-effectiveness by “removing the need to continually train your model to be able to use your private data.” This directly satisfies the requirement to avoid recurring model-training costs.

With Amazon Bedrock Knowledge Bases, the organization connects supported data sources, ingests and indexes the documents, and retrieves relevant chunks when a user asks a question. RAG then combines that retrieved content with the user ' s query so that the FM can generate an answer grounded in company information. AWS describes RAG as using information from data sources to improve the relevance and accuracy of generated responses.

When source documents change, the knowledge base can be synchronized or re-ingested so the retrieval layer reflects the updated content. This is substantially more appropriate than fine-tuning the model after every documentation change.

Option B would unnecessarily introduce repeated customization jobs, cost, operational overhead, and model-version management. Option C would become stale because static examples would continue referencing earlier documentation. Option D is especially unsuitable because cached answers can become outdated and would not verify them against newly updated source material.

RAG is specifically designed for scenarios where models require access to current, proprietary, or rapidly changing information without embedding that knowledge permanently into model weights.

Therefore, A. Amazon Bedrock Knowledge Bases with RAG is the correct solution.

===========

The correct answer is A – Create an AI agent. Amazon Bedrock Agents provide autonomous orchestration abilities that allow an AI system to interpret user queries, convert them into structured API calls, retrieve data, generate formatted outputs (like CSVs), and interact with external systems such as Amazon S3. According to AWS documentation, Bedrock Agents combine LLM reasoning with tool use, meaning they execute multi-step workflows such as querying OpenSearch, processing results, generating files, and uploading to storage—all without custom coding. The agent defines actions, APIs, and data transformation steps, making it ideal for automated enterprise workflows. Few-shot prompting (B) only influences text generation and cannot perform external actions like uploading to S3. A hand-coded software application (C) is possible but contradicts the goal of using AI for orchestration and requires more operational effort. A decision tree (D) cannot execute API workflows. Bedrock Agents are explicitly designed to perform multi-step tasks like this.

Referenced AWS Documentation:

Amazon Bedrock Agents – Tool Use and Workflow Automation

AWS Generative AI Best Practices – Agent-Based Architectures

Comprehensive and Detailed Explanation (AWS AI documents):

Overfitting occurs when an ML model learns patterns too closely from training data, including noise, and fails to generalize to unseen data. According to AWS ML fundamentals, a key indicator of overfitting is high training accuracy combined with reduced accuracy on new or test data.

Option A directly reflects this behavior: the model performs well during training but loses accuracy when evaluated on new data, which is a textbook symptom of overfitting.

Why the other options are not overfitting:

B describes an under-featured model (underfitting risk).

C indicates poor data representativeness, not overfitting.

D reflects limited feature selection, which may lead to underfitting or bias, not overfitting.

AWS AI Study Guide References:

AWS Machine Learning concepts: bias vs. variance

AWS training and evaluation best practices