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

Transfer learning is a machine learning technique that reuses knowledge learned from previous tasks to improve training efficiency and performance on new tasks. AWS documentation explains that transfer learning allows models to start from pretrained weights or representations, reducing training time and the amount of data required.

In this retail application scenario, the company wants to leverage information from prior tasks to increase learning speed, which is a defining characteristic of transfer learning. AWS emphasizes that transfer learning is especially effective when tasks are related, such as customer behavior analysis, product recommendations, or demand forecasting.

By initializing a model with learned features from an existing task, transfer learning enables faster convergence and improved accuracy compared to training from scratch. AWS frequently recommends this approach when computational efficiency and rapid iteration are important.

The other options do not satisfy the requirement. Supervised learning defines how labels are used but does not reuse prior knowledge. Hyperparameter tuning optimizes model configuration but does not leverage previous task outputs. Regularization techniques reduce overfitting but do not accelerate learning through knowledge reuse.

AWS documentation positions transfer learning as a foundational concept in modern ML workflows, particularly for retail, personalization, and natural language processing use cases. Therefore, transfer learning is the correct solution.

Directional stimulus prompting guides the foundation model to produce outputs aligned with business context. It’s particularly effective for aligning responses with public documents and improving coherence. From Bedrock Prompt Engineering Techniques documentation:

“Directional stimulus prompting provides structured prompts to steer the model output towards desired formats or behaviors using specific linguistic cues.”

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

Amazon SageMaker Ground Truth Plus provides a fully managed data labeling service where AWS manages the workforce, tools, and processes.

Data Wrangler is for data preparation and transformation.

Transcribe is for speech-to-text.

Macie is for sensitive data discovery, not labeling.

???? Reference:

AWS Documentation – SageMaker Ground Truth Plus

Experimenting and refining the prompt is the best approach to ensure that the chatbot using a foundation model (FM) produces responses that adhere to the company's tone.

Prompt Engineering:

Adjusting and refining the prompt allows for better control over the FM's outputs, ensuring they align with the desired tone and style.

This iterative process involves testing different prompts and modifying them based on the model's responses to achieve the desired outcome.

Why Option C is Correct:

Directly Influences Output Quality: Allows for fine-tuning of the model’s responses to match the company's tone.

Cost-Effective: Does not require modifying the model itself, only the inputs to it.

Why Other Options are Incorrect:

A. Low limit on tokens: Limits response length but not the adherence to company tone.

B. Batch inferencing: Relates to processing multiple inputs, not controlling response tone.

D. Higher temperature: Increases randomness in responses, which could deviate from the desired tone.

Amazon Textract (E) automatically extracts text and structured data from scanned documents, such as PDFs.

Amazon Bedrock (B) offers access to LLMs (such as Amazon Titan or Anthropic Claude) for tasks like summarization and generating embeddings for search.

Workflow:

Amazon Textract extracts text from PDFs in S3.

Amazon Bedrock LLMs summarize the extracted text.

(Optional: Summaries can be indexed using Amazon OpenSearch or another search solution.)

A (Translate) is for language translation, not extraction or summarization.

C (Transcribe) is for audio to text, not PDFs.

D (Polly) is for text-to-speech.

“Amazon Textract extracts text, forms, and tables from scanned documents... Bedrock provides generative AI models to perform summarization and other text generation tasks.”

(Reference: Amazon Textract, Amazon Bedrock, AWS GenAI RAG Reference)

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon Macie uses machine learning to:

Discover sensitive data such as PII

Classify data stored in Amazon S3

Help prevent unintended data exposure

AWS security guidance recommends Macie before data sharing to ensure compliance and privacy protection.

Why the other options are incorrect:

Kendra (A) is a search service.

Textract (C) extracts text from documents.

Data Exchange (D) shares datasets, not analyzes sensitivity.

AWS AI document references:

Amazon Macie Overview

Protecting Sensitive Data in S3

Data Privacy and Governance on AWS

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 correct answer is B – Enable model invocation logging in Amazon Bedrock. AWS Bedrock provides native functionality to log all model invocations, including input prompts, parameters, and generated outputs, to Amazon CloudWatch Logs or S3. According to AWS documentation, this feature helps developers monitor model usage, analyze errors, and audit for compliance. Unlike CloudTrail or Audit Manager, which record API events and compliance data respectively, invocation logging captures real inference transactions. EventBridge is used for event routing, not persistent log storage. Bedrock’s logging feature ensures complete traceability for debugging, usage analytics, and governance in accordance with Responsible AI principles.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Model Invocation Logging

AWS Responsible AI Documentation – Monitoring and Auditability

Amazon Bedrock offers an on-demand pricing model that provides flexibility without long-term commitments. This model allows companies to pay only for the resources they use, which is ideal for a limited budget and offers flexibility.

Option A (Correct): "On-Demand": This is the correct answer because on-demand pricing allows the company to use Amazon Bedrock without any long-term commitments and to manage costs according to their budget.

Option B: "Model customization" is a feature, not a pricing model.

Option C: "Provisioned Throughput" involves reserving capacity ahead of time, which might not offer the desired flexibility and could lead to higher costs if the capacity is not fully used.

Option D: "Spot Instance" is a pricing model for EC2 instances and does not apply to Amazon Bedrock.

AWS AI Practitioner References:

AWS Pricing Models for Flexibility: On-demand pricing is a key AWS model for services that require flexibility and no long-term commitment, ensuring cost-effectiveness for projects with variable usage patterns.