Domain 1 of 4 · Chapter 1 of 3

Describe core AI concepts and terminology

AI, machine learning, and generative AI as related categories

Two AI systems arrive on a manager's desk: one labels each card payment as genuine or fraudulent, the other drafts replies to customer emails. Both are artificial intelligence (AI), yet only the second generates anything, and naming that difference correctly is the first vocabulary skill a business leader needs. This topic follows Task 1.1 of the AWS AIB-C01 exam guide, 'Describe core AI concepts and define terminology'[1]: what AI, machine learning (ML), and generative AI are, how a model learns from data and is then used, language, vision, speech, and recommendation capabilities, the AWS offerings Amazon Bedrock, Amazon SageMaker AI, and Amazon Quick, data forms and document processing, why data quality and honest evaluation decide outcomes, and which frameworks give an organization one shared vocabulary. The same guide lists two neighboring tasks separately[1], 'Task 1.2: Identify and select appropriate AI solution types' and 'Task 1.3: Apply GenAI concepts and techniques'; see Identify and select appropriate AI solutions and Apply generative AI concepts and techniques.

Related categories, from broad to specialized

The terms below are related categories, not synonyms: their relationships are not all strict containment. Of the terms below, machine learning, deep learning, foundation models, and large language models nest in that order. Generative AI works by using machine learning models[2], so it sits inside machine learning, and it overlaps deep learning, with one part inside and one part outside. Inside deep learning are its modern forms: modern generative AI emerged in the late 2010s with advancements in deep learning[2], and the foundation models below, which AWS describes as a form of generative AI[3], are large deep learning neural networks[3]. Outside deep learning are older statistical generative models, which predate it: primitive generative models have been used for decades in statistics[2], whereas neural networks and deep learning were recent precursors for modern generative AI[2]. Large language models are one class of foundation models[2], so they sit inside generative AI too, as the figure below shows; AWS places foundation models as a group under generative AI, though a single model can convert input into embeddings[4] or be intended for understanding languages[3] instead of creating new content, as the foundation-model and large-language-model entries below explain.

Generation is not the test for AI

These relationships settle a common misreading at once: a system does not have to generate content to count as AI. Classifying transactions or recommending products are prediction and recognition tasks, and ML models perform specific analysis tasks like classifying documents, labeling images, or predicting the maintenance schedule of factory equipment[5] without producing anything new. The overlap also runs the other way: a generative model can classify when asked to, because classification is among the language tasks LLMs handle[2]. Category membership describes how a system gets its capability, not the single task it happens to perform.

How a generative LLM produces language

A generative LLM, the kind that writes text, works in tokens, the units of text (whole words or word parts) that it reads and writes. During training it adjusts its parameter values until it correctly predicts the next token from the previous sequence of input tokens[6]; parameters are the internal numbers a model learns, explained in the next section. When it generates a response, it predicts one token after another from the prompt (the instruction and input you give it) and the tokens it has already produced. Foundation model and LLM are not interchangeable names: the foundation-model category also includes text-to-image models such as Stable Diffusion[3], so every LLM is a foundation model but not every foundation model is an LLM.

Why foundation models change the economics

Before foundation models, each new text task usually meant training a narrow model for it. A foundation model is reusable instead: it is faster and cheaper to use pretrained FMs to develop new ML applications rather than train unique ML models from the ground up[3], and building a foundation model from scratch is expensive and training may take months[3]. Broad pretraining has limits, though. Broad pretraining does not establish knowledge of your private contracts or customer records, and AWS notes that answers on certain subject matter may be unreliable[3]. Evaluate it for your specific use case[7] and adapt it where the evaluation shows a gap.

Broad capability is not artificial general intelligence

Artificial general intelligence (AGI) is a field of theoretical AI research that attempts to create software with human-like intelligence and the ability to self-teach, performing tasks it was not necessarily trained or developed for[8]. The AI systems businesses deploy are task-bounded, which AWS calls narrow or weak AI: even emerging generative AI applications with better memory retention are considered weak AI because they cannot be repurposed for other domains[8]. Reusing one foundation model for several business tasks, or letting an agent (an AI system that pursues a goal by taking actions) complete a workflow on its own, is useful task-bounded capability and does not by itself demonstrate AGI.

The takeaway: distinguish these categories by how a system gets its capability, and do not let generation, breadth, or autonomy stand in for a definition.

Artificial intelligence (AI)Machine learning (ML)Deep learningFoundation models (FMs)Large languagemodels (LLMs)Generative AIOlder statisticalgenerative models
AWS classifies FMs as generative AI: generative AI (dashed) is in ML, holds FMs and LLMs, and extends below deep learning to older statistical generative models

From learning algorithm to trained model to prediction

Algorithm, model, and inference are distinct terms, and the AWS AIB-C01 exam guide names all three among the fundamental AI concepts to recognize and explain in business contexts[1]. Keeping them apart tells you whether a proposal changes the learning method, the learned result, or only how the result is used.

Algorithm versus trained model

A learning algorithm is the procedure that finds patterns; a trained model is what the procedure produces. AWS illustrates the difference with a small case: given the input and output pairs (2,10), (5,19), and (9,31), the algorithm computes the relationship o = 3 × i + 4, and given the input 7 it predicts 25[5]. The procedure that searched for the relationship is the algorithm; the resulting formula is the model, and the numbers 3 and 4 are its learned parameters. In a real system the model encapsulates what it learned in its parameters[5], which training adjusts to shrink the gap between predictions and the known outcomes. Run the same algorithm on a different company's data and you can get a different model. So when a team proposes a training change, ask which of two things it is: changing the learning method, or updating the learned model with new training evidence.

Training versus inference

Training learns the parameters from examples; inference uses the finished model. Inferencing is the process of an AI model generating educated predictions or outputs from new data[9], using the learned parameters it ended training with. Forecasting next month's demand and drafting a reply to a customer are both inference, even when the input contains details the model never saw before.

Ordinary inference does not change the model. AWS explains model drift in exactly those terms: when a model's weights (its learned parameters) remain fixed based on previous AI training data[9] and the world shifts, the outputs become less accurate, and retraining is the remedy. Storing every prediction request in an archive therefore teaches the model nothing; learning from newly collected examples needs an explicit training or update step.

One AWS statement can look like a contradiction here. AWS also writes that foundation models can continue to learn from data inputs or prompts during inference[3], and the same passage explains what that means: carefully curated prompts produce better outputs. A prompt steers that one response, while the learned parameters stay as they were.

Predictions are estimates, and generation can vary

A learned prediction is an estimate, not a promise. Machine learning can be made deterministic[5], so a model may return the same prediction every time for the same input, yet a repeatable prediction is still not a promise about the real-world outcome: a demand forecast is useful even though actual demand may differ from it. Generative models add a different kind of variation, in the output itself: for any given sequence, a model determines a probability distribution of options for the next token and samples from this distribution[10], so the same prompt can produce different wording on different requests. Inference parameters, which are settings and not the learned parameters (those stay unchanged), narrow or widen that variation: when running model inference, you can adjust inference parameters to influence the model response[10]. Temperature is one such setting; it affects the shape of the probability distribution for the predicted output[10], and a lower temperature leads to more deterministic responses, and a higher temperature leads to more random responses[10].

