AIF-C01 domain - 12% of the exam

Responsible and secure AI

Responsible and secure AI is 12% of the AIF-C01 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

87
Practice questions
3
Objectives
19
Easy
68
Medium

Where people go wrong

  • Swapping the model card for another document

    The wrong answers offer a data dictionary, a deployment runbook or installation notes where a model card is needed, or treat a model card as interchangeable with a lineage record or a registry entry. A data dictionary describes features, a runbook covers serving infrastructure, lineage traces where data came from and a registry versions artefacts and their approval status. A model card states a model's intended uses, limitations, performance and known biases, so adopters can judge whether it fits their setting.

    See it in a sample question
  • Treating overall accuracy as evidence of fairness

    The wrong answers raise aggregate accuracy, add model capacity or report one headline score and call the result fair. A model can score well overall while performing far worse for a smaller group, because the larger groups dominate the figure. Fairness is shown by comparing outcomes or error rates across defined groups and recording the method, which is what the correct answers do.

    See it in a sample question
  • Defending against prompt injection with a setting or a prompt line

    The wrong answers reach for temperature, a larger context window, TLS or a prompt line telling the model to ignore hostile text. None of these separates trusted instructions from untrusted input, which is the weakness the attack exploits. Sanitising and validating inputs, and treating retrieved content as untrusted, address the injection itself. Scoping a tool's role with least privilege and requiring human approval before a state-changing action limit the damage when an injected instruction gets through.

    See it in a sample question
  • Substituting another record for data lineage

    The wrong answers offer inference monitoring, bias detection, access control, a model registry, a feature store or hyperparameter tracking when an auditor or regulator asks where data came from. Those record runtime health, fairness, permissions or model versions. Lineage and provenance record the source, ownership, usage terms and transformation steps behind each dataset, so a past decision can be traced to the data and model version that produced it.

    See it in a sample question
  • Treating encryption or logging as data residency

    The wrong answers propose a customer-managed key, audit logging, output redaction or field minimisation to meet a rule that personal data stay inside a country or the European Union. These protect confidentiality or record access, yet the data is still stored and processed elsewhere. Residency concerns location, so the correct answer is choosing an AWS Region inside the required jurisdiction and confirming the service runs there.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleResponsible and secure AIeasy

An organisation is preparing to publish an open-source machine learning model. To help downstream users understand the model's intended uses, limitations, and known biases, which artefact should they produce?

  • AA data dictionary listing every feature in the training dataset
  • BA model card documenting intended use cases, performance metrics, and known limitations Correct
  • CA deployment runbook describing the infrastructure required to serve the model
  • DA README file listing the Python package dependencies and installation steps
Identify the model card as the standard responsible AI artefact for communicating intended use, limitations, and known biases to downstream users. Model cards, introduced to formalise responsible disclosure, are structured documents that accompany a model and cover its intended applications, out-of-scope uses, evaluation across relevant demographic subgroups, and known limitations. They allow downstream developers and organisations to assess fit-for-purpose and potential harms before integrating the model into their own systems.

Why A is wrong: A data dictionary describes features but does not communicate intended use, limitations, performance across subgroups, or ethical considerations - the core content of a model card.

Why B is correct: A model card is the standardised responsible AI artefact specifically designed to disclose a model's purpose, evaluation results, fairness considerations, and constraints so users can make informed deployment decisions.

Why C is wrong: A deployment runbook covers operational setup, not model behaviour or ethical considerations. It addresses how to run the model, not whether or how it should be used.

Why D is wrong: Installation documentation helps users set up the software but contains none of the bias, fairness, or intended-use information that responsible AI disclosure requires.

Free sampleResponsible and secure AIeasy

A data science team notices that a credit-scoring model approves loans at a significantly lower rate for one demographic group compared to all others, even though that group has similar repayment histories. Which practice most directly addresses this disparity during model development?

  • AEvaluating disaggregated fairness metrics across demographic subgroups and retraining with corrected data or constraints Correct
  • BIncreasing the model's overall accuracy on the full training dataset
  • CDeploying the model behind an API so that end users cannot inspect its decision logic
  • DRemoving all demographic attributes from the training features before the initial model fit
Understand how disaggregated fairness evaluation and targeted mitigation correct demographic disparity in AI model outputs. Responsible AI development requires measuring model behaviour separately for each subgroup rather than relying on aggregate metrics. Disaggregated fairness metrics (such as equalised odds or demographic parity difference) reveal where a model fails specific groups, enabling corrective actions such as data augmentation, re-weighting, or in-training fairness constraints that reduce the disparity directly.

Why A is correct: Disaggregated evaluation exposes differential performance per subgroup, allowing targeted mitigation such as re-sampling, re-weighting, or fairness constraints during retraining.

Why B is wrong: Tempting because higher accuracy sounds like a better model, but aggregate accuracy can improve while bias against a subgroup worsens if that group is a small fraction of the dataset.

Why C is wrong: Hiding decision logic via an API does nothing to correct the underlying bias; it only reduces transparency, which compounds responsible AI concerns.

Why D is wrong: Removing protected attributes is a common first step but does not eliminate bias because correlated proxy features (postcode, occupation) can still encode demographic information.

