AIB-C01 (beta) · FOUNDATIONAL PRACTICE EXAM

AWS Certified AI Business Strategist (AIB-C01 (beta)) Free Practice Exam and Practice Test

848 AIB-C01 (beta) practice questions, updated , in an exam simulator that mirrors the real exam: its domains, its question types and its timing, with an explanation for every answer.

FREE PRACTICE EXAM20 questions · no sign-upStart the free practice exam
The AIB-C01 exambeta
Questions65
Duration130 min
Passing score70%
Domains4
Beta startSep 29, 2026 Last dayNot announced
All exam dates →
COURSEInteractive AIB-C01 (beta) course221 lessons built around exercises, no videos. See the course →EXAM GUIDEOfficial AIB-C01 (beta) exam guideThe AWS document listing every domain, task and service in scope.Open the guide →

AIB-C01 (beta) example questions

One example question per domain from the AIB-C01 (beta) question bank, with the correct answer and its explanation. Sign in to the simulator to answer them with all answer options.

AI Fundamentals and Literacy

A pharmaceutical company is reviewing an AI prototype that investigates discrepancies in clinical trial records. Given a discrepancy, the prototype uses one foundation model to choose among approved read-only tools for searching study records and checking laboratory results. It examines each tool's results and decides whether to investigate further or submit an evidence summary to a reviewer. The sequence of checks is not predefined. The prototype cannot modify records, and a person makes the final determination.

Which assessment should the company's AI business strategist make?

Show answerCORRECT ANSWER

The prototype is an AI agent with bounded autonomy because it selects and revises investigative actions while operating within read-only permissions and human decision authority.

The prototype pursues a goal through an action-and-observation cycle: it selects tools, evaluates their results, and decides whether to continue or stop. An agent can use a single model, have read-only permissions, and leave consequential decisions to a person.

AI Strategy and Business Value Creation

A logistics company funded an AI pilot to reduce the time employees spend assigning shipments to carriers. Before the next funding review, the company adopts a transportation management system that automates these assignments. Representative testing confirms that the AI pilot provides no additional time savings, service improvements, or other measurable benefits over the new system. The pilot meets its technical, security, and sustainability requirements, but production integration would require significant additional funding. No alternative business use has been identified. The project sponsor argues that the company should proceed because most pilot development costs have already been incurred. What should the investment review board do?

Show answerCORRECT ANSWER

Terminate the initiative, document the decision against the updated business baseline, and release uncommitted funding.

The funding review should assess whether current evidence justifies the next commitment. The new system has removed the business opportunity, and further integration costs would produce no demonstrated incremental benefit. Past pilot spending is a sunk cost, not a reason to continue.

AI Governance and Responsible AI Leadership

A retail chain is considering purchasing an AI system that assigns employees' weekly shifts. The vendor provides security certifications and test results showing similar average scheduled hours across demographic groups. Store managers expect to accept most schedules without changes. Employee representatives warn that unpredictable schedules could affect childcare arrangements, transportation, and eligibility for benefits. Before committing to the contract and implementation budget, what should the business sponsor require to determine whether adoption is acceptable?

Show answerCORRECT ANSWER

Evaluate the proposed scheduling process with employees and relevant specialists, compare AI and non-AI alternatives, and document potential harms, required controls, acceptance criteria, and accountable risk owners before approving the investment.

This applies an Algorithmic Impact Assessment during business planning. It examines consequences in the actual deployment context, considers whether AI is appropriate, and translates findings into requirements and investment conditions before contractual and architectural commitments are made.

Business Readiness, Leadership, and AI Transformation

A professional services firm wants to improve consultant productivity and can fund one AI development initiative this quarter. Its teams can configure managed AI applications but have limited experience evaluating model outputs and operating custom models.

Leadership approves three investment criteria: strategic contribution (45%), current organizational readiness (35%), and implementation difficulty (20%). Reviewers score each proposal from 1 to 5. Higher scores indicate stronger strategic contribution, greater readiness, and greater implementation difficulty, respectively. The transformation team multiplies each score by its criterion weight and adds the results. A complex custom-model initiative ranks first, narrowly ahead of a managed AI assistant.

All proposals meet mandatory legal and security requirements. Before approving funding, leadership asks for a defensible recommendation that preserves its agreed priorities and establishes a development pathway appropriate to current capabilities.

What should the transformation lead do?

Show answerCORRECT ANSWER

Replace implementation difficulty with a feasibility score in which higher means easier to deliver, recalculate using the approved weights, and use the readiness gaps to identify development steps for subsequent investments.

The current calculation rewards greater implementation difficulty. Reversing that criterion's direction makes higher scores consistently represent more desirable outcomes while preserving leadership's priorities. Recalculating provides a defensible comparison, and the readiness gaps inform capability-building steps for later investments.

Free AIB-C01 (beta) cheat sheets

One PDF per exam domain: the domain's task statements, each drawn with its services and exam traps, then the concepts and core services to remember.

Exam domains

The AIB-C01 (beta) questions are grouped into 4 domains divided into 13 tasks.

AI Fundamentals and Literacy24%
3 tasks · 5 in the free practice exam
  • Describe core AI concepts and define terminology
  • Identify and select appropriate AI solution types
  • Apply GenAI concepts and techniques