The figure below traces the two phases: historical examples run through the learning algorithm to produce the trained model, new examples update the model's learned parameters only through a training or update step, and each new input passes through the unchanged model at inference to give a prediction that is an estimate.

To sum up: the algorithm learns, the model holds what was learned, inference applies it without changing it, and predictions are estimates, not guarantees.

Historical examplesLearning algorithmNew examples(retraining)TrainingTrained model(learned parameters)New inputInferencePrediction(an estimate)
Training versus inference: the learning algorithm produces the trained model, and inference applies it unchanged to each new input

Learning approaches: matching the method to your evidence

For example, suppose a retailer has three questions, each answered by a different way of learning. To flag fraudulent card transactions, it can learn from past transactions already confirmed as fraud or genuine, which is AWS's own example of training a system to classify fraudulent and genuine transactions[5] in supervised learning. To find natural groups among customers that nobody has grouped yet, it needs unsupervised learning, whose algorithms train on unlabeled data[5]. To choose a sequence of offers that keeps customers loyal, it learns from reward feedback associated with its offers, the reward-and-punishment paradigm[11] of reinforcement learning. The evidence the retailer holds decides the approach, and the decision tree in this topic's overview walks the same choice for every approach in the table below.

Approach Evidence it needs What it produces Example
Supervised learning Examples paired with known outcomes (labels) A category (classification) or a number (regression) Fraudulent or genuine; a selling price
Unsupervised learning Data with no labels Groups, associations, or unusual observations Customer segments; bread bought with butter
Semi-supervised learning A few labeled examples plus many unlabeled ones A model trained on both Long documents too costly to label in full
Self-supervised learning Unlabeled data from which targets can be derived Patterns learned without human labels Foundation-model pretraining
Reinforcement learning Actions and the rewards that follow them A strategy that maximizes reward over time Offer sequences aimed at long-term retention

Supervised learning: known outcomes

In supervised learning the sample data specifies both the input and the output[5]; the known output for each example is its label. That is why the fraud case above fits: its past transactions already carry known outcomes. Supervised models predict one of two kinds of target. Classification predicts a category, either one of two possible classes (binary classification) or one of more than two outcomes (multiclass classification)[12]; regression predicts a numeric value[12], such as a selling price. Before choosing it, a business has to name the outcome it wants predicted and confirm that reliable historical examples of that outcome exist.

Unsupervised learning: patterns without answers

Unsupervised learning algorithms train on unlabeled data[5] and find structure on their own: grouping similar items (clustering), such as news articles into topics, or finding items that occur together (association), such as a customer who buys butter being most likely to also buy bread[5]. AWS states the limit plainly: it cannot give precise predictions[5]. The groups it finds are similarity groups that need business interpretation. A cluster of customers who look alike is not a set of verified churn labels, and a segmentation run cannot stand in for a model trained to forecast an exact revenue figure.

Anomaly detection: a signal, not a verdict

Anomaly detection is examining specific data points and detecting rare occurrences that seem suspicious because they are different from the established pattern of behaviors[13]. It helps when you lack enough labeled examples of the failures you care about. For fraud with little labeled history, AWS describes an unsupervised anomaly detection model as one option, with the caveat that not all fraud events are anomalies, and not all anomalies are indeed fraud[14]. An unusual transaction or machine reading is therefore a reason to investigate, not proof of fraud or of a specific fault. A supervised classifier answers a different question: it recognizes the categories present in its labeled examples, while anomaly detection flags departures from normal.

Semi-supervised and self-supervised learning: when labels are scarce

Scarce labels do not stop learning. Semi-supervised learning relies on a small amount of labeled data and a large amount of unlabeled data[5], which suits material such as long documents that would be too time-consuming for humans to read and label[5]. Self-supervised learning goes further and derives the targets from the data itself: foundation models use self-supervised learning to create labels from input data[3], for example by learning to predict the next word in a text. Neither approach requires a person to supply the correct answer for every example, and neither removes the need to evaluate the result against the actual business task.

Reinforcement learning: rewards over time

Reinforcement learning (RL) learns from actions and their consequences instead of from paired correct answers. RL algorithms use a reward-and-punishment paradigm, are capable of delayed gratification, and may find that the best overall strategy requires short-term sacrifices[11]. That strength is also the business risk, because the system pursues whatever the reward measures: as the data scientist designs the rewards, they can influence the results[5]. Reward only immediate clicks and the system learns to chase clicks, even when the real goal is long-term retention.

The takeaway: start from the evidence. Known outcomes point to supervised learning, no labels to unsupervised discovery, unlabeled data from which targets can be derived (as in foundation-model pretraining) to self-supervised learning, a few labels plus many unlabeled examples to semi-supervised learning, and actions with delayed results to reinforcement learning.

Language, vision, speech, and recommendation capabilities

Suppose, for example, a retailer's service team receives written complaints, damaged-parcel photos, and recorded calls, and wants to show shoppers relevant products; the AWS AIB-C01 exam guide expects a business professional to recognize common categories of AI tools and their business applications[15], such as recommendation engines and computer vision. Business information arrives in different forms (written text, images, spoken audio, records of customer behavior), and AI capability families specialize in tasks and input types that can overlap. Each job matches one family below; the table is a common set, not an exhaustive list.

Capability What it works on What it produces Business example
Natural language processing (NLP) Written or transcribed human language Meaning: intent, sentiment, translation Sorting support emails by intent
Computer vision Images and video Information found in the visual input Spotting product defects before shipping
Speech recognition (speech to text) Spoken audio Text Transcribing a support call
Recommendation engine Interaction history plus item and user information A selected or ranked set of existing items A Recommended for you product list

Transcription and sentiment are separate tasks

Speech recognition produces words, not their meaning. To learn how a caller felt, transcribe the call first and then run sentiment analysis (an NLP task) on the transcript; contact centers combine the two to derive actionable insights from call analytics[16]. A transcript alone does not measure customer sentiment.

Recommendation selects items; writing is a separate task

A recommendation engine chooses or ranks existing items for a person, using evidence such as past interactions, preferences, and item information. Amazon Personalize is one AWS example among the recommendation tools available: it generates recommendations primarily based on item interaction data, such as users clicking items, and in some cases also uses data from items and users such as genre or price[19]. Writing a personalized message about the chosen item is a different capability. Personalize's own email use case splits the work the same way: Personalize generates batch recommendations for all users on an email list, and then an AWS service or third-party service sends the emails[19]. A customer experience can combine selection with generated wording, but generating the wording does not perform the selection.

The takeaway: match the capability to the form of the information and to the task (understand, see, transcribe, or select), and expect real solutions to chain more than one.

Amazon Bedrock, Amazon SageMaker AI, and Amazon Quick

