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

The verified answer is C. To break text into smaller units for processing. AWS defines tokenization as the process of breaking input text into smaller units called tokens. These tokens can be words, subwords, or characters, and tokenization is used as a preprocessing step for natural language processing tasks. This exactly matches option C.

Tokenization is fundamental because machine learning and generative AI systems do not process raw human language in the same way humans read sentences. Text must first be split into units the model can represent, count, embed, and process mathematically. For example, a sentence might be split into words, subword pieces, punctuation, or characters depending on the tokenizer and model architecture. These tokens can then be converted into numerical representations for downstream tasks such as classification, summarization, question answering, translation, or text generation.

Option A is incorrect because encryption protects data confidentiality by transforming readable text into unreadable ciphertext. Tokenization in NLP is not encryption. The original purpose is linguistic and computational processing, not data protection.

Option B is incorrect because compression reduces file size. Tokenization may reduce text into units, but its purpose is not storage compression. It prepares text for analysis by NLP systems.

Option D is incorrect because translation is a downstream NLP task that converts text from one language to another. Tokenization may be used before translation, but it is not itself translation.

The wording “break text into smaller units” is the defining phrase. Therefore, the correct answer is C.

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Feature engineering focuses on:

Creating new features

Selecting the most relevant existing features

Improving model signal and accuracy

AWS ML best practices identify feature engineering as a key driver of predictive performance.

Why the other options are incorrect:

Visualization (A) helps understanding, not feature creation.

Hyperparameter tuning (B) optimizes models, not features.

Data collection (D) expands datasets but does not engineer features.

AWS AI document references:

Feature Engineering Best Practices

Improving Model Accuracy on AWS

ML Model Development Lifecycle

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.

Responsible use of AI refers to developing, deploying, and operating artificial intelligence systems according to principles that promote fairness, transparency, accountability, safety, and appropriate human oversight.

In this scenario, the company wants AI adoption to align with organizational objectives while minimizing discriminatory outcomes and supporting transparent decision-making.

These requirements directly correspond to responsible AI governance principles.

AWS emphasizes incorporating responsible AI considerations throughout the complete machine learning lifecycle, including initial design, data preparation, model training, evaluation, deployment, and ongoing monitoring.

Risk management focuses on identifying and mitigating potential threats. Data curation concerns collecting, cleaning, and maintaining datasets. Cloud financial management addresses the financial efficiency of cloud resources.

Although these activities may support AI governance, they do not fully represent the ethical and organizational responsibilities described in the question.

Therefore, responsible use of AI is the correct governance perspective.

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.

Comprehensive and Detailed Explanation From Exact Extract:

In a RAG (Retrieval Augmented Generation) architecture, there are steps that can be optimized using offline batch processing, particularly for operations that do not require real-time updates:

A. Generation of content embeddings:When new content is published, it can be processed in batches to generate embeddings (vector representations) offline. These embeddings are then used at query time for similarity search. As new documents come in daily, batch processing is ideal for generating embeddings for all new content together.

“Content/document embeddings are typically generated offline, as this operation can be computationally expensive and does not need to happen in real-time.”

(Reference: AWS GenAI RAG Blog, Amazon Bedrock RAG Pattern)

C. Creation of the search index:After generating the content embeddings, these are indexed in a vector database or search service. This indexing is also typically performed in batch as part of the offline pipeline.

“Building or updating the vector index is often performed as a batch operation, reflecting the latest state of the content repository.”

(Reference: AWS RAG Pattern Whitepaper)

B, D, and E are real-time steps. Embeddings for user queries (B), retrieval of relevant content (D), and response generation (E) must be processed in real-time to provide an interactive experience.

The verified answer is A. Configure Amazon Macie to detect sensitive information in the documents that are uploaded to Amazon S3. The data is stored in Amazon S3, and the company wants automated sensitive information detection with the least development effort. AWS documentation states that Amazon Macie can automate discovery, logging, and reporting of sensitive data in an Amazon S3 data estate. Macie can use automated sensitive data discovery or sensitive data discovery jobs, and it can analyze S3 objects using AWS-managed data identifiers, custom data identifiers, or both.

This fits the requirement better than a custom ML or regex-based approach because Macie is purpose-built for discovering sensitive data in S3. AWS states that managed data identifiers can detect many types of sensitive data, including personally identifiable information, financial information, and credentials. Macie also produces sensitive data findings and discovery results, which can be monitored and processed by other AWS services.

Option B is incorrect because deploying an LLM on SageMaker would require model selection, deployment, prompt design, testing, security controls, and possibly custom redaction logic. That is not the least development effort.

Option C is incorrect because manually developing regex patterns is brittle and maintenance-heavy. It also requires custom development and does not fully automate sensitive information detection across many data types.

Option D is incorrect because asking customers not to share sensitive data is not a technical control and cannot guarantee detection or alerting.

Because the documents are in Amazon S3 and sensitive data detection must be automated, Amazon Macie is the correct solution.

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.

The business objective to evaluate the effect of an LLM chatbot aimed at reducing the actions required by call center employees should be average call duration.

Average Call Duration:

This metric measures the time taken to handle a customer call or query. A successful LLM chatbot should reduce the call duration by efficiently providing answers, minimizing the need for human intervention.

By decreasing the average call duration, the company can improve call center efficiency, reduce costs, and enhance the user experience.

Why Option B is Correct:

Direct Impact: The objective aligns directly with the goal of reducing the number of actions call center employees must take.

Operational Efficiency: Reducing call duration is a clear indicator of the chatbot ' s effectiveness in assisting customers without human help.

Why Other Options are Incorrect:

A. Website engagement rate: Is unrelated to call center operations.

C. Corporate social responsibility: Does not relate to call center efficiency.

D. Regulatory compliance: Is important but does not measure the effectiveness of a chatbot in reducing employee actions.

Comprehensive and Detailed Explanation (AWS AI documents):

AWS generative AI documentation defines hallucinations as a condition in which a generative model produces outputs that appear fluent, confident, and plausible but are factually incorrect or not grounded in the training data or provided context.

Limited or insufficient training data increases the likelihood of hallucinations because the model lacks enough factual grounding to generate reliable responses. This behavior is a well-known challenge in large language models and foundation models.

Why the other options are incorrect:

Interpretability refers to understanding how a model arrives at its predictions.

Nondeterminism refers to variation in outputs across runs due to probabilistic sampling.

Accuracy is a general performance metric, not the specific phenomenon described.

AWS AI Study Guide References:

AWS generative AI challenges and limitations

AWS guidance on hallucinations in foundation models