AI Strategy and Business Value Creation28%
3 tasks · 5 in the free practice exam
  • Develop AI strategies that align with business objectives
  • Measure and demonstrate AI business value
  • Position AI for competitive advantage
AI Governance and Responsible AI Leadership24%
3 tasks · 5 in the free practice exam
  • Apply responsible AI principles to business decisions
  • Establish AI governance structures and ensure regulatory compliance
  • Identify enterprise AI risks and direct mitigation strategies
Business Readiness, Leadership, and AI Transformation24%
4 tasks · 5 in the free practice exam
  • Assess AI business readiness and maturity
  • Establish data and infrastructure foundations for AI
  • Lead enterprise-wide change and build AI-ready workforce capabilities
  • Scale AI from pilots to enterprise-wide deployments

Exam mode and practice mode

Exam modePractice mode
Questions count651 - 75
Time limit130 minutesOptional, 10 - 200 minutes
Exam scope4 domains with the official questions ratioSelected domains with the official questions ratio
Correct answersAfter exam submissionAfter exam submission or after each answer
Question typesSingle answer and multiple answerSingle answer, multiple answer or all types
Question hintsNeverOptional
Question domainRevealed after exam submissionRevealed after submission or during the exam
Scoring15 of 65 questions do not count towards the resultOfficial AWS method or mathematical mean

See all simulator features on the AWS Exam Simulator page.

Technologies and concepts

A/B Testing

A/B testing compares a baseline with an alternative under similar conditions to determine whether a change improves outcomes. For foundation model applications, it helps engineers evaluate changes to models, prompts, or retrieval configurations using real-world task success, human feedback, safety, latency, and cost rather than relying only on benchmark scores.

Acceptable Use Policy

An Acceptable Use Policy establishes behavioral rules for using cloud infrastructure, including restrictions on unlawful activity, spam, and security abuse. Engineers need to understand these rules to design compliant workloads, prevent misuse, and report suspected abuse through the correct provider channel.

Access Control

Access control turns security requirements into enforceable permissions for people, applications, and cloud services. It limits unauthorized activity while preserving legitimate operations, including the ability to deliver logs, run health checks, and investigate incidents.

ADKAR Model

ADKAR helps leaders identify why people are struggling with a change and select interventions that address the actual barrier. For enterprise AI adoption, it connects communication, employee involvement, practical training, supported experimentation, and ongoing reinforcement rather than treating deployment or course completion as evidence of readiness.

AI Agents

In foundation model applications, an AI agent combines a model with instructions, context, and tools to complete tasks that may require several decisions and interactions with external systems. Agents matter because they can move beyond generating answers to performing business work, but their access, reliability, cost, and degree of autonomy require explicit controls.

AI Guardrails

Guardrails help AI applications produce appropriate responses, protect sensitive information, and avoid unauthorized actions. They combine prompt engineering with independently enforced checks, permissions, and operational monitoring because model instructions alone cannot reliably enforce every requirement.

AI Transparency

AI transparency gives users, engineers, reviewers, and auditors appropriate information about how an AI system is developed, operated, and controlled. It supports informed use, accountability, and compliance by documenting system behavior and responsibilities without unnecessarily exposing private data, intellectual property, or security-sensitive details.

Algorithmic Bias

Algorithmic bias can arise from training data, labels, model objectives, prompts, retrieval sources, and the way an AI system is deployed. It matters because a technically accurate system can still discriminate, expose users to harm, create legal risk, and undermine customer trust.

Algorithmic Fairness

Fairness requires choosing context-appropriate criteria for equitable treatment, examining data and model behavior, and addressing harmful disparities throughout the AI lifecycle. It matters because high overall accuracy can conceal systematically worse outcomes for particular populations, especially in consequential decisions such as hiring, lending, and healthcare.

Algorithmic Impact Assessment

It examines a system’s purpose, affected stakeholders, potential benefits and harms, and the controls needed to make its use acceptable. Starting the assessment during project planning embeds responsible AI into business decisions, architecture, and delivery gates rather than treating governance as a final compliance check.

Allowlisting

Allowlisting establishes a known set of permitted choices rather than attempting to identify every unsafe choice. In cloud and AI governance, it helps prevent unauthorized access and shadow AI by connecting transparent approval decisions to enforceable access controls, documented usage conditions, and ongoing review.

Audit Logging

Audit logging creates an evidence trail showing who or what performed an action, when it occurred, which resource was affected, and what the outcome was. In cloud environments, effective auditing requires selecting complementary log sources and protecting their delivery, retention, and accessibility across accounts, Regions, and workloads.

Automation Bias

Automation bias occurs when people give automated outputs more authority than the available evidence warrants, including accepting incorrect advice or overlooking problems that a system does not flag. As organizations move employees from manual execution to AI oversight, they must preserve meaningful human judgment rather than turn reviewers into routine approvers.

AWS Cloud Adoption Framework (AWS CAF)

AWS CAF organizes cloud transformation around six perspectives: Business, People, Governance, Platform, Security, and Operations. It helps organizations identify readiness gaps, coordinate stakeholders, and prioritize changes that support outcomes such as reduced business risk, improved ESG performance, increased revenue, and greater operational efficiency.

AWS Compliance

Compliance in AWS combines AWS-provided infrastructure assurances with customer responsibilities for data, applications, configurations, and operating procedures. Engineers must identify applicable requirements, verify service and geographic scope, implement controls, and retain evidence rather than assume that using AWS makes a workload compliant.

