CCNA Guidelines for Responsible AI Questions — Page 2 of 2

MCQeasy

A startup is developing a mobile app that uses facial recognition to verify user identity for account access. The app is intended for a global audience, but the training data predominantly includes images of light-skinned individuals. During beta testing, users with darker skin tones report frequent verification failures, while light-skinned users have a high success rate. The startup wants to release the app soon and needs to address this fairness issue without delaying the launch too much. The team has limited resources. Which approach should they take to most effectively mitigate the bias while meeting the launch timeline?

A.Apply a post-processing rule to increase acceptance rate for users with darker skin tones

B.Lower the similarity threshold for all users to improve acceptance rates

C.Defer verification for users with darker skin tones to manual human review

D.Collect more diverse training data and augment the existing dataset, then retrain the model

AnswerD

Retraining on augmented, demographically diverse data corrects the underlying representation imbalance causing disparate error rates across skin tones. This directly addresses the root cause of the fairness failure while remaining feasible within the startup's limited resources and launch timeline.

Why this answer

The root cause of the bias is a skewed training dataset that underrepresents darker skin tones. Collecting more diverse data and augmenting the existing dataset directly addresses the data imbalance, allowing the facial recognition model to learn robust features for all skin tones. Retraining the model on this enriched dataset is the most effective long-term fix that aligns with responsible AI principles, and with focused effort it can be completed within a reasonable timeline without introducing the risks of post-hoc patches.

Exam trap

AWS often tests the misconception that a quick operational fix (like adjusting thresholds or adding manual review) can effectively solve algorithmic bias, when in fact the only principled solution is to address the data imbalance at the source.

How to eliminate wrong answers

Option A is wrong because applying a post-processing rule to artificially increase acceptance rates for darker-skinned users does not fix the underlying model bias; it merely masks the problem and can lead to higher false acceptance rates, undermining security. Option B is wrong because lowering the similarity threshold for all users would increase false positives across the board, reducing the overall security of the verification system without addressing the specific failure mode for darker skin tones. Option C is wrong because deferring verification to manual human review for darker-skinned users creates a separate, slower process that introduces user friction, scales poorly with limited resources, and does not resolve the model's inherent bias.

Practice this question →

MCQeasy

A company develops a chatbot using Amazon Lex. To ensure transparency, what should the chatbot do when it cannot answer a question?

A.Remain silent and wait for the next input

B.Provide a random answer from a predefined list

C.Clearly state that it cannot answer and offer alternatives

D.Automatically escalate all unanswered questions to a human

AnswerC

When confidence is low, the bot must acknowledge its inability rather than fabricate an answer, satisfying the transparency requirement. Explicitly stating it cannot answer and suggesting alternatives prevents misleading users, which is central to responsible conversational AI design.

Why this answer

Responsible AI guidelines, including those from AWS for Amazon Lex, require that when a chatbot cannot answer a question, it should clearly state its inability and offer alternatives (e.g., rephrasing the query or providing related topics). This maintains transparency and user trust, aligning with the 'Explainability' principle under the Guidelines for Responsible AI.

Exam trap

AWS often tests the misconception that a chatbot should always escalate or remain passive when it cannot answer, but the correct approach under responsible AI is to acknowledge the limitation and offer alternatives, not to hide or mislead.

How to eliminate wrong answers

Option A is wrong because remaining silent and waiting for the next input violates transparency and can confuse users, as it provides no feedback or guidance. Option B is wrong because providing a random answer from a predefined list is deceptive and can mislead users, undermining the principle of honesty and accountability in AI. Option D is wrong because automatically escalating all unanswered questions to a human is inefficient and not always necessary; the chatbot should first attempt to offer alternatives or clarify before escalation, as per responsible AI practices.

Practice this question →

MCQhard

A machine learning team is building a credit risk model and discovers that the training data has a significant imbalance in loan approval rates between two demographic groups. They decide to reweight the training samples using a preprocessing technique. Which SageMaker Clarify feature can help compute the appropriate sample weights to achieve demographic parity?

A.Clarify preprocessing (reweighting)

