Free Practice Questions for Amazon Web Services AIF-C01 Exam

The correct answer is AWS Artifact, which is a central resource for accessing AWS compliance documentation, audit reports, and certifications from both AWS and third-party providers, including ISVs. According to AWS documentation, Artifact supports notifications for newly available reports. Customers can subscribe to notification emails when specific compliance documents or updates are published. This feature is ideal for regulated industries or companies needing third-party verification of compliance and security postures. Artifact provides access to reports such as SOC 2, ISO, PCI, and more, and is commonly used for audit preparation and vendor risk management. In contrast, AWS Audit Manager helps create internal audit frameworks but is not focused on third-party report distribution. AWS Data Exchange is for marketplace data sharing, and Trusted Advisor provides performance and cost optimization recommendations, not compliance document alerts. Thus, AWS Artifact is the purpose-built service that meets this requirement.

Referenced AWS AI/ML Documents and Study Guides:

AWS Artifact Documentation – Compliance Reports and Subscriptions

AWS Security and Compliance Whitepaper – Using Artifact for Third-Party Assurance

Comprehensive and Detailed Explanation (AWS AI documents):

AWS recommends using managed, purpose-built services to enforce safety, compliance, and responsible AI controls in generative AI applications in order to minimize operational complexity and maintenance effort.

Amazon Bedrock Guardrails are specifically designed to help customers:

Block or mask sensitive information, such as personally identifiable information (PII)

Detect and reduce hallucinations by enforcing grounding and response constraints

Apply content filters, topic restrictions, and safety policies consistently across generative AI applications

Configure safeguards without building or managing custom infrastructure

Because Guardrails are fully managed and integrated directly with Amazon Bedrock, they require minimal setup, no custom code for policy enforcement, and no infrastructure management, resulting in the least operational overhead.

Why the other options are less suitable:

A. AWS Lambda policy evaluator requires custom logic, testing, monitoring, and ongoing maintenance.

B. FM default policies alone are insufficient because they do not provide application-specific masking, hallucination detection, or configurable governance controls.

D. Custom EC2-based policy evaluators introduce the highest operational overhead due to server management, scaling, patching, and monitoring.

AWS AI Study Guide References:

Amazon Bedrock overview and safety features

Amazon Bedrock Guardrails for responsible generative AI

AWS best practices for building secure and governed generative AI applications

The verified answer is A. Continuous pre-training. The company wants to expose an existing LLM to medical papers so the model becomes more familiar with medical topics, terminology, and writing patterns. AWS generative AI documentation defines continued pre-training as extending the pre-training phase of a foundation model by exposing it to additional unlabeled text from specific domains or corpora. It also explains that continued pre-training helps the model acquire deeper knowledge of new domains and adapt to domain-specific terminology and content types.

That exactly matches the scenario. Medical papers are typically domain text. The goal is not to train the model to follow a labeled input-output task, but to improve its domain familiarity and medical-language fluency. AWS security reference guidance also distinguishes continued pre-training from fine-tuning by stating that continued pre-training uses unlabeled data to enhance domain knowledge, while fine-tuning uses labeled data to optimize task-specific performance.

Supervised learning is incorrect because it requires labeled training examples, usually input-output pairs. The question only says the company has medical papers, not labeled prompts and responses.

Reinforcement learning is incorrect because it optimizes behavior based on rewards, feedback, or preference signals. The question does not describe reward modeling or human preference feedback.

Boosting is incorrect because boosting is an ensemble technique that combines weak learners to improve predictive performance. It is not the standard method for adapting an LLM to a specialized knowledge domain.

Because the company wants to familiarize an LLM with medical subject matter through medical papers, the correct technique is continuous pre-training.

Comprehensive and Detailed Explanation (AWS AI documents):

AWS Responsible AI principles stress the importance of fairness, robustness, and accountability, which begin with the quality of the data used to train models. A responsible dataset should:

Be diverse, representing different populations, environments, and conditions to reduce bias

Be sourced from reputable and appropriate sources, ensuring data quality and ethical use

Have balanced categories, preventing the model from favoring one class over others and reducing the risk of discriminatory outcomes

These characteristics help ensure that the resulting image classification model behaves fairly, performs reliably across groups, and aligns with AWS Responsible AI best practices.

Why the other options are incorrect:

B focuses on dataset size rather than quality, balance, or representativeness.

C increases the risk of bias and poor generalization.

D limits diversity and does not inherently ensure fairness or accountability.

AWS AI Study Guide References:

AWS Responsible AI principles: fairness and data quality

AWS guidance on dataset selection and preparation for responsible ML

Amazon SageMaker Canvas is a visual, no-code tool for building and deploying ML models. According to the official SageMaker Canvas documentation:

“SageMaker Canvas provides a visual point-and-click interface that allows business analysts to generate accurate ML predictions without writing any code.”