Benefits of migrating to the AWS Cloud

Cloud migration can improve availability, adapt capacity to demand, accelerate delivery, and provide access to infrastructure near users worldwide. These benefits depend on architecture, cost management, automation, and organizational readiness rather than occurring automatically when workloads move.

Benefits Realization

Benefits realization connects technical delivery to outcomes such as lower operating costs, faster service, increased revenue, or reduced risk. For cloud and AI initiatives, it means establishing a baseline, assigning accountability, measuring actual results, and using that evidence to guide expansion from short-term wins to enterprise-wide adoption.

Bias and Fairness

Bias can enter an AI system through its data, labels, design choices, or operating environment, potentially creating unjustified differences in outcomes. Fairness means evaluating and addressing those differences using criteria appropriate to the application, affected people, and applicable requirements.

Blue-Green Deployment

Two independently deployable environments allow engineers to validate a replacement release while the existing release continues serving users. Switching traffic rather than modifying the live environment reduces deployment disruption and can enable fast rollback, provided data and dependencies remain compatible.

Business Model Canvas

It connects customer needs and revenue opportunities with the activities, resources, partnerships, and costs required to serve them. For AI strategy, it helps distinguish incremental automation from changes that enable new products, customer segments, pricing models, or ways of delivering value.

Capability Maturity Model

Maturity models evaluate organizational capability through defined stages supported by observable evidence, rather than by technology adoption alone. For enterprise AI, they help leaders distinguish isolated experiments from sustainable production adoption and prioritize improvements across strategy, people, data, governance, and operations.

Center of Excellence

A Center of Excellence (CoE) brings business, technical, and control functions together to guide adoption, build workforce capabilities, and establish clear accountability. In cloud and AI initiatives, it helps teams reuse proven approaches while managing security, cost, operational, legal, and ethical risks.

Change Impact Assessment

For cloud and AI initiatives, change impact assessment compares current ways of working with the proposed future state and identifies affected roles, dependencies, risks, and readiness gaps. It provides the evidence for realistic implementation plans, targeted training, and transparent communication about timelines, expected outcomes, and workforce implications.

Change Readiness

Change readiness evaluates whether an organization can turn a proposed transformation into effective, controlled operational change. For cloud-based AI initiatives, it helps identify gaps in leadership alignment, data quality, employee preparedness, infrastructure, and governance before those gaps become delivery failures or business risks.

CI/CD

Continuous integration validates frequently merged code changes through automated builds and tests, while continuous delivery or continuous deployment automates the path toward production. Together, these practices shorten feedback cycles, make releases more repeatable, and reduce the risks associated with large, manually executed changes.

Communities of Practice

A Community of Practice connects people who work in a shared domain across teams, roles, or business units so they can learn from one another and improve how work is done. In cloud and AI transformation, these communities help executive sponsors and local champions turn isolated experiments into reusable practices, workforce capabilities, and sustained organizational change.

Compute

In the cloud, compute provides on-demand CPU, memory, and optional accelerators through virtual machines, containers, and managed execution environments. Choosing an appropriate compute model helps engineers balance performance, cost, scaling behavior, and operational responsibility.

Confidence Scoring

Confidence scores help engineers manage uncertain AI outputs by connecting model predictions and supporting evidence to explicit decision thresholds. For generative AI, they can help identify potentially unsupported responses, but they do not prove factual correctness and should complement grounding, output validation, and human review.

Context Window

The context window limits how much instruction, conversation history, retrieved information, and generated output a model can handle together. Engineers use this limit when selecting foundation models and designing prompts, retrieval pipelines, and conversation management so requests fit without sacrificing relevant information or exceeding cost and latency targets.

Control Groups

When evaluating AI adoption, a control group continues using the existing workflow while a treatment group uses the AI-enabled workflow. Measuring both groups before and during the rollout helps distinguish AI-driven business value from changes caused by seasonality, staffing, demand, or other factors.

Conversation Memory

Conversation memory lets a generative AI application carry forward relevant messages, user preferences, decisions, and task progress instead of treating every request as unrelated. It is part of context engineering: selecting and organizing the information a foundation model needs for its next response while controlling cost, privacy, and accuracy.

Cost Allocation

Cost allocation turns a cloud bill into an accountable view of who consumed resources and which business activities incurred costs. Engineers apply account boundaries, resource metadata, and allocation rules to support budgeting, showback, chargeback, and informed architecture decisions.

Cost management

In the cloud, cost management connects resource consumption and pricing choices to business outcomes. It helps engineers compare deployment options, eliminate waste, and balance spending against performance, availability, security, and operational effort.

Cost-Benefit Analysis

For cloud and AI/ML projects, cost-benefit analysis evaluates whether measurable improvements justify development, infrastructure, operational, and error-related costs compared with simpler alternatives. It helps engineers recognize when predictions provide useful business value and when deterministic software, established rules, or human judgment are more appropriate.

Data Contracts

A data contract makes expectations about shared data explicit, testable, and owned rather than leaving consumers to infer them from files or tables. It provides a foundation for reliable AI by clarifying who is accountable for data, whether it is suitable and permitted for a particular use, and how changes or failures will be handled.

Data Minimization