B.Clarify post-training bias metrics

C.Model Monitor bias drift

D.Clarify explainability (SHAP)

AnswerA

Clarify preprocessing computes sample weights that rebalance labelled outcomes across demographic groups, directly satisfying the demographic parity constraint. It analyses the training dataset's label distribution per group and emits weights for the training job, correcting the imbalance before model fitting rather than post-hoc adjusting predictions.

Why this answer

SageMaker Clarify's preprocessing (reweighting) feature directly computes sample weights to adjust for imbalances in training data, enabling demographic parity by assigning higher weights to underrepresented groups. This is a pre-training bias mitigation technique that modifies the dataset before model training, aligning with the team's goal of reweighting samples to address loan approval rate disparities.

Exam trap

The trap here is that candidates confuse post-training bias metrics (Option B) with pre-training mitigation techniques, assuming that measuring bias is the same as correcting it via sample weights.

How to eliminate wrong answers

Option B is wrong because post-training bias metrics measure bias after model training (e.g., difference in positive proportions), not compute sample weights for preprocessing. Option C is wrong because Model Monitor bias drift detects changes in bias over time during inference, not pre-training weight computation. Option D is wrong because Clarify explainability (SHAP) provides feature attribution for model predictions, not sample reweighting for bias mitigation.

Practice this question →

MCQmedium

A financial services company is deploying a generative AI chatbot to assist customers with account inquiries. The company wants to ensure the chatbot does not generate biased or harmful responses. Which combination of AWS services and practices should the company implement to monitor and mitigate these risks?

A.Configure the chatbot to use a pre-trained model from SageMaker JumpStart and disable logging to avoid storing sensitive customer data.

B.Use Amazon Rekognition to analyze chat logs for biased language and automatically block responses with a confidence score above 90%.

C.Use Amazon SageMaker Clarify to detect bias in model outputs and implement a human-in-the-loop workflow with Amazon A2I to review flagged responses.

D.Deploy Amazon Lex with built-in sentiment analysis to detect negative customer emotions and automatically escalate to a human agent.

AnswerC

SageMaker Clarify detects bias in model outputs, satisfying the requirement to monitor harmful responses. Amazon A2I adds human-in-the-loop review of flagged outputs, providing the mitigation control the financial services chatbot needs before responses reach customers.

Why this answer

Amazon SageMaker Clarify is specifically designed to detect bias in machine learning models and their outputs, while Amazon Augmented AI (A2I) enables a human-in-the-loop workflow to review flagged responses. This combination directly addresses the requirement to monitor and mitigate biased or harmful responses from a generative AI chatbot, ensuring responsible AI practices.

Exam trap

The AIF-C01 exam often tests the distinction between services that detect customer sentiment (like Amazon Comprehend or Lex sentiment analysis) versus services that detect bias in model outputs (like SageMaker Clarify), leading candidates to mistakenly choose sentiment analysis options for bias detection.

How to eliminate wrong answers

Option A is wrong because disabling logging prevents the monitoring and auditing necessary to detect biased or harmful responses, and using a pre-trained model from SageMaker JumpStart without additional safeguards does not mitigate bias. Option B is wrong because Amazon Rekognition is an image and video analysis service, not designed for analyzing text chat logs for biased language; it cannot process text-based conversations. Option D is wrong because Amazon Lex's built-in sentiment analysis detects customer emotions but does not detect bias or harmful content in the chatbot's responses, and escalation to a human agent does not proactively mitigate biased outputs.

Practice this question →

Multi-Selecthard

Which THREE considerations are essential for ensuring responsible AI in a model that predicts employee performance? (Choose 3)

Select 3 answers

A.Minimize the number of features to reduce cost

B.Publish the model's predictions publicly for transparency

C.Incorporate human review before final decisions

D.Ensure employee data privacy and consent

E.Test for bias across demographic groups

AnswersC, D, E

Human review before final decisions satisfies the accountability constraint: a performance prediction can carry employment consequences, so a person must evaluate context the model cannot capture and challenge biased or erroneous outputs. This keeps a human answerable for outcomes, rather than deferring to automated scoring, as responsible AI practise requires.