Suppose a company's developers want a foundation-model support assistant, its data scientists their own churn model, and its analysts AI answers from company data; the AIB-C01 exam guide describes Bedrock as a generative AI platform, SageMaker AI as custom ML, and Quick as AI-powered business assistants[15]. These three AWS offerings are listed in the exam's scope, and they serve different people at different layers. Overlapping AI capabilities do not make them interchangeable; the useful question is who is building or using what.

Offering Who typically uses it What it provides
Amazon Bedrock Teams building generative AI applications and agents Managed access to a choice of foundation models plus the capabilities to build generative AI applications
Amazon SageMaker AI Data scientists and developers A managed environment to build, train, and deploy their own ML models
Amazon Quick Business users Ready-to-use AI assistance grounded in connected company data, plus analytics and workflow automation

The takeaway: builders assemble generative AI applications on Bedrock, technical teams develop their own models on SageMaker AI, and business users work with Quick.

Structured, semi-structured, and unstructured data

Whether data is structured depends on its schema, not on whether it holds numbers or words. A schema is the predefined design of a dataset: the field names, data types, and constraints that every new record follows[23]. The AWS AIB-C01 exam guide asks candidates to distinguish between structured and unstructured data and explain the relevance of data types for AI[1]: which of the three data forms a source takes, and which type of information each input carries (its modality). Evaluating data readiness across sources, including the effects of data silos on AI initiatives[24], is a separate task in the guide, 'Task 4.2: Establish data and infrastructure foundations for AI'; data silos are digital systems where data is difficult to share or access by other services[25]. See Establish data and infrastructure foundations for AI.

Data form Defining feature Examples What AI must do with it
Structured A predefined schema of named fields Transaction rows with customer, date, and amount Analyze records
Semi-structured Self-describing tags and metadata without a rigid table A media library with dates and topic tags Filter by tags; analyze the content separately
Unstructured No predefined schema Narrative documents, images, audio, video, scanned pages Understand the content

Structured versus unstructured

Structured data is typically tabular with rows and columns that clearly define data attributes[23]. Unstructured data exists without any predefined schema[23]: plain text documents, video and audio files, images, and scanned documents. The difference is the schema, not the subject matter: a structured database can easily track quantitative information, such as product prices and order volume, and can also store customer feedback for sentiment analysis[26].

Text is not automatically unstructured. A short product-category or customer-ID field is part of a schema and is structured, while a digital contract with no fixed fields is still unstructured. The distinction tells you which job you are buying: record analysis for structured data, content understanding for unstructured data.

Semi-structured data: metadata is not meaning

Semi-structured data lacks a specific relational or tabular data model but includes self-describing elements such as tags, metadata, and nesting[23]. A recording library tagged with dates and topics can be filtered by those tags, but the tags do not tell you what anyone said in a recording; that still needs analysis of the content. Searching document filenames is likewise not the same as reading the obligations inside the contracts they name.

Modality: the type of information

A modality is a type of information, such as text, images, audio, or video, and a multimodal capability handles more than one. AWS describes multi-modal agents as AI systems that can understand and analyze data in multiple modalities[27]. A text-only capability receives only text, so it cannot inspect the damage shown in a claim photo or read the values in a scanned chart just because a user mentions the image. For a mixed-information task, list which modalities the decision depends on and check that any conversion, such as summarizing an image as text, keeps the evidence the decision needs.

The takeaway: identify the data form and every modality first, then pick a capability that reads that form and does the job you need (search, analyze records, or understand content).

Optical character recognition versus intelligent document processing

Reading a document's text and capturing its business fields are different jobs; the AWS AIB-C01 exam guide lists document extraction[15] among the common categories of AI tools. Optical character recognition (OCR) converts an image of text into a machine-readable text format[28], which makes a scanned page searchable. Intelligent document processing (IDP) goes further: it automates the process of manual data entry from paper-based documents or document images to digital form[29], for example extracting invoice data and entering it in the required format in the accounting system[29], and it helps with data extraction, validation, and classification[29]. OCR is one of the technologies IDP builds on[29]. A scanned invoice made searchable through OCR shows that text recognition occurred, not that the invoice number, total, and payment terms were captured correctly in the business record.

The takeaway: OCR makes a document's text searchable; when the job is to extract fields, ask for field-level extraction and validation as well.

Data quality dimensions and why they decide outcomes

A model learns whatever its training records say, mistakes included. AWS states that a machine learning model's performance depends on the data quality used for training, and that missing values, inconsistent data entries, and noise can significantly degrade model accuracy[5]; using poor training datasets can result in erroneous predictions in deployed models[30]. This section covers the dimensions used to describe data quality and what to do when one fails. The AWS AIB-C01 exam guide lists data strategies, data ownership, and data sharing frameworks[24] under 'Task 4.2: Establish data and infrastructure foundations for AI'; see Establish data and infrastructure foundations for AI.

The dimensions

AWS guidance describes overall data quality through facets such as consistency, completeness, correctness, accuracy, validity, and timeliness[31] and treats two of them together as the degree of data accuracy relative to real-world entities (correctness and accuracy)[31], so the Accuracy row below covers correctness too. Data-quality rules also check uniqueness, the share of unique values, which occur exactly once[32]. Each dimension catches a different defect, so a dataset can pass one and fail another.

Dimension The question it asks A defect it catches
Accuracy Do recorded values reflect reality? A customer address that is simply wrong
Completeness Is the required information present? Missing income on loan applications
Timeliness Is the data current enough for this decision? Last year's prices feeding today's forecast
Consistency Does the same business fact mean and look the same across records and sources? Two stores recording returns differently
Validity Do values follow the required format or range? A date written in the wrong format
Uniqueness Is each entity or event recorded only once? The same customer entered twice

Passing one dimension's check does not establish another's, as these pairs show:

  • Accuracy versus timeliness. An old record can be perfectly accurate for its date and still unsuitable for a decision that needs current information.
  • Validity versus accuracy. Validity rules restrict values within a specific range, format, or predefined set[33], but a value can pass a format check and still be wrong: a correctly formatted phone number can belong to someone else.
  • Uniqueness versus completeness. Two copies of the same customer can both be accurate and have every required field filled in, so a completeness check passes them, yet together they inflate the customer count. Ask whether repeated records are genuinely separate observations before treating record volume as the size of the business population.

Fix the source before retraining

When predictions rest on inaccurate or missing records, correct the source data and reassess whether it suits the use before retraining. A more sophisticated model trained on contradictory customer records still faces that data-quality risk, and adding more examples from the same faulty process can enlarge the problem rather than supplying better evidence. Data cleansing means modifying and removing incorrect and incomplete data fields, identifying and removing duplicate information, and correcting formatting, missing values, and spelling errors[30]. When stores record the same business event differently, standardize how the data is defined, collected, and checked at the source; making the final AI reports look uniform changes the presentation, not the comparability of the underlying measurements.

Profiling finds issues; experts decide what they mean