The most cost-effective combination is to perform the managed foundation-model customization through Amazon Bedrock and secure connectivity by using Amazon VPC and AWS PrivateLink .

AWS documentation states that when a Bedrock model-customization job is submitted, Amazon Bedrock accesses the designated training and validation data to fine-tune the selected foundation model. The customization operation is available programmatically through the Amazon Bedrock API.

For network isolation, AWS states: “Using a VPC protects your data” and recommends creating an interface endpoint with AWS PrivateLink so the data does not need to be available over the public internet.

AWS PrivateLink establishes private connectivity between resources in the VPC and Amazon Bedrock without routing application traffic through the public internet. For model customization, AWS supports supplying a VPC configuration containing appropriate subnets and security groups to protect access to training data.

AWS also documents that Bedrock fine-tuning data is used only for the customization process and is not used to train the underlying base model for unrelated customers. Training and validation data provided for fine-tuning is not retained by Bedrock after the job completes.

Option A would introduce unnecessary on-premises infrastructure and hardware costs. Fine-tuning supported Bedrock foundation models does not require deploying the entire service through AWS Outposts.

Option D is invalid because customers do not host the managed Amazon Bedrock service API on premises.

Option E provides monitoring and observability, but CloudWatch logging does not establish private network connectivity or isolate model-customization data.

Thus, Amazon Bedrock supplies the managed fine-tuning capability while VPC connectivity and AWS PrivateLink provide the private network path. This combination minimizes infrastructure management while satisfying the stated security requirement.

Therefore, the correct answers are B and C .

===========

Amazon SageMaker JumpStart is the correct service for quickly deploying and consuming a foundation model (FM) within a team ' s VPC.

Amazon SageMaker JumpStart:

Provides access to a wide range of pre-trained models and solutions that can be easily deployed and consumed within a VPC.

Designed to simplify and accelerate the deployment of machine learning models, including foundation models.

Why Option B is Correct:

Rapid Deployment: JumpStart allows for quick deployment of models with minimal configuration, directly within a secure VPC environment.

Ease of Use: Provides a user-friendly interface to select and deploy models, reducing the time to value.

Why Other Options are Incorrect:

A. Amazon Personalize: Focuses on creating personalized recommendations, not deploying foundation models.

C. PartyRock: Not a recognized AWS service.

D. Amazon SageMaker endpoints: Endpoints are for deploying specific models, not a feature for quickly starting with pre-trained foundation models.

The correct answer is B, because AWS recommends that any generative AI initiative begin with use-case clarification, stakeholder alignment, and measurable business objectives. According to the AWS Generative AI Adoption Framework and the AWS Machine Learning Journey guidelines, successful AI projects start with defining specific business outcomes—such as revenue growth, reduced time-to-market, or improved campaign efficiency. Conducting stakeholder interviews ensures the organization identifies the highest-value marketing use cases, such as personalized campaigns or content generation, and sets KPIs to measure revenue impact within the target timeframe. AWS documentation emphasizes avoiding premature model training (option A), which is costly and unnecessary without validated requirements. Implementing a prebuilt assistant (option C) may help operations but does not guarantee alignment with the core revenue objective. Replicating competitor features (option D) may lack strategic alignment. Therefore, refining use cases and measurable goals is the foundational AWS-recommended approach for a targeted revenue-driven generative AI initiative.

Referenced AWS Documentation:

AWS Generative AI Adoption Framework

AWS ML Business Value and Use-Case Identification Guidelines

Class imbalance in a training dataset can cause ML models to favor overrepresented groups, leading to biased predictions. The AWS AI Practitioner guide and SageMaker Clarify documentation emphasize the need to identify and mitigate class imbalance to ensure fairness and unbiased model outcomes.

D is correct: By measuring class imbalance and adapting the training process (e.g., through oversampling, undersampling, or using class weights), organizations can improve fairness and reduce bias across demographic groups.

A (reducing data size) could worsen bias by removing potentially useful diverse data.

B (consistency with historical results) might reinforce existing biases.

C (separate models) is not scalable and can introduce other fairness issues.

“To reduce bias, examine class imbalance in your training data and use techniques to ensure all groups are fairly represented.”

(Reference: AWS SageMaker Clarify: Mitigating Bias, AWS Responsible AI)

Comprehensive and Detailed Explanation From Exact AWS AI documents:

The F1 score is a standard evaluation metric that represents the harmonic mean of precision and recall.

In AWS ML evaluation guidance:

Precision measures correctness of positive predictions

Recall measures coverage of actual positive cases

F1 score balances both metrics into a single performance indicator

This makes the F1 score particularly useful when evaluating classification performance of foundation models.

Why the other options are incorrect:

Speed (B) is a latency metric.

Cost (C) measures operational efficiency.

Energy efficiency (D) is unrelated to predictive accuracy.

AWS AI document references:

Model Evaluation Metrics on AWS

Classification Performance Measurement

Amazon SageMaker Evaluation Best Practices