Data minimization reduces privacy exposure by limiting the amount, sensitivity, and detail of information used throughout a system’s lifecycle. In cloud and AI architectures, it helps engineers preserve useful functionality while reducing unnecessary disclosure, storage, and downstream use of personal or confidential information.

Data Network Effects

The reinforcing cycle connects adoption, useful data, better AI-driven outcomes, and further adoption. It can support sustainable competitive advantage when the data is difficult to replicate and improvements benefit users across the product, but data volume alone does not establish a network effect.

Data Provenance

Data provenance connects a dataset to its sources, collection conditions, permissions, processing steps, and downstream uses. In AI systems, it helps engineers assess whether training and evaluation data are appropriate, investigate quality or bias issues, reproduce results, and explain the evidence behind model development.

Data Quality

Data quality determines whether engineers can rely on data for analytics, application behavior, and AI training or inference. In secure data engineering, quality assessments work alongside privacy protections, access controls, and integrity checks to reduce unreliable outputs, unauthorized changes, and inappropriate use of sensitive information.

Data Representativeness

Representative data provides appropriate coverage of the populations and situations an AI system will encounter, including relevant minority groups and uncommon but important cases. It supports reliable evaluation and responsible development by reducing coverage gaps that can hide poor performance or unequal outcomes.

Data Silos

Data silos arise from disconnected applications, organizational boundaries, incompatible formats, and restrictive or unclear access processes. They reduce AI readiness by limiting the completeness, quality, and availability of training and inference data, even when an organization holds large volumes of information.

Decision Rights

Decision rights connect organizational accountability to the choices that shape an AI initiative, including funding, data use, risk acceptance, and production deployment. Clear assignments help cross-functional teams act quickly within agreed boundaries while keeping consequential decisions with authorized owners.

Determinism

Determinism concerns repeatability, not whether an answer comes from explicit rules or a learned model, and not whether that answer is correct. When choosing between conventional software and AI/ML, distinguish repeatable execution from guaranteed compliance with a specification: a model can repeatedly produce the same prediction without satisfying a requirement for an exact calculation or mandatory business rule.

Embeddings

An embedding model maps inputs such as text or images into a vector space where related inputs are intended to have similar representations. Embeddings support semantic search, recommendations, clustering, and retrieval-augmented generation by helping applications find relevant information beyond exact keyword matches.

Encryption

Encryption helps prevent unauthorized parties from understanding data stored in cloud systems or transmitted over networks. Its effectiveness depends on protecting cryptographic keys, controlling decryption permissions, and applying encryption wherever sensitive data travels or persists.

Environmental Sustainability

In cloud computing and AI, environmental sustainability means considering energy consumption, greenhouse gas emissions, water use, and hardware resource demands when designing and operating workloads. Responsible model selection weighs these impacts alongside accuracy, safety, fairness, latency, privacy, and cost rather than automatically choosing the largest or most capable model.

EU AI Act

The Act links governance obligations to an AI system’s intended purpose, potential harms, and the organization’s role in its lifecycle. Engineers and business leaders use this classification to identify prohibited applications, prioritize controls for high-risk systems, and implement applicable transparency requirements rather than treating every AI workload identically.

Executive Sponsorship

For cloud and AI adoption, executive sponsorship connects technical work to business outcomes and gives teams the authority and resources to deliver change across organizational boundaries. Effective sponsorship includes continuing decisions about priorities, readiness gaps, risk, and adoption—not simply approving a budget or endorsing a launch.

Experiment Tracking

Experiment tracking connects each model result to the data, code, parameters, and execution environment that produced it. It supports repeatable development, informed model selection, and traceability as models move toward production and are later retrained.

Failover

Failover uses redundant resources, health detection, and a mechanism for transferring work to reduce interruptions when components fail. In cloud architectures, distributing those resources across multiple Availability Zones helps maintain availability when an instance or an entire zone becomes unavailable.

Feedback Loops

In responsible AI, feedback loops connect model decisions and explanations with the people affected by them, allowing users to question results, report problems, and request review. They support human-centered design by turning those signals into evaluated changes to models, explanations, interfaces, or operating policies.

Fine-Tuning

Fine-tuning reuses the capabilities of an existing model rather than learning everything from scratch. It can improve task accuracy, response style, and output consistency, but introduces training, evaluation, deployment, and maintenance costs that must be compared with prompting and retrieval-based approaches.

First-Mover Advantage

Early adoption of AI can create advantages through customer acquisition, operational learning, proprietary data, and integration into customer workflows. Moving first matters only when the organization converts its head start into measurable value that competitors cannot quickly reproduce.

Gap Analysis

For AI transformation, gap analysis identifies specific shortfalls across people, processes, technology, and governance that could prevent business success. It turns a broad readiness assessment into an evidence-based improvement plan with priorities, accountable owners, and measurable completion criteria.

GDPR

GDPR requires organizations to justify, protect, and remain accountable for their use of personal data, including data processed by AI systems. For cloud and AI leaders, compliance involves business decisions, contractual safeguards, technical controls, and operational processes rather than simply choosing a compliant cloud provider.

Generative AI

Generative AI creates outputs from learned patterns and supplied context rather than only assigning labels or predicting numerical values. In cloud applications, it supports capabilities such as document summarization, conversational assistance, and code generation, but requires evaluation and controls because plausible outputs are not necessarily correct.

Growth Mindset

