Crush the AWS AIF-C01 AI Practitioner Exam Without the Fluff

Decreasing the number of tokens in the prompt reduces the cost associated with using an LLM model on Amazon Bedrock, as costs are often based on the number of tokens processed by the model.

Token Reduction Strategy:

By decreasing the number of tokens (words or characters) in each prompt, the company reduces the computational load and, therefore, the cost associated with invoking the model.

Since the model is performing well with few-shot prompting, reducing token usage without sacrificing performance can lower monthly costs.

Why Option B is Correct:

Cost Efficiency: Directly reduces the number of tokens processed, lowering costs without requiring additional adjustments.

Maintaining Performance: If the model is already performing well, a reduction in tokens should not significantly impact its performance.

Why Other Options are Incorrect:

A. Fine-tuning: Can be costly and time-consuming and is not needed if the current model is already performing well.

C. Increase the number of tokens: Would increase costs, not lower them.

D. Use Provisioned Throughput: Is unrelated to token costs and applies more to read/write capacity in databases.

The best solution is Amazon Bedrock Knowledge Bases, which allows for the seamless integration of structured and unstructured internal documents—such as PDFs, CSVs, and extracted image text—into a retrieval-augmented generation (RAG) pipeline. According to AWS documentation, Bedrock Knowledge Bases offer a no-code or low-code setup to link your enterprise data with foundation models for context-aware responses, without needing to fine-tune or retrain models. The system indexes documents in an Amazon S3 bucket, creates embeddings, and stores them in a vector store. At inference time, the model retrieves relevant context and incorporates it into its response. This approach provides dynamic and up-to-date responses while maintaining data privacy, with minimal operational overhead. Unlike fine-tuning or building a model from scratch in SageMaker, which requires considerable compute resources and model management, Bedrock Knowledge Bases are serverless and easy to configure. It is designed exactly for internal knowledge AI assistants.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Developer Guide – Knowledge Bases

AWS Generative AI Best Practices – RAG Patterns for Enterprise Search

To comply with multiple regulatory frameworks, the company must ensure data protection and threat detection. Data protection involves safeguarding sensitive customer information, while threat detection identifies and mitigates security threats to the application.

Option C (Correct): " Data protection " : This is correct because data protection is critical for compliance with privacy and security regulations.

Option B (Correct): " Threat detection " : This is correct because detecting and mitigating threats is essential to maintaining the security posture required for regulatory compliance.

Option A: " Auto scaling inference endpoints " is incorrect because auto-scaling does not directly relate to regulatory compliance.

Option D: " Cost optimization " is incorrect because it is focused on managing expenses, not compliance.

Option E: " Loosely coupled microservices " is incorrect because this architectural approach does not directly address compliance requirements.

AWS AI Practitioner References:

AWS Compliance Capabilities: AWS offers services and tools, such as data protection and threat detection, to help companies meet regulatory requirements for security and privacy.

In generative AI models, such as those built on Amazon Bedrock, inference costs are driven by the number of tokens processed. A token can be as short as one character or as long as one word, and the more tokens consumed during the inference process, the higher the cost.

Option A (Correct): " Number of tokens consumed " : This is the correct answer because the inference cost is directly related to the number of tokens processed by the model.

Option B: " Temperature value " is incorrect as it affects the randomness of the model ' s output but not the cost directly.

Option C: " Amount of data used to train the LLM " is incorrect because training data size affects training costs, not inference costs.

Option D: " Total training time " is incorrect because it relates to the cost of training the model, not the cost of inference.

AWS AI Practitioner References:

Understanding Inference Costs on AWS: AWS documentation highlights that inference costs for generative models are largely based on the number of tokens processed.

The correct answer is D because low latency and optimized inference speed are critical for real-time applications. For delivering real-time service quotes, the system must respond in milliseconds or a few seconds at most, making latency a primary concern when choosing the model.

From AWS Bedrock documentation:

" When selecting a foundation model for real-time applications, inference speed and latency are key evaluation metrics to ensure responsive user experiences. "