Data profiling analyzes the statistical properties, distributions, and patterns within a dataset to identify anomalies, missing values, outliers, and other quality issues[34] before training. It needs people as well as tools: subject matter experts should interpret these findings to determine appropriate actions[34], and AWS lists failing to document data quality issues and their resolutions[34] as an anti-pattern. An unusually large transaction may be a typing error or a legitimate business event; deleting every large transaction before training a fraud model may discard the very cases the model needs to learn. Set quality expectations, decide each remediation with an expert rather than blindly accepting an automated suggestion, and record why.

The takeaway: name the failing dimension, fix it where the data is produced, and have business experts judge what profiling flags before anything is removed.

Representative data, label quality, and synthetic data

Volume is not coverage. This section covers three properties of training evidence that even a large dataset can lack: representation of the right people and situations, trustworthy labels, and synthetic examples that behave like the real thing.

Representative data

Training evidence has to look like the setting where the model will work. AWS guidance is to consider whether your datasets accurately reflect the real-world conditions where your system will be used, and to gather examples that represent your users[35]. Imbalance has a predictable effect: when some classes are much more frequent, the model can perform well on the majority class while failing to predict the minority class accurately[5]. A strong overall score can therefore hide weak performance for an underrepresented group, a rare outcome, or a missing business context. Collecting more of the already dominant customer segment adds volume without filling the gap; seek relevant examples of what is missing and record what you included and excluded from your datasets, so the limitations are known[35].

Label quality

A label tells a supervised learning system which answer to learn, so inconsistent or biased labels teach the wrong associations. For human labeling, AWS recommends training processes that teach consistent labeling, measuring how well different annotators agree with each other, checking for unwanted biases, and simple tests using examples with known correct answers[36], along with processes for fixing labels that do not meet your quality standards[36]. Machine-generated labels need the same scrutiny: check synthetic and model-generated labels against human judgment, and test whether they work well for underrepresented groups and edge cases where automated systems may fail[36]. Automation changes how labels are produced, not the need to prove they are reliable.

Synthetic data

Synthetic data is data generated by an algorithm rather than observed from real-world measurements[37], and it can supplement scarce examples. Its value depends on realism, not volume. AWS guidance is to verify that synthetic data keeps the statistical properties you need, does not exclude important edge cases or rare scenarios, and preserves key relationships in the data[38]; to search for bias in the synthetic data generation process[38]; to have domain experts evaluate whether synthetic examples capture the key phenomena and scenarios[38]; and to document when synthetic data should and should not be used as a substitute for real data[38]. Replacing a handful of rare real incidents with many generic generated ones can erase the unusual relationships the model most needs to recognize.

The takeaway: judge training evidence by coverage, label reliability, and realism, and document its limits; a bigger dataset with the same gaps is not better evidence.

Training, validation, and test sets

A model's training score says how well it learned the examples it was given, not how it will perform on the next customer. This section covers how teams separate the evidence so that an approval decision rests on examples the model has not already seen, and the ways that separation breaks.

Three sets, three jobs

AWS guidance is to split the data into at least three sets: training, validation, and testing[39].

A business approval should rely on the test result, because those examples were neither used to fit the model nor consulted again and again while refining it. Checking every development revision against the test set quietly turns it into a second validation set, and the independent assessment is lost. The same rule applies to prompt engineering: AWS recommends that you split a sample dataset into a development set for trying prompt changes and a hold-out test set to see if your prompt modifications generalize[40]. That separation tells a reusable improvement apart from a result tailored to familiar examples. The figure below traces the whole sequence, ending with the use-context check described at the end of this section.

Data leakage

Data leakage happens when your model gets data that it should not have access to, such as data samples that were used for training, or information that will not be available when the model is deployed in production[39]. Leakage makes results look better than reality, in two common ways:

When a result looks impressive, ask two questions: was every input available at the real decision point, and are the evaluation examples genuinely separate from the training examples?

Overfitting and underfitting

The gap between training and test results is the diagnostic. Overfit models perform well on the training set but not on the test set; underfit models produce inaccurate results on both the training data and the test set[41]. An overfit model memorized training-specific detail or noise; an underfit model never learned the relevant relationship. AWS identifies overfitting by a high error rate in the testing data and a large gap between accuracy in the training data and test data[41]. In AWS's terms, underfit models exhibit high bias and overfit models exhibit high variance[41]: bias here is the error of a model that never learned the relationship, and variance is performance that holds on the training set but not on new data. Neither is the unfair treatment of groups discussed under representative data and the fairness dimension. AWS notes that for a sufficiently complex model more model training leads to less bias, but variance can increase[41]. Longer training or a higher training score is therefore not automatically better. The two patterns need different technical fixes, and the business question is always whether the model generalizes to new examples.

Check the use context

An aggregate test score covers the population the test set came from, not every place the model will be used. AWS gives two examples. A credit model trained on data for a whole country should, when the bank expands into one city, be evaluated on test data for that city slice as well[39]; a slice is a subset of evaluation data for a particular group, place, or segment. And a grocery demand model trained on 2019 data and tested on early 2020 data would probably score well on the testing set but generate poor results in production because consumer patterns changed significantly during the COVID-19 pandemic[39], which is why AWS suggests an additional recent test set as a safeguard for model approval. After a major business shift, ask for evaluation on suitably recent examples.

The takeaway: approve on held-out, leak-free evidence that covers the groups, places, and recent conditions where the model will run; a single impressive aggregate score is not that evidence.

Training setFit the modelValidation setTune and chooseTest set (held out)Assess onceSlices, recent dataCheck use contextApprove or reject
Model evaluation sequence: fit on the training set, tune on the validation set, assess once on the held-out test set, then check slices and recent data

ISO/IEC 22989, 23053, and 42001

Three ISO/IEC standards come up in AI conversations, and each answers a different question. This section covers what each one is for, so you can tell a vocabulary standard from a system framework and from a management-system standard. The AWS AIB-C01 exam guide lists governance work under 'Task 3.2: Establish AI governance structures and ensure regulatory compliance'[42]; see Establish AI Governance and Regulatory Compliance.

Standard Kind of document The question it answers
ISO/IEC 22989 Concepts and terminology What do our AI terms mean?
ISO/IEC 23053 Framework for AI systems that use ML What are the parts of an ML-based system, and how do they relate?
ISO/IEC 42001 Management-system requirements How does the organization manage its AI?

A management system is not a model check

ISO itself draws the contrast: 22989 establishes terminology and 23053 a framework for describing ML systems, while ISO/IEC 42001 is a management system standard that puts in place policies and procedures for the sound governance of an organization in relation to AI, using the Plan-Do-Check-Act methodology, rather than looking at the details of specific AI applications[45]. Plan-Do-Check-Act is a repeating cycle of four steps (plan, do, check, act) that serves the standard's requirement for establishing, implementing, maintaining and continually improving[45] the management system. Two contrasts follow from it. Reaching for 42001 to settle a terminology dispute picks a management-system standard over the dedicated vocabulary standard. And a model benchmark report is not an AI management system: it measures one application's outputs, while 42001 concerns the organization's coordinated policies, objectives, and improvement processes. An organization should consider both kinds of evidence in light of its AI role and use case.