In cloud and AI transformation, a growth mindset helps people treat unfamiliar technology and capability gaps as opportunities to learn rather than evidence of permanent limitations. Leaders make this practical by providing safe experimentation, role-specific training, constructive feedback, and clear accountability for responsible adoption.

Guiding Coalition

A guiding coalition connects executive sponsorship with the operational leaders and trusted practitioners who make change happen. In enterprise AI transformation, it aligns business priorities, removes organizational barriers, and empowers AI champions to build workforce capability and sustain momentum beyond initial pilots.

Hallucinations

Generative AI can produce convincing answers without establishing that their claims are true or supported by the supplied evidence. Engineers must account for this limitation because fabricated facts, citations, instructions, or commitments can cause operational failures, legal exposure, and loss of customer trust.

High performance

High performance depends on how effectively an application uses compute, memory, storage, and networking to deliver useful work. In the cloud, it requires measurable targets, appropriate resource choices, and continuous tuning rather than simply selecting larger instances.

Hub-and-Spoke Model

For enterprise AI, the hub is typically an AI center of excellence, while the spokes are business-unit or product teams responsible for applying AI to specific problems. This arrangement helps organizations scale beyond isolated pilots by reusing infrastructure and governance without removing delivery ownership from domain experts.

Human-Centered Design

For AI systems, human-centered design makes predictions and decisions understandable, useful, and open to appropriate human challenge or correction. It combines user research, accessible explanations, feedback mechanisms, and meaningful oversight so that technical performance supports real human needs rather than becoming the only measure of success.

Human-in-the-Loop

Human-in-the-Loop combines AI’s ability to process information at scale with people’s ability to interpret context, resolve ambiguity, and exercise judgment. It supports assisted decision-making and responsible automation by giving people meaningful opportunities to correct outputs, challenge decisions, and improve system behavior.

Inference Latency

Inference latency determines how quickly an AI-powered application responds and whether it meets user expectations or processing deadlines. For generative AI, input length, generated output length, model choice, and available serving capacity affect latency, while token-based pricing links much of that work to inference cost.

Intellectual Property Rights

In cloud and generative AI systems, intellectual property rights affect the use of training data, prompts, retrieved documents, models, software, and generated outputs. Engineers must combine licensing reviews, access controls, provenance records, and output review to reduce infringement claims and protect proprietary assets without assuming that a managed service provides legal clearance.

Interpretability-Performance Tradeoff

Models that are easy to understand may sacrifice predictive capability on some tasks, while more complex models can require additional methods to explain their behavior. This tradeoff is not inevitable: engineers must measure model quality, explanation usefulness, safety, latency, and cost rather than assume that complexity always improves results.

ISO/IEC 23053

ISO/IEC 23053:2022, titled “Framework for Artificial Intelligence (AI) Systems Using Machine Learning (ML),” establishes a common way to understand and describe ML-based AI systems. It helps engineers, business stakeholders, and suppliers communicate about system architecture without tying that discussion to a particular cloud provider or product.

ISO/IEC 42001

ISO/IEC 42001:2023 provides an organizational framework for governing the responsible development, provision, and use of AI. It connects technical safeguards with accountable leadership, risk assessment, documented processes, and ongoing oversight, helping organizations demonstrate that AI governance operates in practice.

Iterative Prompt Refinement

A prompt is treated as a testable application component rather than a one-time question. Engineers examine outputs, identify failure patterns, and make targeted revisions to improve accuracy, relevance, consistency, and safety without necessarily changing model weights.

Key Performance Indicators

A key performance indicator connects a business objective to a defined measurement, target, and review period. For generative AI applications, KPIs help engineers distinguish technical improvements from business value by measuring outcomes such as efficiency, conversion, revenue, accuracy, and return on investment.

Label Quality

Labels define expected outcomes for supervised learning, human-preference training, and many AI evaluations. Incorrect, ambiguous, outdated, or systematically biased labels can teach models the wrong behavior and make evaluation results misleading, even when the underlying data and training pipeline are technically sound.

Labor Productivity

Labor productivity measures how effectively people turn working time into business outcomes. For cloud and AI initiatives, it helps determine whether automation and assistance increase useful capacity, while distinguishing time savings from realized financial benefits.

Leading Indicators

Leading indicators provide early evidence about project readiness, adoption, technical performance, and delivery risk before financial or operational results are fully observable. They help teams intervene sooner, but their usefulness depends on validating their relationship to the business outcomes they are intended to predict.

Least privilege

Least privilege reduces the damage that compromised credentials, software defects, and operational mistakes can cause. In cloud environments, it applies to identity permissions, workload roles, administrative access, network connectivity, and organizational guardrails, and requires ongoing review as requirements change.

Machine learning

Machine learning turns examples and experience into models that can handle tasks such as detecting suspicious transactions, classifying images, and understanding text. Cloud platforms provide scalable infrastructure and managed APIs for applying these models, but useful results still depend on appropriate data, evaluation, security, and ongoing monitoring.

Management and governance

Management handles activities such as provisioning, monitoring, configuration, and remediation, while governance defines who may act, which standards apply, and how compliance is demonstrated. Together, they help organizations give engineers useful autonomy without losing accountability, cost visibility, or control over risk.

Mass Customization