Explanation of other options:

A. Model size affects performance and cost but doesn ' t directly guarantee low latency.

B. Training data quality is important for accuracy, but it doesn’t address real-time performance requirements.

C. GPU availability matters in infrastructure planning, not in model selection for latency optimization.

Referenced AWS AI/ML Documents and Study Guides:

Amazon Bedrock Model Selection Guide – Real-time Use Case Considerations

AWS ML Specialty Guide – Foundation Model Performance Criteria

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.

Amazon SageMaker Model Cards are specifically designed to support transparency, responsible AI, and governance throughout the machine learning lifecycle. According to AWS AI documentation, Model Cards provide a structured way to document critical information about machine learning models, including intended use cases, business context, training data assumptions, evaluation metrics, ethical considerations, and known limitations or risks. This makes Model Cards the correct feature for the requirements described.

AWS emphasizes that Model Cards help organizations meet internal governance standards and external regulatory or compliance expectations by improving model interpretability and accountability. They allow AI practitioners to clearly explain why a model was built, how it was trained, what data it relies on, and what risks or biases may exist. This aligns directly with the need to document business problems, training considerations, and usage risks.

Other options do not fully address these needs. Amazon SageMaker Model Registry focuses on versioning, approval workflows, and deployment tracking of models, but it does not provide comprehensive documentation for transparency or ethical considerations. Amazon SageMaker Model Monitor is designed to detect data drift, bias drift, and performance degradation in production, not to document assumptions or governance details. Model Dashboard offers a centralized view of deployed models and endpoints but does not provide structured, narrative documentation of model intent or risks.

AWS positions Model Cards as a core component of Responsible AI, enabling organizations to promote fairness, explainability, and trust in machine learning systems. By capturing standardized, auditable documentation, Model Cards ensure that stakeholders—including developers, auditors, and business leaders—can understand how a recommendation system should be used and where caution is required.

The verified answer is B. Data leakage. The model exposes sensitive company information because that information was inadvertently included in training data. AWS guidance warns that using sensitive data to train models can cause unintended disclosure of data from model output, including data leakage during inference. This is exactly the scenario: sensitive information entered the training process and later appeared in model output after deployment.

AWS security reference guidance for generative AI model customization identifies sensitive information disclosure as a threat where a model trained on datasets containing PII leaks sensitive information during inference. Although the question says company information rather than PII specifically, the same security principle applies: protected data included in training or continued pre-training can be memorized or reproduced by the model later.

Jailbreaking is incorrect because jailbreaking refers to attempts to bypass model safety controls through adversarial prompts. The problem here is not that a user bypassed safety controls; the sensitive information was already embedded through training data.

Contextual grounding is incorrect because grounding is a technique for improving answer accuracy by connecting model responses to trusted context, such as RAG sources. It is not a security risk.

Prompt injection is incorrect because prompt injection involves malicious input that attempts to override or manipulate model behavior at inference time. The question does not describe a malicious prompt. It describes accidental exposure from training data.

Therefore, the correct security risk is data leakage.

Amazon Q Developer is a tool designed to assist developers in increasing productivity by generating code snippets, managing reference tracking, and handling open-source license tracking. These features help developers by automating parts of the software development process.

Option A (Correct): " Create software snippets, reference tracking, and open-source license tracking " : This is the correct answer because these are key features that help developers streamline and automate tasks, thus improving productivity.

Option B: " Run an application without provisioning or managing servers " is incorrect as it refers to AWS Lambda or AWS Fargate, not Amazon Q Developer.

Option C: " Enable voice commands for coding and providing natural language search " is incorrect because this is not a function of Amazon Q Developer.

Option D: " Convert audio files to text documents by using ML models " is incorrect as this refers to Amazon Transcribe, not Amazon Q Developer.

AWS AI Practitioner References:

Amazon Q Developer Features: AWS documentation outlines how Amazon Q Developer supports developers by offering features that reduce manual effort and improve efficiency.

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.