Course menuAIF-C01

Exams / AIF-C01 / Study guide / Data governance and lineage

Data governance and lineage: AIF-C01 study notes and practice questions

What to know about Data governance and lineage for the AIF-C01 exam, from the Security, Compliance, and Governance for AI Solutions domain (14% of the exam guide), then 2 free questions to test it. Part of the AIF-C01 study guide.

Last verified against current AWS documentation ·How we write our questions

What to know for the exam

Data governance questions ask how to know, control and prove what data an AI system uses.

What governance covers

Area Question AWS tools
Lineage Where did this data and model come from, and what steps produced them? SageMaker ML Lineage Tracking, SageMaker Model Registry
Cataloging What data do we have, and what is it? AWS Glue Data Catalog, Amazon SageMaker Catalog
Access control Who may use which data? IAM, AWS Lake Formation fine-grained permissions
Residency Which country or Region holds the data? Region choice; geographic cross-Region inference profiles in Bedrock
Retention and lifecycle How long is data kept, and when is it deleted? S3 Lifecycle rules, retention policies
Quality Is the data accurate and complete? AWS Glue Data Quality, SageMaker Data Wrangler
Sensitive data Where is personal data? Amazon Macie
Monitoring Is data or model behavior drifting? SageMaker Model Monitor

Practices

  • Data source citation: record where training and retrieval data came from, including licenses.
  • Data minimization: use only the data the task needs.
  • Privacy: anonymize or mask personal data; get consent where required.
  • Documentation: model cards and data sheets describe data and intended use.
  • Logging and auditing: keep records of data access and model use.

Common traps

  • Lineage vs catalog. A catalog lists what data exists; lineage tracks how data and models were produced.
  • Cross-Region inference and residency. Use geographic profiles to keep processing inside one geography when rules require it.
  • Keeping data forever “just in case”. Retention rules should match the purpose and the law.

Try the 2 practice questions

During an audit, a regulator asks a car insurer to show exactly which dataset version, hyperparameters and processing steps produced the pricing model now in production, and to reproduce that model.

The data team retrains weekly from one shared dataset, and the record must be kept for seven years.

Which capability BEST provides this?

Choose one answer.

  1. A. SageMaker ML Lineage Tracking, which records the datasets, training job parameters and pipeline steps behind each model.
  2. B. AWS CloudTrail logs, which record who called the training APIs and when each call was made.
  3. C. AWS Config history of the training instances, which shows how their configuration settings changed over time.
  4. D. S3 Versioning on the training bucket, which keeps every earlier version of each object in the bucket.
Show the answer and explanation

Answer: A

  • A. Right: Correct. Lineage Tracking creates and stores information about each stage of an ML workflow, so the artifacts behind a model can be queried and the model reproduced. Learn more: Amazon SageMaker ML Lineage Tracking (opens in a new tab)
  • B. Wrong: CloudTrail records API activity for auditing. It shows who called an action and when, but not which dataset and hyperparameters produced a model.
  • C. Wrong: Config tracks resource configurations, such as instance settings. It does not link a model to the datasets and parameters used to train it.
  • D. Wrong: Versioning keeps old copies of the data, which helps. It does not record the training job, its parameters or the steps that connected the data to the model.

Explanation

SageMaker ML Lineage Tracking records the steps and artifacts of an ML workflow, from data preparation to deployment, so a team can trace and reproduce a model. Audit logs, configuration history and object versions each answer a different question. This question tests choosing lineage over general audit tools.

Study

A European bank uses foundation models on Amazon Bedrock.

Its data residency policy requires that prompts and responses are processed only within the EU. Traffic peaks sometimes exceed what one Region can serve, so the bank needs cross-Region inference.

Which approach meets both requirements?

Choose one answer.

  1. A. Use an EU geographic cross-Region inference profile, which routes requests only among Regions within the EU.
  2. B. Use a global cross-Region inference profile, which can spread requests across Regions beyond any single geography.
  3. C. Use one in-Region on-demand model only, and accept that requests above the Region's capacity are throttled at peak times.
  4. D. Use a US geographic cross-Region inference profile, since it offers more capacity than the EU profile.
Show the answer and explanation

Answer: A

  • A. Right: Correct. Geographic profiles keep routing inside one geography, so EU requests stay among EU Regions while the bank absorbs traffic peaks. Learn more: Geographic cross-Region inference - Amazon Bedrock (opens in a new tab)
  • B. Wrong: A global profile is not limited to one geography, so it can send requests to Regions outside the EU. That breaks the residency rule.
  • C. Wrong: A single Region keeps data in the EU but cannot absorb peak traffic beyond its capacity. The bank's throughput need is not met.
  • D. Wrong: A US profile routes requests only among US Regions, which moves EU prompts outside the EU. It fails the residency rule.

Explanation

Cross-Region inference raises throughput by routing requests across Regions. Geographic profiles restrict that routing to one geography, such as the EU or the US, which is how residency rules are met. This question tests combining a throughput need with a residency limit.

Study

Want more on Data governance and lineage? The 5 full-length practice sets have 13 more Data governance and lineage questions, 325 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets

Study Data governance and lineage

More Security, Compliance, and Governance for AI Solutions topics