The takeaway: 22989 for the words, 23053 for the parts of an ML system, 42001 for how the organization manages AI.

NIST AI RMF, AWS CAF for AI, and AWS responsible AI dimensions

Beyond the ISO standards, three more frameworks give business and technical teams a shared vocabulary: one for risk, one for adoption, and one for responsible AI. The AWS AIB-C01 exam guide lists Task 3.1, 'Apply responsible AI principles to business decisions'[42] and Task 4.1, 'Assess AI business readiness and maturity'[24] separately; see Apply Responsible AI Principles to Business Decisions and Assess AI business readiness and maturity.

NIST AI Risk Management Framework

The NIST AI Risk Management Framework (AI RMF) is intended to be voluntary, rights-preserving, non-sector-specific, and use-case agnostic[46], offered to organizations that design, develop, deploy, or use AI systems. Its Core is composed of four functions: Govern, Map, Measure, and Manage[46]:

Govern is not a one-time first step: governance is designed to be a cross-cutting function to inform and be infused throughout the other three functions[46], and framework users may apply these functions as best suits their needs[46], tailoring them to their application and context. Because the framework is voluntary guidance, adopting it is not regulatory permission to deploy; applicable legal requirements still apply on their own terms.

AWS Cloud Adoption Framework for AI

The AWS Cloud Adoption Framework for AI (AWS CAF for AI) treats AI adoption as an organizational capability challenge. Adoption depends on foundational capabilities in business, people, governance, platform, security, and operations[47], the framework's six perspectives. The word governance names three elements here, each defined in its own framework: NIST's cross-cutting Govern function, this CAF for AI perspective, and an AWS responsible AI dimension below; security is likewise a CAF perspective and part of the privacy and security dimension. A capability here is an organizational ability to use processes to deploy resources (such as people, technology, and other tangible or intangible assets) to achieve an outcome[48]. The perspectives connect business outcomes and workforce capability with oversight, enabling technology, protection, and reliable operation, which gives business and technical stakeholders one structure for discussing gaps. An assessment limited to the Platform perspective leaves the other five perspectives unassessed, so on its own it cannot establish overall AI readiness.

AWS responsible AI dimensions

AWS defines responsible AI using a core set of dimensions[7], each a distinct concern:

Dimension AWS definition
Fairness Considering impacts on different groups of stakeholders
Explainability Understanding and evaluating system outputs
Privacy and security Appropriately obtaining, using, and protecting data and models
Safety Preventing harmful system output and misuse
Controllability Having mechanisms to monitor and steer AI system behavior
Veracity and robustness Achieving correct system outputs, even with unexpected or adversarial inputs
Governance Incorporating best practices into the AI supply chain, including providers and deployers
Transparency Enabling stakeholders to make informed choices about their engagement with an AI system

Distinguish transparency from explainability. Transparency is disclosure that lets people decide how to engage with a system; explainability is the ability to understand and evaluate its outputs. A transparency disclosure alone therefore does not establish that individual decisions are understandable. More generally, strong results on one dimension, such as veracity, do not by themselves establish adequate performance on the others, so no single quality score can stand in for all eight.

The takeaway: the NIST AI RMF organizes risk work, AWS CAF for AI organizes adoption capabilities, and the responsible AI dimensions name the separate concerns a trustworthy system has to meet.

Matching business situations to core AI concepts

The AWS AIB-C01 exam guide asks candidates to recognize and explain fundamental AI concepts in business contexts[1]. The table below gives illustrative business situations, the concept each one points to, and a neighboring concept or misreading that sounds right but does not apply, with the mechanism that rules it out.

Business situation Concept that applies Neighboring misreading and why it fails
A system classifies or recommends but writes nothing AI or ML without generation Ruling it out as AI; generation is one kind of AI, not the definition
A new text task and no model yet Reusing a pretrained foundation model Commissioning a model from scratch; foundation models are pretrained for reuse
An archive of prediction requests keeps growing Inference does not update the model Calling the archive retraining; storing requests changes no parameters
Call recordings, and the goal is customer mood Speech recognition, then sentiment analysis Transcription alone; it outputs words, not their meaning
A numerical revenue forecast is needed Supervised regression on known outcomes Customer segmentation; it discovers groups, not a numeric target
An unusual transaction is flagged Anomaly detection, a signal to investigate Treating it as confirmed fraud; not all anomalies are fraud
Experts cannot label every document Self-supervised or semi-supervised learning Requiring full manual labels before any pretraining
Reward set on immediate clicks, goal is retention Reinforcement learning reward design Assuming the system pursues the real goal; it pursues what the reward measures
Customer ID and product-category fields Structured data Calling all text unstructured; schema-defined text fields are structured
Claim photos sent to a text-only model Modality fit Judging visual damage from text that never described it
Invoices are now searchable OCR, not field extraction Accepting searchability as proof that payment fields were captured
Duplicate customer records Uniqueness Relying on a completeness check; duplicates can have every field filled
Weak results for a minority segment Representative data Adding more majority-segment data; volume does not fill the gap
The test set is used on every revision Independent testing Calling the final score an independent assessment
Settlement data in an initial claim-risk model Data leakage Trusting the score; it uses information known only later
Strong national score, new city Slice evaluation Accepting the aggregate; local performance is unexamined
Teams dispute what AI terms mean ISO/IEC 22989 ISO/IEC 42001, a management-system standard
NIST AI RMF adopted before launch Voluntary risk guidance Treating adoption as regulatory permission to deploy
Only platform capacity reviewed for readiness AWS CAF for AI perspectives Treating one perspective as the whole readiness assessment
A model disclosure is published Transparency Treating it as explainability of individual decisions

The takeaway: name the mechanism behind each situation (what the system learns from, what form the data takes, what the evidence proves, what the framework is for) before choosing between neighboring concepts.

AI vs machine learning vs generative AI

QuestionArtificial intelligence (AI)Machine learning (ML)Generative AI
What it isThe broad category of systems that perceive, reason, and predictThe branch of AI that learns patterns from dataAI that produces new content from learned patterns
Where it sitsThe outer categoryInside AI; deep learning is a specialized form of MLInside ML; overlaps deep learning, and modern forms use deep learning
Typical outputA decision, a recognition, or an actionA prediction: a category, a number, or a groupNew text, images, audio, or code
Business exampleSmart assistants, robotic vacuums, self-driving carsClassifying a transaction as fraudulent or genuineDrafting a reply to a customer email
Must it generate content?NoNoYes, generation is what defines it

Decision tree

Learning fromactions and rewards?ReinforcementlearningYesNoFew labels plusmany unlabeled?Semi-supervisedYesNoKnown outcomesare categories?Supervised:classificationYesNoKnown outcomesare numbers?Supervised:regressionYesNoNo labels: targetsderived from data?Self-supervisedYesNoUnsupervisedlearning

Sharp facts the exam loves — give these one last read before exam day.

Cheat sheet

Sharp facts the exam loves — scan these before test day.