Free sampleResponsible and secure AImedium

A company deploys a customer-facing chatbot backed by a large language model. An attacker crafts a message that instructs the model to ignore its system prompt and reveal internal configuration details. Which control most directly prevents this class of attack?

  • AEnable TLS encryption for all traffic between the client and the model endpoint.
  • BRestrict the model's IAM role to read-only permissions on all AWS services.
  • CIncrease the model temperature to introduce randomness and reduce deterministic responses to adversarial prompts.
  • DApply input validation and prompt sanitisation to strip or neutralise adversarial instructions before they reach the model. Correct
Understand that prompt injection is mitigated by validating and sanitising model inputs before they reach the language model. Prompt injection exploits the model's inability to distinguish trusted system instructions from untrusted user input. Input validation and prompt sanitisation intercept the attack before the model processes it, unlike network-layer or IAM controls which operate at different layers and do not address the in-context instruction override.

Why A is wrong: TLS protects data in transit but does nothing to prevent malicious instructions embedded in the model input from overriding system behaviour. The attack exploits the model's instruction-following, not network interception.

Why B is wrong: Least-privilege IAM limits downstream blast radius if the model calls AWS APIs, but does not prevent the model from responding to injected instructions with information it already holds in context. The attack succeeds before any IAM call is made.

Why C is wrong: Higher temperature makes outputs less predictable but does not block the model from following injected instructions; it may simply produce a slightly different but still harmful response. Temperature is a generation parameter, not a security control.

Why D is correct: Prompt injection attacks rely on the model treating user-supplied text as trusted instructions. Sanitising and validating inputs - removing delimiter tokens, detecting instruction-override patterns - removes the attack vector at its origin.

Free sampleResponsible and secure AImedium

A bank runs a credit-decision model in a regulated market. An auditor asks the team to show, for any individual decision made last quarter, exactly which dataset version, feature transformations, and model artefact produced it. The team can name the current model but cannot reconstruct which inputs and version were live on a given past date. Which governance capability is the team missing?

  • AReal-time inference monitoring that tracks latency and request volume for the production endpoint
  • BA bias-detection report that measures approval-rate disparities across customer demographic groups
  • CData lineage and traceability that links each prediction to its dataset version, transformations, and model version Correct
  • DAn access-control policy that restricts who can invoke the credit-decision model in production
Data lineage and traceability let an organisation reconstruct which data version, transformations, and model artefact produced any past decision. Reconstructing a historical decision requires a recorded chain linking the specific source data version, the transformations applied, and the exact model artefact in use at that time, which is precisely what data lineage and traceability provide for audit and compliance.

Why A is wrong: Inference monitoring captures operational health such as throughput and latency, which is useful but does not record which data version or artefact produced a historical decision, so it cannot satisfy the auditor's reconstruction request.

Why B is wrong: Bias detection addresses fairness across groups and is part of responsible AI, but it does not trace an individual decision back to its specific data version and artefact, so it answers a different governance question.

Why C is correct: Lineage and traceability record the chain from source data through transformations to the specific model artefact, letting the team reconstruct exactly which inputs and version produced any past decision, which is what the auditor demands.

Why D is wrong: Access control governs who may call the model and is a sound security control, yet it stores no record of which data and version generated a particular historical decision, so it cannot reconstruct the audit trail.

Free sampleResponsible and secure AImedium

A European retailer plans to run a generative AI customer-service assistant on AWS. Its data protection regulator requires that customer personal data processed by the assistant must be stored and processed only within the European Union. The team must choose how this requirement shapes the deployment. Which decision most directly satisfies this regulatory constraint?

  • AEncrypt all customer data at rest with a customer-managed key so the regulator's residency expectation is met regardless of where the workload runs.
  • BDeploy the assistant and its data stores in an AWS Region located within the European Union and restrict processing to that Region. Correct
  • CEnable detailed request logging in AWS CloudTrail so every access to customer data is recorded for the regulator to inspect later.
  • DApply a content guardrail that redacts personal data from model outputs before responses reach the customer.
Data-residency regulation is satisfied by choosing the geographic location of storage and processing, not by encryption, logging, or output filtering. Residency obligations constrain the physical jurisdiction in which personal data is held and processed; only selecting an AWS Region inside that jurisdiction and confining processing to it keeps the data within the legally required boundary, whereas encryption, logging, and redaction address different risks.

Why A is wrong: Encryption with a customer-managed key protects confidentiality and supports access control, but it does not control the physical location where data is stored or processed, so it does not satisfy a data-residency obligation.

Why B is correct: Data-residency rules are about geographic location, and selecting an in-region AWS Region with processing confined to it keeps the personal data inside the required jurisdiction, which is exactly what the regulator demands.

Why C is wrong: Audit logging creates a record of access and supports accountability, but recording where data went after the fact does not keep the data inside the required jurisdiction, which is the actual obligation here.

Why D is wrong: Output redaction reduces the leakage of personal data into responses, but the underlying data is still stored and processed somewhere, so it does not address where processing physically occurs as residency law requires.

Other domains in this exam

See also the AIF-C01 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Amazon Web Services. Original, blueprint-aligned practice material only.