Mass customization combines reusable components and repeatable processes with customer-specific choices or adaptations. AI and cloud infrastructure can make this model economically practical by automating configuration, content creation, and fulfillment decisions, helping businesses compete through differentiated offerings rather than price alone.

Minimum Viable Product

An MVP limits initial scope so a team can learn whether a proposed solution solves a meaningful problem before committing to broader investment. In cloud and AI initiatives, it connects experimentation to a controlled launch, using measured outcomes to decide whether to improve, scale, pivot, or stop.

Model Drift

A model learns patterns from historical data, but those patterns may no longer represent the environment in which it operates. Monitoring for drift helps teams identify changing conditions, investigate performance problems, and decide whether to fix data pipelines, adjust the model, or retrain it.

Model Evaluation

Model evaluation uses representative data, defined metrics, and human judgment to determine whether a model meets technical and business requirements. It supports model selection and release decisions throughout the foundation model lifecycle, helping engineers balance output quality, safety, latency, cost, and environmental impact.

Model Explainability

Explainability helps engineers, reviewers, and affected users understand which inputs and model behaviors contributed to an outcome. It matters when choosing between traditional machine learning and foundation models because regulatory obligations, decision risk, and operational constraints can require explanations that a highly complex model cannot reliably provide.

Model Inference

Inference puts a model's learned patterns to work, such as estimating delivery times, identifying suspicious transactions, or generating a customer-support response. It is distinct from training and requires engineering decisions about response time, cost, capacity, output quality, and data protection.

Model Retraining

A model learns patterns from historical data, but those patterns may become less useful as users, operating conditions, or business processes change. Ongoing monitoring identifies potential drift and performance degradation, while retraining provides a controlled way to update the model when evidence shows that an update is needed.

Model Robustness

A robust model behaves reliably beyond clean training examples, including when production inputs contain errors, unfamiliar variations, or adversarial manipulation. Robustness is a feature of responsible AI because unexpected model failures can create harmful decisions, unreliable automation, and loss of user trust.

Multi-Agent Orchestration

Multiple specialized agents can collaborate on work that requires different responsibilities, data sources, or decision steps. Orchestration defines how tasks are assigned, how agents communicate, and how the application controls state, failures, permissions, and completion.

Networking, connectivity, and content delivery

This concept combines network isolation, addressing, routing, name resolution, hybrid connectivity, traffic distribution, and delivery from geographically distributed edge locations. Engineers use these capabilities to balance reachability, security, latency, availability, and cost across public-facing applications and private systems.

NIST AI Risk Management Framework

The framework organizes AI risk management around four functions: GOVERN, MAP, MEASURE, and MANAGE. It helps organizations prioritize oversight and controls according to an AI system’s context, potential harms, and risk tolerance, without prescribing universal risk tiers or replacing applicable laws.

Operational Readiness Reviews

An operational readiness review evaluates production controls, support processes, ownership, and unresolved risks before launch or a significant change. For AI initiatives, it connects successful experimentation to enterprise deployment by checking model behavior, data governance, human oversight, reliability, and ongoing operating costs—not just prototype accuracy.

Overfitting

An overfit model can achieve excellent training results without learning relationships that generalize reliably. Preventing overfitting improves prediction accuracy and supports responsible AI, especially when overall performance hides unreliable predictions for particular demographic groups.

Payback Period

Payback period measures how quickly a cloud or AI initiative earns back its upfront investment through incremental financial benefits. It helps teams assess funding exposure and compare initiatives, but it does not measure total profitability or capture benefits beyond the recovery point.

Phased Rollout

A phased rollout starts with a limited deployment that delivers measurable value, then expands through defined stages toward broader adoption. For enterprise AI, it connects short-term wins to repeatable technical, operational, and organizational capabilities while limiting the impact of failures.

Porters Five Forces

The framework examines the structural pressures that determine how much value businesses can retain within an industry. For cloud and AI strategy, it helps teams identify where AI could reduce costs, create differentiation, or change bargaining power—and where competitors could quickly copy those improvements.

Privacy by Design

Privacy by Design treats privacy as a continuous engineering and governance responsibility rather than a compliance check performed before launch. In cloud and AI projects, it reduces unnecessary data collection, limits inappropriate use and disclosure, and makes privacy requirements part of business decisions throughout the system lifecycle.

Privacy Impact Assessment

A Privacy Impact Assessment identifies privacy risks before an organization introduces or changes a system, business process, or AI use case. It documents data flows, applicable obligations, potential harms, mitigation measures, and accountability so decision-makers can determine whether processing should proceed.

Prompt Context

Context gives a model task-specific facts, conversation history, reference material, or situational details that may not be available from its learned parameters. Selecting relevant, trustworthy context improves response quality, but requires attention to token limits, cost, privacy, and the distinction between supporting information and instructions.

Prompt Templates

A prompt template defines the repeatable parts of a model request, such as the task, context boundaries, examples, and expected response format, while leaving placeholders for request-specific data. Templates help engineers standardize application behavior, evaluate changes systematically, and reduce duplicated prompt-building logic without retraining the model.

Proof of Concept

A proof of concept (POC) replaces assumptions with evidence about technical feasibility, business potential, and implementation constraints. In cloud and AI initiatives, it reduces uncertainty while giving teams practical experience, but success does not establish production readiness or enterprise-wide AI maturity.

Psychological Safety