AI, machine learning, and generative AI describe related but different capabilities

Artificial intelligence is the broad category of systems performing tasks such as perception, reasoning, and prediction; machine learning is an approach within AI that learns patterns from data. Deep learning is a form of ML using multilayer neural networks, and modern generative AI uses learned patterns to produce content such as text, images, or audio. A system can classify transactions or recommend products without generating new content, while a generative model can also perform tasks such as classification when prompted.

Trap Using content generation as the defining requirement for every AI application, which excludes predictive and recognition capabilities.

4 questions test this
An algorithm is a method, while a trained model contains learned relationships

A learning algorithm is the procedure used to discover patterns, whereas a trained model is the resulting representation of those patterns and learned parameter values. The same learning procedure can produce different models when trained on different business data. When discussing an AI proposal, distinguish changing the learning method from updating the learned model with new training evidence.

5 questions test this
Training learns patterns, while inference applies a model to a new request

Training uses examples to learn model parameters; inference uses an already trained model to produce a prediction or response for an input. Forecasting next month's demand or generating a reply is inference, even when the input contains information the model has not previously encountered. Ordinary inference does not itself update the model's trained parameters; learning from newly collected examples requires an explicit training or updating process.

Trap Treating a growing archive of prediction requests as automatic retraining, which confuses collecting examples with updating model parameters.

5 questions test this
Foundation models provide broadly reusable capabilities rather than one narrowly trained task

A foundation model is pretrained on broad, diverse data and can be adapted or prompted for multiple downstream tasks. This allows a business to reuse an existing capability instead of funding training from scratch for every application. Broad pretraining does not establish that the model knows a company's private information or meets its specific quality requirements, so business-specific evaluation and, where necessary, adaptation remain important.

Trap Commissioning a new model from scratch for each text task, which overlooks the reusable capabilities of pretrained foundation models.

4 questions test this
Language, vision, and speech capabilities address different forms of business information

Natural language processing interprets or generates human language, supporting sentiment analysis, intent recognition, and translation. Computer vision extracts information from images or video, supporting visual inspection and object recognition. Speech recognition converts spoken words into text, which can then be analyzed for meaning; transcribing a call and determining customer sentiment are different tasks that can be combined.

Trap Using speech transcription alone to measure customer sentiment, which produces words rather than an interpretation of their meaning.

4 questions test this
A large language model generates language by predicting successive tokens

A large language model (LLM) is a model trained on extensive language data to learn patterns that support understanding and generating text. A generative LLM produces a response by predicting successive tokens from the supplied context and the tokens already generated. LLMs are language-focused members of the broader foundation-model category, which also includes models for non-language content such as images; foundation model and LLM are therefore not interchangeable names.

A learned prediction is an estimate rather than a guaranteed outcome

A learned prediction is a probabilistic estimate based on patterns, not a promise that the predicted event will occur. A demand forecast can therefore be useful even though actual demand differs from its predicted value. Generative responses can also vary across repeated requests with the same prompt because generation can select among possible next tokens; identical wording is not guaranteed simply because the request is unchanged.

4 questions test this
Broad task capability does not by itself establish artificial general intelligence

Artificial general intelligence (AGI) denotes the theoretical goal of generalized human-level cognitive ability, including learning and solving problems across domains beyond the tasks a system was developed for. Task-bounded AI operates within capability limits even when it performs many useful activities. Reusing a foundation model for several business tasks or letting an agent complete a workflow autonomously does not by itself demonstrate AGI.

Recommendation engines select relevant items rather than merely personalize wording

A recommendation engine uses evidence such as customer interactions, preferences, and item information to select or rank relevant products or content. Purchase history and product descriptions can help determine which existing items to show a customer. Generating a personalized message about an item is a different capability: it creates wording rather than performing the selection or ranking, although a business experience can combine both.

3 questions test this
Amazon Bedrock, Amazon SageMaker AI, and Amazon Quick serve different business capability needs

Amazon Bedrock provides managed access to foundation models and capabilities for creating generative AI applications and agents. Amazon SageMaker AI provides a managed environment for technical teams to develop, customize, train, deploy, and manage models across the custom-ML lifecycle. Amazon Quick is a ready-to-use business AI service combining assistance grounded in connected data, analytics, and workflow automation. These categories distinguish application-building capabilities, a model-development environment, and business-facing assistance; overlapping features do not make the offerings interchangeable.

4 questions test this
Supervised learning uses known outcomes to learn categorical or numerical predictions

Supervised learning learns from inputs paired with known target outcomes, such as historical transactions marked fraudulent or genuine. Classification predicts a category, including two-category and multiple-category outcomes; regression predicts a numerical value such as a selling price. A business must identify both the outcome it wants predicted and whether reliable historical examples of that outcome exist.

Trap Using customer segmentation as the training objective for an exact revenue forecast, which discovers groups rather than learning the required numerical target.

4 questions test this
Unsupervised learning discovers relationships without examples of a required answer

Unsupervised learning finds patterns in data without supplied target labels. Clustering groups similar customers or documents, while association discovery identifies relationships such as products frequently purchased together. These findings support exploration, but the resulting groups need business interpretation rather than being treated as predefined outcomes the system was taught to predict.

Trap Treating newly discovered customer clusters as verified churn labels, which substitutes similarity groups for observed business outcomes.

4 questions test this
Limited manual labels do not mean all learning must stop

Semi-supervised learning uses a small labeled dataset together with a larger unlabeled dataset, which can be useful when expert labeling is costly. Self-supervised learning derives learning targets from the data itself, as in learning to predict missing or subsequent text, and is widely used in foundation-model pretraining. These approaches differ from collecting a human-provided correct answer for every training example; neither removes the need to evaluate results against the intended business task.

Trap Requiring experts to label every document before any pretraining can begin, which overlooks learning signals obtainable from unlabeled data.

4 questions test this
Reinforcement learning learns actions from rewards rather than paired correct answers

Reinforcement learning improves a strategy through actions and feedback expressed as rewards, with the aim of improving cumulative outcomes over time. A locally attractive action can be less useful than a sequence that earns a better long-term result. Business leaders must understand what the reward encourages, because a system can learn to pursue the rewarded outcome even when that outcome is a poor proxy for the real business goal.

Trap Rewarding only immediate engagement for a long-term retention goal, which teaches the system to optimize a different outcome.

3 questions test this
Anomaly detection identifies unusual behavior rather than proving its cause

Anomaly detection identifies observations that differ from expected patterns, which can help surface unusual transactions or equipment behavior when exhaustive examples of failures are unavailable. An unusual observation is a signal for investigation, not by itself proof of fraud or a particular equipment fault. A known-outcome classifier instead learns the categories represented in its labeled examples, so the two capabilities answer different business questions.

Trap Treating an unusual transaction as a confirmed fraud label, which turns a deviation signal into an unverified conclusion.

3 questions test this
Data structure depends on its schema, not whether it contains numbers or words

