AIF-C01 Exam Dumps - AWS Certified AI Practitioner Exam

To securely use large language models (LLMs) on Amazon Bedrock, companies should design clear and specific prompts to avoid unintended outputs and ensure proper configuration of AWS Identity and Access Management (IAM) roles and policies with the principle of least privilege. This approach limits access to sensitive resources and minimizes the potential impact of security incidents.

Option A (Correct): " Design clear and specific prompts. Configure AWS Identity and Access Management (IAM) roles and policies by using least privilege access " : This is the correct answer as it directly addresses both security practices in prompt design and access management.

Option B: " Enable AWS Audit Manager for automatic model evaluation jobs " is incorrect because Audit Manager is for compliance and auditing, not directly related to secure LLM usage.

Option C: " Enable Amazon Bedrock automatic model evaluation jobs " is incorrect because Bedrock does not provide automatic model evaluation jobs specifically for security purposes.

Option D: " Use Amazon CloudWatch Logs to make models explainable and to monitor for bias " is incorrect because CloudWatch Logs are used for monitoring and not directly for making models explainable or secure.

AWS AI Practitioner References:

Secure AI Practices on AWS: AWS recommends configuring IAM roles and using least privilege access to ensure secure usage of AI models.

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

Amazon Kendra is an enterprise search service that uses machine learning to index and search unstructured data such as documents, manuals, and course materials.

Amazon Comprehend performs NLP tasks like sentiment analysis and entity recognition, not enterprise search.

Amazon Textract extracts structured text from scanned docs and PDFs.

Amazon Personalize builds recommendation systems, not search engines.

📖 Reference:

AWS Documentation – Amazon Kendra

Network isolation is a key security feature for SageMaker. It ensures that training and inference jobs run in a VPC and are not accessible from the internet. Per the official SageMaker documentation:

“When you enable network isolation, your model can’t make any outbound network calls. This is useful for security and regulatory compliance when working with sensitive data.”

Step 1: Define the business objective.

Step 2: Process the data.

Step 3: Develop and train the model.

Step 4: Deploy the model.

The correct order represents the machine learning lifecycle as defined by AWS in the Amazon SageMaker documentation and AWS Certified Machine Learning Specialty Study Guide. The lifecycle describes the sequence of tasks required to build, train, and deploy a custom ML model effectively.

From AWS documentation:

" The machine learning process begins with defining the business problem, followed by collecting and processing data, developing and training models, and finally deploying them into production for inference. "

Step 1 – Define the business objective:

This step involves clearly identifying the business problem to be solved and determining the measurable outcomes expected from the ML model. This ensures alignment between business goals and ML outputs.

Step 2 – Process the data:

Data is collected, cleaned, transformed, and prepared for training. This includes handling missing values, normalizing data, and performing feature engineering — a crucial phase that influences model performance.

Step 3 – Develop and train the model:

The model is built and trained on the processed data using algorithms appropriate to the problem (e.g., regression, classification, clustering). Hyperparameters are tuned to optimize model accuracy.

Step 4 – Deploy the model:

Once validated, the model is deployed to a production environment (e.g., Amazon SageMaker endpoint) to make predictions on new data. Continuous monitoring and retraining ensure the model remains effective.

Referenced AWS AI/ML Documents and Study Guides:

Amazon SageMaker Developer Guide – Machine Learning Lifecycle

AWS Certified Machine Learning Specialty Study Guide – Model Development Lifecycle

AWS ML Best Practices Whitepaper – End-to-End ML Workflow

Comprehensive and Detailed Explanation (AWS AI documents):

According to AWS Generative AI and Foundation Model guidance, foundation models are pre-trained on very large and diverse datasets, enabling them to perform a wide range of tasks such as classification, summarization, labeling, and content generation without task-specific training.

For labeling online news articles, a foundation model can be used out of the box or with minimal prompt engineering, whereas a conventional ML model would typically require:

Task-specific labeled training data

Model training and validation cycles

Ongoing retraining as content evolves

Why the other options are incorrect:

B. Smaller and faster – Foundation models are generally larger, not smaller, than conventional ML models.

C. More transparent – FMs are often less transparent due to their size and complexity.

D. Not biased – Foundation models can still inherit biases from training data; bias mitigation is required.

AWS AI Study Guide References:

AWS Generative AI fundamentals

AWS Foundation Model characteristics and benefits

The verified answer is C. Amazon Inspector. The company needs automated vulnerability assessment for Amazon EC2-based infrastructure. AWS documentation states that Amazon Inspector scans EC2 instances for package vulnerabilities and network reachability issues and produces findings. It compares instance metadata against vulnerability intelligence and security advisory rules. This is exactly the service used to assess EC2 infrastructure before deploying sensitive workloads such as generative AI models.

AWS also documents that Amazon Inspector scans EC2 instances for common vulnerabilities and exposures, operating system package vulnerabilities, programming language package vulnerabilities, network exposure issues, and network reachability issues. This confirms that Inspector is the correct service for automated vulnerability assessment of EC2-based ML infrastructure.

AWS CloudFormation is incorrect because it provisions infrastructure as code. It can create EC2 instances, security groups, and related resources, but it does not perform vulnerability assessment. Amazon Comprehend is incorrect because it is a natural language processing service used to extract insights from text. It does not scan infrastructure. AWS Trusted Advisor is incorrect because it provides best-practice recommendations across categories such as cost optimization, security, performance, and service limits, but it is not the dedicated automated vulnerability assessment service for EC2 instances.

The requirement is specific: scan EC2-based ML infrastructure for vulnerabilities before deployment. The AWS-native service that performs this function is Amazon Inspector.

RAG combines large pre-trained models with retrieval mechanisms to fetch relevant context from a knowledge base. This approach is cost-effective as it eliminates the need for frequent model retraining while ensuring responses are contextually accurate and up to date. References: AWS RAG Techniques.