Psychological safety helps teams surface uncertainty and operational risks before they become business failures. During AI adoption, it enables employees to discuss skills gaps, question model outputs, and report unsuccessful experiments while remaining accountable for responsible behavior and delivery standards.

RACI Matrix

A RACI matrix makes ownership explicit across teams by separating who performs work from who owns its outcome, provides input, or receives updates. In cloud and AI initiatives, it helps prevent governance gaps, unclear approvals, duplicated effort, and operational handoffs without an owner.

Resiliency

Resiliency combines failure isolation, redundant resources, controlled recovery, and operational testing to limit the impact of failures. In the cloud, it requires deliberate architecture across independent failure domains rather than assuming that provider-managed infrastructure makes an application immune to outages.

Retrieval-Augmented Generation

RAG connects a foundation model to information outside its learned parameters, such as enterprise documents, product catalogs, or operational records. It helps applications answer questions using organization-specific or recently updated information without retraining the model, although accuracy still depends on retrieval quality and how the model uses the evidence.

Return on Investment

ROI helps engineers and business stakeholders determine whether an AI, ML, or cloud initiative produces enough measurable value to justify its costs. Unlike model-quality metrics, ROI connects technical performance to financial outcomes such as reduced operating expenses, increased contribution profit, or avoided losses.

Right-Sizing

Right-sizing uses observed demand and application requirements to choose appropriate compute, memory, storage, and throughput capacity. It reduces waste while preserving performance and reliability, and it requires regular review as workloads change.

Risk Appetite

Risk appetite guides decisions when business benefits conflict with concerns such as safety, fairness, privacy, security, and transparency. For cloud and AI initiatives, it helps teams determine which use cases to pursue, which safeguards are required, and when residual risk requires escalation or prevents deployment.

Risk Matrix

A risk matrix maps identified risk scenarios to consistently defined likelihood and consequence levels, producing categories such as low, medium, high, or critical. In AI governance, it helps teams allocate oversight across the lifecycle while keeping business risk prioritization separate from mandatory legal classifications and obligations.

Role-Based Learning

Employees need different levels of AI knowledge depending on whether they sponsor initiatives, build systems, govern risks, or use AI-assisted workflows. Role-based learning combines shared AI literacy with targeted development so an organization can adopt AI effectively without requiring every employee to become a machine learning specialist.

Rule-Based AI

Rule-based AI represents human knowledge as conditions and actions, often expressed as if–then rules evaluated by a reasoning engine. It is useful when decision criteria are explicit and explainability matters, but it requires manual maintenance as policies and operating conditions change.

Rule-Based Systems

A rule-based system uses human-authored logic, such as if–then conditions, rather than learning decision patterns from training data. It is useful when requirements are clear, outcomes must follow explicit policies, and decisions need to be traceable. Choosing between rules and learned AI depends on whether the task can be specified reliably or requires interpreting patterns, ambiguity, or unstructured information.

Selective Disclosure

In responsible AI, selective disclosure balances meaningful transparency with the risks of exposing sensitive data, proprietary information, or details that enable misuse. It helps engineers provide useful explanations and accountability without assuming that transparency requires publishing every model artifact or operational control.

Semantic Search

Semantic search helps users find relevant information even when their queries use different wording from the source material. It commonly uses machine-learning embeddings and relevance models, making it useful for enterprise search, customer support, and retrieving evidence for generative AI applications.

Semi-Structured Data

Semi-structured data combines identifiable organization with flexible fields, nesting, and optional attributes, as commonly seen in JSON events and XML documents. It matters because cloud ingestion, analytics, and AI pipelines must preserve that flexibility while validating and transforming records into forms that downstream consumers can use reliably.

Sensitivity Analysis

Sensitivity analysis tests whether a business case remains attractive when inputs such as adoption, time savings, inference costs, or revenue uplift change. It helps engineers and business stakeholders identify the assumptions that drive value, establish break-even thresholds, and prioritize evidence gathering before committing resources.

Separation of Duties

The idea is to prevent one identity from initiating, approving, executing, and concealing a sensitive action without independent oversight. In cloud environments, separate administrative roles, account boundaries, approval workflows, and protected audit records reduce the risk of fraud, mistakes, and compromised credentials.

Servitization

Servitization shifts the commercial relationship from a one-time product sale toward continuing support, capabilities, or measurable outcomes. Cloud connectivity and AI can make this model practical by enabling remote monitoring, predictive maintenance, and optimization, but success also requires suitable pricing, service operations, and accountability for delivery.

Shadow AI

Shadow AI occurs when employees or teams adopt AI outside established security, procurement, and risk-management processes, including AI features embedded in otherwise familiar software. Transparent classification of tools as approved, blocked, or under evaluation helps people choose permitted solutions while reducing data exposure, compliance gaps, and unaccountable decision-making.

Skills Matrix

A skills matrix compares demonstrated capabilities with the capabilities needed to deliver and operate a business initiative. For cloud and AI transformation, it helps leaders identify missing expertise, insufficient role coverage, and development priorities while distinguishing workforce gaps from process, technology, and governance deficiencies.

Stage-Gate Process

Each stage produces evidence that decision-makers assess against agreed business, technical, operational, and risk criteria before committing further resources. For cloud and AI initiatives, this approach limits premature investment, aligns development with organizational maturity, and creates a controlled path from experimentation to enterprise adoption.

