The verified answer is A. AWS PrivateLink. The requirement is that API calls between generative AI applications and foundation models must not travel across the public internet. AWS documentation states that AWS PrivateLink can create a private connection between a VPC and Amazon Bedrock. With this configuration, applications can access Amazon Bedrock as if it were inside the VPC, without requiring an internet gateway, NAT device, VPN connection, or Direct Connect connection. AWS also states that instances in the VPC do not need public IP addresses to access Amazon Bedrock. This exactly satisfies the requirement for private API communication to foundation models.

Amazon Q is incorrect because Amazon Q is a generative AI assistant service for business, developer, and data use cases. It is not the network service used to privately route API calls between applications and FMs.

Amazon CloudFront is incorrect because CloudFront is a content delivery network. It caches and delivers content through edge locations, but it is not the correct service for private VPC-to-AWS-service connectivity that avoids the public internet.

AWS CloudTrail is incorrect because CloudTrail records account activity and API events for governance, audit, and security analysis. It helps track what happened, but it does not provide private network connectivity.

The key phrase is “must not travel across the public internet.” In AWS architecture, that requirement points to private connectivity using VPC endpoints powered by AWS PrivateLink. Therefore, the correct service is AWS PrivateLink.

The verified answer is D. Enhanced ability to identify bias and improve model governance. Increasing model transparency improves the ability of technical teams, business stakeholders, risk teams, and compliance teams to understand how a model behaves, what factors influence its predictions, and whether it shows unfair or biased behavior. AWS SageMaker Clarify documentation states that SageMaker Clarify provides tools to help explain how machine learning models make predictions. These tools help modelers, developers, and internal stakeholders understand model characteristics before deployment and debug predictions after deployment.

AWS also connects transparency directly to fairness, bias detection, explainability, and governance. AWS guidance states that SageMaker Clarify can be used to create comprehensive reports on model fairness and explainability for stakeholders, including risk and compliance-aligned teams and external regulators. These reports document bias detection and mitigation efforts and provide transparency into responsible AI practices. This directly supports option D because transparency improves the organization’s ability to identify bias and strengthen governance.

Option A is incorrect because transparency does not reduce the need for validation. A transparent model still requires validation, testing, monitoring, and governance controls. Option B is incorrect because transparency does not eliminate regulatory compliance monitoring. In fact, transparency often supports and strengthens compliance monitoring rather than replacing it. Option C is incorrect because transparency does not automatically remove all bias. It helps teams detect, explain, measure, and mitigate bias, but bias mitigation still requires deliberate actions such as representative data preparation, metric evaluation, retraining, sampling changes, or governance review.

Therefore, the correct outcome of increasing model transparency is an improved ability to identify bias and improve model governance.

Amazon SageMaker Model Cards document model details, performance, intended use cases, and risk considerations. They support responsible AI by improving transparency and governance.

Rekognition is computer vision.

Comprehend is NLP for entity/sentiment.

Lex is conversational AI.

???? Reference:

AWS Documentation – SageMaker Model Cards

AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises networks, ensuring traffic does not traverse the public internet.

A is correct:

" AWS PrivateLink provides private connectivity to services across VPCs, keeping API traffic off the public internet. "

(Reference: AWS PrivateLink Overview)

B (Amazon Q) is a generative AI assistant, not a network security/control tool.

C (CloudFront) is a CDN, not for private API calls.

D (CloudTrail) is for logging and monitoring, not secure connectivity.

Providing examples of text passages with corresponding positive or negative labels in the prompt followed by the new text passage to be classified is the correct prompt engineering strategy for using a large language model (LLM) on Amazon Bedrock for sentiment analysis.

Example-Driven Prompts:

This strategy, known as few-shot learning, involves giving the model examples of input-output pairs (e.g., text passages with their sentiment labels) to help it understand the task context.

It allows the model to learn from these examples and apply the learned pattern to classify new text passages correctly.

Why Option A is Correct:

Guides the Model: Providing labeled examples teaches the model how to perform sentiment analysis effectively, increasing accuracy.

Contextual Relevance: Aligns the model ' s responses to the specific task of classifying sentiment.

Why Other Options are Incorrect:

B. Detailed explanation of sentiment analysis: Unnecessary for the model ' s operation; it requires examples, not explanations.

C. New text passage without context: Provides no guidance or learning context for the model.

D. Unrelated task examples: Would confuse the model and lead to inaccurate results.

Jailbreaking an LLM refers to deliberately crafting prompts to bypass its safety guardrails and produce restricted or harmful content.

Fuzzing is input testing for software.

DoS is a service availability attack.

Pen testing (C) is allowed with AWS authorization but doesn’t describe bypassing model safeguards.

???? Reference:

AWS Responsible AI – Prompt Injection and Jailbreak Risks

Comprehensive and Detailed Explanation From Exact AWS AI documents:

BLEU is a widely used metric for evaluating machine translation by comparing machine-generated translations against reference (human) translations.

In this scenario:

Both systems are evaluated on the same dataset

The goal is to compare model output against human output

AWS ML evaluation guidance describes BLEU as suitable for relative comparison of translation quality across systems.

Why the other options are incorrect:

Absolute quality (A, C) is difficult to measure without human judgment.

BERTScore (D) is more computationally complex and less standard for operational comparisons.

AWS AI document references:

Evaluating Machine Translation Models

NLP Model Evaluation Metrics

Comparing AI and Human Translations

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

AWS KMS provides customer-managed encryption keys (CMKs) that can be used to encrypt model artifacts and other sensitive data at rest.

Bedrock integrates with AWS KMS to allow encryption of customized models with your own keys.

Amazon Inspector is for vulnerability scanning, Amazon Macie for sensitive data discovery, AWS Secrets Manager for storing credentials and secrets.

???? Reference:

AWS Documentation – Using KMS with Amazon Bedrock