Pass the Amazon Web Services AWS Certified AI Practitioner AIF-C01 Questions and answers with CertsForce

Chain-of-thought prompting is a prompt engineering technique where you instruct the model to explain its reasoning step by step, which is particularly useful for tasks involving logic, math, or reasoning.

A is correct: Asking the model to " explain its reasoning step by step " directly invokes chain-of-thought prompting, as documented in AWS and generative AI literature.

B is unrelated (prompt injection is a security concern).

C (few-shot) provides examples, but doesn’t specifically require step-by-step reasoning.

D (templating) is about structuring the prompt format.

" Chain-of-thought prompting elicits step-by-step explanations from LLMs, which improves performance on complex reasoning tasks. "

(Reference: Amazon Bedrock Prompt Engineering Guide, AWS Certified AI Practitioner Study Guide)

The context window determines how much information can fit into a single prompt when using a large language model (LLM) like those on Amazon Bedrock.

Context Window:

The context window is the maximum amount of text (measured in tokens) that a language model can process in a single pass.

For LLM applications, the size of the context window limits how much input data, such as text for sentiment analysis, can be fed into the model at once.

Why Option B is Correct:

Determines Prompt Size: The context window size directly informs how much information (e.g., words or sentences) can fit in one prompt.

Model Capacity: The larger the context window, the more information the model can consider for generating outputs.

Why Other Options are Incorrect:

A. Temperature: Controls randomness in model outputs but does not affect the prompt size.

C. Batch size: Refers to the number of training samples processed in one iteration, not the amount of information in a prompt.

D. Model size: Refers to the number of parameters in the model, not the input size for a single prompt.

The requirement is to identify an AWS database service that supports the storage and querying of embeddings (from a generative AI model) as vectors. Embeddings are typically high-dimensional numerical representations of data (e.g., text, images) used in AI applications like conversational search. The database must support vector storage and efficient vector similarity searches. Let’s evaluate each option:

A. Amazon Athena: Amazon Athena is a serverless query service for analyzing data in Amazon S3 using SQL. It is designed for ad-hoc querying of structured data but does not natively support vector storage or vector similarity searches, making it unsuitable for this use case.

B. Amazon Aurora PostgreSQL: Amazon Aurora PostgreSQL is a fully managed relational database compatible with PostgreSQL. With the pgvector extension (available in PostgreSQL and supported by Aurora PostgreSQL), it can store and query vector embeddings efficiently. The pgvector extension enables vector similarity searches (e.g., using cosine similarity or Euclidean distance), which is critical for conversational search applications using embeddings from generative AI models.

C. Amazon Redshift: Amazon Redshift is a data warehousing service optimized for analytical queries on large datasets. While it supports machine learning features and can store numerical data, it does not have native support for vector embeddings or vector similarity searches as of May 17, 2025, making it less suitable for this use case.

D. Amazon EMR: Amazon EMR is a managed big data platform for processing large-scale data using frameworks like Apache Hadoop and Spark. It is not a database service and is not designed for storing or querying vector embeddings in the context of a conversational search application.

Exact Extract Reference: According to the AWS documentation, “Amazon Aurora PostgreSQL-Compatible Edition supports the pgvector extension, which enables efficient storage and similarity searches for vector embeddings. This makes it suitable for AI/ML workloads such as natural language processing and recommendation systems that rely on vector data.” (Source: AWS Aurora Documentation - Using pgvector with Aurora PostgreSQL, https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/PostgreSQLpgvector.html). Additionally, the pgvector extension supports operations like nearest-neighbor searches, which are essential for querying embeddings in a conversational search system.

Amazon Aurora PostgreSQL with the pgvector extension directly meets the requirement for storing and querying embeddings as vectors, making B the correct answer.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

This scenario describes prompt injection, which is a well-documented security and safety risk in generative AI systems.

Prompt injection occurs when a user intentionally crafts input prompts to override, manipulate, or bypass system instructions, guardrails, or safety policies defined by the AI application developer. The user’s instruction explicitly attempts to override prior system instructions and force the model into unrestricted behavior.

AWS Responsible AI and Generative AI security guidance describe prompt injection as:

An attempt to alter model behavior through malicious or manipulative user input

A risk that can lead to policy violations, unsafe outputs, or data misuse

A key concern when deploying large language models (LLMs) in production systems

Why the other options are incorrect:

Data bias (B) refers to skewed or unrepresentative training data, not user manipulation at inference time.

Hallucination (C) refers to the model generating incorrect or fabricated information.

Data exposure (D) involves leaking sensitive or private data, not instruction hijacking.

AWS AI document references (for exact extracts):

AWS Responsible AI Overview — section on Generative AI risks

Amazon Bedrock Security Best Practices — section on prompt injection and input validation

AWS Generative AI Governance Guidance — discussion of instruction hierarchy and guardrails