Structured data follows a predefined schema, such as transaction rows with named fields for customer, date, and amount. Unstructured data includes narrative documents, images, and recordings whose meaning is not organized as fixed record fields. Short text fields can be structured, and a digital document can remain unstructured; the distinction helps determine whether a business needs record analysis or content understanding.

Trap Classifying all text as unstructured, which ignores schema-defined fields such as customer identifiers and product categories.

4 questions test this
Metadata organizes content without making all of its meaning structured

Semi-structured information combines organizational cues with content that does not fit a rigid table, such as a media collection with dates and topic tags. Those tags can support filtering and discovery, while understanding what a recording actually says still requires analysis of its content. A business should distinguish searching known metadata from extracting new meaning from the underlying material.

Trap Using document filenames as substitutes for analyzing contract obligations, which searches labels rather than the terms inside the documents.

4 questions test this
An AI solution must support the information modalities the business needs it to use

A modality is a type of information, such as text, images, audio, or video; a multimodal capability can process more than one type. A text-only capability cannot directly interpret visual evidence in a product photograph or a scanned chart merely because a user mentions it. For a mixed-information task, establish which modalities must be understood and whether any required conversion preserves the evidence needed for the decision.

Trap Using a text-only summary to judge visual damage that was never described in text, which removes the evidence needed for the assessment.

4 questions test this
Recognizing text and extracting business fields are different document-processing capabilities

Optical character recognition converts an image of text into machine-readable text. Intelligent document processing goes further by extracting, classifying, and validating business information such as invoice numbers, totals, and payment terms for downstream workflows. When the goal is to populate a business record rather than simply make a document searchable, assess field-level extraction and validation as well as text recognition.

Trap Accepting a searchable invoice as proof that its payment fields were correctly captured, which confuses text recognition with business-data extraction.

5 questions test this
Incorrect and missing records are data-quality problems before they are model problems

When predictions rely on inaccurate records or missing business information, prioritize correcting the source data and assessing its suitability before retraining. Accuracy means that recorded values reflect reality, while completeness concerns whether required information is present. Timeliness concerns currency and relevance, so an accurate old record may still be unsuitable for a decision that needs current information. Adding more examples from the same faulty process can enlarge the problem rather than supply better learning evidence.

Trap Funding a more sophisticated model for contradictory customer records, which leaves the incorrect learning evidence unchanged.

5 questions test this
Consistent definitions and valid values make data comparable across business sources

Data consistency requires equivalent business information to have compatible meanings and representations across records and sources. Validity checks whether values follow required formats or acceptable ranges; a value can pass a format check and still be factually wrong. When stores record the same business event differently, standardize collection definitions and quality checks rather than merely standardizing the AI's final reports.

Trap Standardizing forecast report layouts to reconcile incompatible store inputs, which changes presentation without making the underlying measurements comparable.

4 questions test this
Large historical datasets can still omit the people and situations that matter

Training evidence must represent the intended users and operating conditions, not simply contain many records. Underrepresented populations, rare outcomes, or missing business contexts can lead to uneven performance even when overall results look strong. Seek relevant coverage of those gaps and document exclusions; collecting more of the already dominant examples does not necessarily address them.

Trap Expanding only the majority customer segment to fix weak minority coverage, which increases volume without filling the missing experience.

4 questions test this
Training labels require quality control whether people or AI produced them

A label tells a supervised-learning system what answer to learn, so inconsistent or biased labels can teach the wrong associations. Require clear labeling guidance, checks against known examples, and review of disagreements by appropriate domain experts. Machine-generated labels also need validation against human judgment, especially for underrepresented groups and difficult cases; automation changes how labels are produced, not the need to establish their reliability.

Trap Treating agreement among automatically generated labels as independent proof of correctness, which can reproduce the same underlying labeling error.

4 questions test this
Synthetic examples are useful only when they preserve the business phenomena being learned

Synthetic or augmented data can supplement scarce examples, but its usefulness depends on realism, relevant relationships, and coverage of important edge cases. Require domain validation and checks for bias rather than accepting generated volume as evidence of quality. Document where synthetic examples can substitute for real observations and where their limitations make real data necessary.

Trap Replacing rare real incidents with generic generated examples, which may remove the unusual relationships the system needs to recognize.

4 questions test this
Data profiling reveals issues, but business expertise determines what they mean

Data profiling examines characteristics such as missing values, distributions, unusual observations, and inconsistent categories before training. Subject matter experts must interpret those findings because an unusual value may be either a recording error or a valid business event. Establish quality expectations and record the rationale for remediation instead of blindly accepting an automated suggestion or removing every unusual case.

Trap Removing every unusually large transaction before fraud training, which may discard legitimate examples of the events being investigated.

4 questions test this
Duplicate records can distort evidence even when every field is correct

Uniqueness is the data-quality dimension concerned with avoiding unintended duplicate records for the same business entity or event. Recording the same customer twice can inflate customer counts even when both records are accurate and complete. Assess whether repeated records represent genuinely separate observations before accepting record volume as evidence of the size of the business population.

Trap Using a required-field completeness check as the sole acceptance criterion for customer counts, because duplicate records can contain every required field.

Training, validation, and testing provide different kinds of evidence

Training data teaches the model, validation data supports development decisions, and a separate test set assesses performance after those decisions are made. A business approval should rely on examples not used to fit or repeatedly refine the model. The same independence principle applies to prompt engineering: use development cases to refine instructions and held-out cases to verify the final prompt. This distinguishes a reusable improvement from a result tailored to familiar examples.

Trap Using the final test set for every development revision, which makes the claimed independent assessment part of the development process.

3 questions test this
Information unavailable at decision time must not inflate historical evaluation results

Data leakage occurs when learning or evaluation uses information that would not legitimately be available for the real prediction. Examples include later business outcomes present in historical records and duplicate examples appearing across training and testing. When reviewing impressive results, ask whether the evidence reflects the information available at the actual decision point and whether evaluation examples are genuinely separate.

Trap Including completed-claim settlement information in an initial claim-risk prediction, which supplies knowledge the business would only obtain later.

2 questions test this
Training success must be compared with performance on unfamiliar examples

Overfitting occurs when a model learns training-specific detail or noise and performs well on training examples but poorly on new examples. Underfitting means the model has not learned the relevant relationship and performs poorly on both training and test examples. These patterns call for different technical investigations; business leaders should request evidence of generalization rather than assuming longer training or higher training accuracy is always better.

Trap Demanding more training solely to maximize an already strong training score, which can deepen memorization instead of improving generalization.

4 questions test this
Historical evaluation must address the specific context in which the model will be used

A national or historical average test score does not establish performance for a particular city, customer group, or newly changed market. Request evaluation on relevant subsets and, after a major business shift, suitably recent examples before relying on the broader result. The decision is whether the evaluation evidence supports the intended application, not whether a single aggregate score is impressive.

Trap Accepting a national average test result as sufficient evidence for entry into a poorly represented city, which leaves local performance unexamined.

3 questions test this
ISO/IEC 22989 and ISO/IEC 23053 support different levels of shared AI understanding