Why this answer

Option C is correct because responsible AI in an HR context requires human-in-the-loop oversight: performance predictions should inform, not automate, decisions about employees, so a human reviewer can catch errors and provide context before any action is taken. Option D is correct because employee performance data is personal and often sensitive, so the model must comply with privacy and consent requirements (e.g., GDPR lawful basis, purpose limitation, and data minimization) to be ethically and legally sound. Option E is correct because bias testing across demographic groups (e.g., comparing error rates, selection rates, and disparate impact metrics by gender, age, or ethnicity) is essential to detect and mitigate discriminatory outcomes in performance predictions.

Option A does not belong because minimizing features to cut cost is an efficiency concern, not a responsible-AI safeguard, and can even harm fairness if it removes relevant variables. Option B does not belong because publishing individual employees' predicted performance publicly would violate privacy and confidentiality rather than constitute meaningful transparency, which is better served by model documentation and explainability to authorized stakeholders.

Exam trap

The AIF-C01 exam often tests the misconception that transparency means public disclosure of all model outputs, whereas in responsible AI, transparency refers to explainability and auditability of the model's logic, not exposing sensitive predictions.

Practice this question →

MCQhard

A healthcare startup uses Amazon SageMaker to train a model predicting patient readmission. They need to ensure the model's predictions do not discriminate based on protected attributes like age or race. Which SageMaker feature allows them to monitor and mitigate bias during training?

A.SageMaker Model Monitor

B.SageMaker Autopilot

C.SageMaker Debugger

D.SageMaker Clarify

AnswerD

SageMaker Clarify computes bias metrics such as disparate impact and demographic parity on training data and model outputs, detecting imbalance across protected attributes like age and race. It also provides SHAP-based feature attribution, satisfying the requirement to monitor and mitigate bias during training.

Why this answer

SageMaker Clarify is the correct choice because it is specifically designed to detect and mitigate bias in machine learning models. It provides built-in capabilities to analyze training data and model predictions for bias against protected attributes such as age or race, and can generate bias reports and suggest mitigation strategies during training.

Exam trap

The trap here is that candidates often confuse SageMaker Clarify with SageMaker Model Monitor, assuming that monitoring for data drift also covers bias detection, but Clarify is the dedicated service for bias detection and mitigation.

How to eliminate wrong answers

Option A is wrong because SageMaker Model Monitor is used to detect data drift and model quality degradation in production, not to analyze or mitigate bias during training. Option B is wrong because SageMaker Autopilot automates the process of building, training, and tuning models, but it does not include built-in bias detection or mitigation features. Option C is wrong because SageMaker Debugger is designed to monitor training jobs for issues like vanishing gradients or overfitting by capturing tensors and metrics, not for bias detection or mitigation.

Practice this question →

MCQeasy

Which of the following is NOT one of the core principles of responsible AI as defined by AWS?

A.Transparency

B.Fairness

C.Profitability

D.Robustness

AnswerC

AWS responsible AI centres on fairness, explainability, privacy, security, safety, controllability and governance. Profitability is a commercial objective, not a responsible AI principle, so it is correctly excluded, satisfying the question's requirement to identify the option that is NOT a core principle.

Why this answer

Profitability is not one of the core principles of responsible AI as defined by AWS. AWS defines six core principles: Fairness, Transparency, Robustness, Privacy, Security, and Explainability. Profitability is a business objective, not a principle for ensuring ethical and trustworthy AI systems.

Exam trap

The trap here is that candidates may confuse business objectives like profitability or cost-efficiency with the ethical and technical governance principles that AWS specifically defines for responsible AI.

How to eliminate wrong answers

Option A is wrong because Transparency is a core AWS responsible AI principle that requires AI systems to be open about their capabilities, limitations, and decision-making processes. Option B is wrong because Fairness is a core principle that mandates AI systems should treat all groups equitably and avoid bias. Option D is wrong because Robustness is a core principle that ensures AI systems perform reliably under varying conditions and resist adversarial inputs.

Practice this question →