Amazon Web Services Updated AIF-C01 Exam Questions and Answers by abiha

The correct answer is C because Amazon Bedrock ' s model evaluation feature allows users to compare outputs from different foundation models using human evaluation or automatic metrics. It enables the creation of structured evaluations where human reviewers (in this case, scientists) can assess model responses based on custom criteria like relevance, coherence, or accuracy.

From AWS documentation:

" Amazon Bedrock provides model evaluation capabilities that support both automatic and human evaluation. You can define custom evaluation prompts and collect assessments from reviewers to compare foundation model outputs for tasks such as summarization, text generation, and more. "

This solution is ideal for research workflows requiring domain experts to provide feedback on LLM-generated content.

Explanation of other options:

A. Amazon Personalize is used for building recommendation systems, not for evaluating model output.

B. Amazon Rekognition is used for analyzing images and videos (e.g., moderation, facial recognition), not textual output.

D. Amazon Comprehend provides NLP services like sentiment analysis, but sentiment is not sufficient for full quality evaluation of research paper generation.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Model Evaluation Overview

AWS Generative AI Best Practices

AWS ML Specialty Study Guide – Evaluation and Feedback Loops in LLMs

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.

The correct answer is B – Data preprocessing, which involves cleaning, filtering, and transforming raw data before model training. AWS defines preprocessing as the step where irrelevant or poor-quality data (e.g., excessively short or misrecorded audio) is removed or normalized. The described task— filtering recordings by duration and language—is a textbook example of preprocessing since it prepares the dataset for downstream feature extraction. Feature engineering would occur afterward when converting audio signals into numerical representations (like Mel-frequency coefficients). Model training and data collection come after and before preprocessing respectively. Proper preprocessing ensures data consistency, reduces noise, and improves model accuracy, especially in audio-based healthcare models where clarity and consistency are critical.

Referenced AWS AI/ML Documents and Study Guides:

AWS Machine Learning Specialty Guide – Data Preprocessing and Cleaning

Amazon SageMaker Data Wrangler Documentation – Data Preparation Best Practices

Creating effective prompts is the best solution to ensure that the content generated by a pre-trained generative AI model aligns with the company ' s brand voice and messaging requirements.

Effective Prompt Engineering:

Involves crafting prompts that clearly outline the desired tone, style, and content guidelines for the model.

By providing explicit instructions in the prompts, the company can guide the AI to generate content that matches the brand’s voice and messaging.

Why Option C is Correct:

Guides Model Output: Ensures the generated content adheres to specific brand guidelines by shaping the model ' s response through the prompt.

Flexible and Cost-effective: Does not require retraining or modifying the model, which is more resource-efficient.

Why Other Options are Incorrect:

A. Optimize the model ' s architecture and hyperparameters: Improves model performance but does not specifically address alignment with brand voice.

B. Increase model complexity: Adding more layers may not directly help with content alignment.

D. Pre-training a new model: Is a costly and time-consuming process that is unnecessary if the goal is content alignment.