Amazon Comprehend is the correct service to analyze customer support interactions and identify frequently asked questions and insights.

Amazon Comprehend:

A natural language processing (NLP) service that uses machine learning to uncover insights and relationships in text.

Capable of extracting key phrases, detecting entities, analyzing sentiment, and identifying topics from text data, making it ideal for analyzing customer support interactions.

Why Option B is Correct:

Text Analysis Capabilities: Can process large volumes of text to identify common topics, phrases, and sentiment, providing valuable insights.

Suitable for Customer Support Analysis: Specifically designed to understand the content and meaning of text, which is key for identifying frequently asked questions.

Why Other Options are Incorrect:

A. Amazon Lex: Used for building conversational interfaces, not for text analysis.

C. Amazon Transcribe: Converts speech to text but does not perform text analysis.

D. Amazon Translate: Used for translating text between languages, not for analyzing content.

Clustering is an unsupervised machine learning technique used to group data points based on similarity without requiring labeled data. AWS documentation explains that clustering is commonly used for customer segmentation , where the goal is to discover natural groupings within a dataset.

In this scenario, the dataset is unlabeled and includes behavioral and demographic features. Clustering algorithms analyze patterns and distances between data points to identify distinct customer groups, making this technique ideal for understanding customer segments.

Regression and classification require labeled outputs, and reinforcement learning focuses on sequential decision-making, not grouping. AWS positions clustering as the correct approach for this use case.

The correct answer is C because Amazon Bedrock with On-Demand Throughput is designed for variable or unpredictable workloads. It allows you to pay only for what you use, which is ideal for early-stage or pilot-phase generative AI applications.

From AWS documentation:

" On-Demand Throughput in Amazon Bedrock provides flexibility and cost-efficiency for unpredictable or low-volume generative AI applications. You are charged based on the number of input/output tokens processed, with no need to provision dedicated capacity. "

Explanation of other options:

A. Using GPU-powered EC2 instances requires managing infrastructure and is generally more expensive, especially for inconsistent usage.

B. Provisioned Throughput is best suited for predictable, high-volume production workloads where guaranteed throughput is needed.

D. SageMaker JumpStart is for training and deploying ML models, not for efficient inference of foundation models.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Pricing and Throughput Models

AWS Generative AI Best Practices – Cost Optimization

AWS ML Specialty Guide – Bedrock Deployment Models

The business goal identification phase of the ML lifecycle involves defining the objectives of the project and understanding the requirements, including compliance and regulatory considerations. This phase ensures the ML solution aligns with legal and organizational standards before proceeding to technical stages like data collection or model training.

Exact Extract from AWS AI Documents:

From the AWS AI Practitioner Learning Path:

" The business goal identification phase involves defining the problem to be solved, identifying success metrics, and determining compliance and regulatory requirements to ensure the ML solution adheres to legal and organizational standards. "

(Source: AWS AI Practitioner Learning Path, Module on Machine Learning Lifecycle)

Detailed Explanation:

Option A: Feature engineeringFeature engineering involves creating or selecting features for model training, which occurs after compliance requirements are identified. It does not address regulatory concerns.

Option B: Model trainingModel training focuses on building the ML model using data, not on determining compliance or regulatory requirements.

Option C: Data collectionData collection involves gathering data for training, but compliance and regulatory requirements (e.g., data privacy laws) are defined earlier in the business goal identification phase.

Option D: Business goal identificationThis is the correct answer. This phase ensures that compliance and regulatory requirements are considered at the outset, shaping the entire ML project.

Amazon SageMaker Feature Store is the correct solution for sharing and managing variables (features) across multiple teams during model development.

Amazon SageMaker Feature Store:

A fully managed repository for storing, sharing, and managing machine learning features across different teams and models.

It enables collaboration and reuse of features, ensuring consistent data usage and reducing redundancy.

Why Option A is Correct:

Centralized Feature Management: Provides a central repository for managing features, making it easier to share them across teams.

Collaboration and Reusability: Improves efficiency by allowing teams to reuse existing features instead of creating them from scratch.

Why Other Options are Incorrect:

B. SageMaker Data Wrangler: Helps with data preparation and analysis but does not provide a centralized feature store.

C. SageMaker Clarify: Used for bias detection and explainability, not for managing variables across teams.

D. SageMaker Model Cards: Provide model documentation, not feature management.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Amazon SageMaker Model Monitor detects:

Data drift

Concept drift

Model quality degradation

AWS MLOps guidance recommends Model Monitor to:

Continuously evaluate production models

Trigger alerts when performance deviates from baselines

Maintain long-term model reliability

Why the other options are incorrect:

Amazon A2I (A) adds human review workflows.

Rekognition (C) is an image analysis service.

Trusted Advisor (D) provides cost and security recommendations.

AWS AI document references:

Amazon SageMaker Model Monitor Overview

Detecting Model Drift on AWS

Production ML Monitoring Best Practices