ISO/IEC 22989 establishes AI concepts and terminology for communication among diverse stakeholders. ISO/IEC 23053 provides a framework for describing the components and functions of AI systems using machine learning, including deep learning. Use shared vocabulary to resolve inconsistent terminology and the ML-system framework to explain how system elements relate; neither serves the same purpose as an organizational AI management system.

Trap Using ISO/IEC 42001 as the primary glossary for a terminology dispute, which selects a management-system standard rather than the dedicated vocabulary standard.

4 questions test this
ISO/IEC 42001 addresses organizational AI management rather than an individual model's accuracy

ISO/IEC 42001 specifies requirements for establishing, maintaining, and continually improving an AI management system. It applies to organizations that provide or use AI, not only those that develop models, and uses a Plan-Do-Check-Act approach to managing risks and opportunities. Its focus is coordinated policies, objectives, and processes across the organization rather than a substitute for evaluating an individual AI application's outputs.

Trap Using a model benchmark report as the organization's AI management system, which measures outputs without establishing management policies and improvement processes.

3 questions test this
The NIST AI RMF provides a voluntary structure for managing AI risks across the lifecycle

The NIST AI Risk Management Framework is voluntary, use-case agnostic guidance for incorporating trustworthiness into AI design, development, use, and evaluation. Its core functions are Govern, Map, Measure, and Manage: establish governance, understand context and risks, assess those risks, and prioritize responses. Govern is cross-cutting rather than a one-time first step; organizations tailor the risk-management outcomes and approaches to their application and context.

Trap Treating adoption of the NIST AI RMF as regulatory permission to deploy, which confuses voluntary risk guidance with applicable legal requirements.

3 questions test this
AWS CAF for AI treats adoption as an organizational capability challenge

AWS CAF for AI applies six perspectives to AI adoption: Business, People, Governance, Platform, Security, and Operations. These connect business outcomes and workforce capability with oversight, enabling technology, protection, and reliable operation. A technology assessment alone therefore cannot establish overall AI readiness; the perspectives provide a common way for business and technical stakeholders to discuss gaps without prescribing one executive owner for every organization.

Trap Using platform capacity as a complete AI-readiness assessment, which leaves people, governance, and other organizational capabilities unassessed.

3 questions test this
AWS responsible AI dimensions describe distinct concerns that a single quality score cannot replace

AWS describes responsible AI through fairness, explainability, privacy and security, safety, controllability, veracity and robustness, governance, and transparency. Explainability concerns understanding and evaluating outputs, while transparency enables informed stakeholder choices; controllability concerns mechanisms to monitor and steer behavior. Fairness considers impacts on different groups, and veracity and robustness address correct outputs even with unexpected inputs, so strong performance on one dimension does not establish all the others.

Trap Using a transparency disclosure as evidence that individual decisions are understandable, which substitutes stakeholder information for output explainability.

3 questions test this

Also tested in

References

  1. https://docs.aws.amazon.com/aws-certification/latest/ai-business-strategist-01/ai-business-strategist-01-domain1.html
  2. https://aws.amazon.com/what-is/generative-ai/
  3. https://aws.amazon.com/what-is/foundation-models/
  4. https://docs.aws.amazon.com/bedrock/latest/userguide/key-definitions.html
  5. https://aws.amazon.com/what-is/machine-learning/
  6. https://aws.amazon.com/what-is/large-language-model/
  7. https://aws.amazon.com/ai/responsible-ai/
  8. https://aws.amazon.com/what-is/artificial-general-intelligence/
  9. https://aws.amazon.com/what-is/inferencing/
  10. https://docs.aws.amazon.com/bedrock/latest/userguide/inference-parameters.html
  11. https://aws.amazon.com/what-is/reinforcement-learning/
  12. https://docs.aws.amazon.com/machine-learning/latest/dg/types-of-ml-models.html
  13. https://aws.amazon.com/what-is/anomaly-detection/
  14. https://aws.amazon.com/blogs/machine-learning/overcome-the-machine-learning-cold-start-challenge-in-fraud-detection-using-amazon-fraud-detector/
  15. https://docs.aws.amazon.com/aws-certification/latest/ai-business-strategist-01/ai-business-strategist-01.html
  16. https://aws.amazon.com/what-is/nlp/
  17. https://aws.amazon.com/what-is/computer-vision/
  18. https://aws.amazon.com/what-is/speech-to-text/
  19. https://docs.aws.amazon.com/personalize/latest/dg/what-is-personalize.html
  20. https://aws.amazon.com/bedrock/faqs/
  21. https://docs.aws.amazon.com/sagemaker/latest/dg/whatis.html
  22. https://docs.aws.amazon.com/quick/latest/userguide/what-is.html
  23. https://aws.amazon.com/what-is/structured-data/
  24. https://docs.aws.amazon.com/aws-certification/latest/ai-business-strategist-01/ai-business-strategist-01-domain4.html
  25. https://aws.amazon.com/what-is/data-silos/
  26. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/postgresql-ml.html
  27. https://aws.amazon.com/blogs/machine-learning/generative-ai-and-multi-modal-agents-in-aws-the-key-to-unlocking-new-value-in-financial-markets/
  28. https://aws.amazon.com/what-is/ocr/
  29. https://aws.amazon.com/what-is/intelligent-document-processing/
  30. https://aws.amazon.com/what-is/data-cleansing/
  31. https://docs.aws.amazon.com/wellarchitected/latest/devops-guidance/metrics-for-data-lifecycle-management.html
  32. https://docs.aws.amazon.com/glue/latest/dg/dqdl-rule-types-Uniqueness.html
  33. https://aws.amazon.com/what-is/data-integrity/
  34. https://docs.aws.amazon.com/wellarchitected/latest/machine-learning-lens/mlops03-bp01.html
  35. https://docs.aws.amazon.com/wellarchitected/latest/responsible-ai-lens/raidp02-bp01.html
  36. https://docs.aws.amazon.com/wellarchitected/latest/responsible-ai-lens/raidp02-bp03.html
  37. https://aws.amazon.com/what-is/synthetic-data/
  38. https://docs.aws.amazon.com/wellarchitected/latest/responsible-ai-lens/raidp02-bp04.html
  39. https://docs.aws.amazon.com/prescriptive-guidance/latest/ml-operations-planning/splits-leakage.html
  40. https://docs.aws.amazon.com/bedrock/latest/userguide/design-a-prompt.html
  41. https://aws.amazon.com/what-is/overfitting/
  42. https://docs.aws.amazon.com/aws-certification/latest/ai-business-strategist-01/ai-business-strategist-01-domain3.html
  43. https://committee.iso.org/standard/74296.html
  44. https://committee.iso.org/standard/74438.html
  45. https://committee.iso.org/standard/42001
  46. https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf
  47. https://docs.aws.amazon.com/whitepapers/latest/aws-caf-for-ai/ai-cloud-transformation-value-chain.html
  48. https://docs.aws.amazon.com/pdfs/whitepapers/latest/aws-caf-for-ai/aws-caf-for-ai.pdf