Stakeholder Mapping

Stakeholder mapping connects technical change to the people who authorize, implement, operate, or experience it. For cloud and AI programs, it helps teams establish executive sponsorship, empower credible local champions, and communicate clearly about delivery timelines, expected outcomes, and changes to workforce roles.

Status Quo Bias

In cloud and AI adoption, status quo bias can cause teams to retain familiar workflows even when alternatives could improve measurable outcomes. Leaders address it through fair comparisons, bounded experiments, workforce development, and clear accountability—not by treating every objection as irrational resistance.

Storage

Cloud storage provides data capacity through managed services rather than requiring engineers to operate all underlying disks and storage systems. Choosing an appropriate storage model and tier requires balancing access patterns, performance, resilience, retention requirements, and total cost.

Structured Data

Structured data commonly appears as records and tables containing values such as customer identifiers, transaction amounts, and timestamps. Its predictable organization makes it useful for querying, validation, analytics, and machine learning, but it does not automatically make the data accurate, labeled, or ready for model training.

Subgroup Analysis

An AI system can perform well on average while producing less accurate, less reliable, or more harmful results for particular populations or operating conditions. Subgroup analysis compares relevant groups using appropriate quality and fairness metrics, helping engineers detect potential bias, investigate label quality, and monitor whether improvements benefit all affected users.

Supervised Learning

A supervised model learns the relationship between input features and known target values, such as transaction details paired with fraud labels or property attributes paired with sale prices. It supports classification and regression, making it useful when historical outcomes are available and engineers need predictions for new cases.

SWOT Analysis

SWOT analysis helps organizations evaluate their competitive position by connecting existing capabilities and limitations with conditions in the market. For cloud and AI initiatives, it supports decisions about where adoption could create measurable business advantage, which gaps require investment, and which risks could undermine the outcome.

Task Completion Rate

Task completion rate measures whether an AI application helps users accomplish their intended goals, rather than merely producing plausible responses. It connects foundation model performance to business objectives and should be evaluated alongside user satisfaction, cost per interaction, latency, and safety.

Task Decomposition

Task decomposition makes the inputs, outputs, dependencies, and judgment requirements of work explicit. It helps organizations identify where AI can assist or automate individual steps while people retain responsibility for decisions requiring critical thinking, empathy, creativity, or accountability.

Task Planning

In foundation-model applications, task planning helps an AI agent determine what actions are needed to achieve a business goal rather than merely generate a response. It enables multistep automation, but reliable implementations must constrain tool access, validate results, and require approval for consequential actions.

Technology Adoption Lifecycle

The model groups adopters into innovators, early adopters, early majority, late majority, and laggards. For AI strategy, it helps organizations choose investment timing and scale by comparing industry adoption, competitive pressure, organizational readiness, and the potential for differentiated business value.

Text Generation

Text generation uses learned language patterns to produce outputs such as summaries, translations, conversational responses, and code. In cloud applications, it enables engineers to build assistants and content-processing workflows without writing explicit rules for every possible response, but its outputs require controls for accuracy, security, and suitability.

Tokenization

Tokens can represent whole words, word fragments, punctuation, whitespace, or other character sequences, depending on the model’s tokenizer. Tokenization determines how much content fits into a model request and directly affects token-metered inference costs, processing requirements, and response latency.

Tool Use

A foundation model can select a tool and generate structured arguments, while the application or managed agent runtime validates and executes the request. This connects language-based reasoning to current data and business systems, enabling AI agents to complete tasks rather than only generate text.

Total Cost of Ownership

Total Cost of Ownership (TCO) includes direct expenses, such as hardware or cloud usage, and indirect expenses, such as administration, facilities, and migration effort. It helps engineers compare deployment options fairly and determine whether moving a workload to the cloud will reduce overall costs rather than simply change how those costs are billed.

Train-Validation-Test Split

Training data teaches a model, validation data guides development decisions, and test data provides an independent final evaluation. Keeping these roles separate helps engineers detect overfitting, prevent data leakage, and estimate how well a model will generalize to production inputs.

Unstructured Data

Unstructured data contains information that typically requires interpretation or transformation before conventional analytics or machine learning can use it effectively. It matters because documents, conversations, photographs, and recordings provide signals that fixed database fields often do not capture.

User Satisfaction

For AI applications, user satisfaction measures whether people find the experience useful, trustworthy, understandable, and responsive. It connects foundation model evaluation to business objectives, but must be assessed alongside task completion, factual correctness, safety, and operating cost.

Vendor Lock-In

In cloud and AI systems, vendor lock-in can arise from proprietary APIs, data formats, model capabilities, operational processes, and contractual commitments. It matters when evaluating build-buy-partner decisions because rapid delivery and lower initial costs can come with reduced negotiating flexibility and higher future migration costs.

Weighted Scoring

Weighted scoring makes investment priorities explicit by evaluating options against shared criteria such as strategic alignment, expected business value, implementation feasibility, and organizational readiness. For cloud and AI initiatives, it helps teams select achievable investments and create progression pathways that reflect both business objectives and current maturity.

Services on the exam

The 39 AWS services the AIB-C01 (beta) exam covers.

Concepts on the exam

The 137 cloud concepts the AIB-C01 (beta) exam covers, each explained with the AWS services that implement it, in the Cloud Concepts Hub .

Other practice exams