AIF-C01 domain - 20% of the exam

Fundamentals of AI and ML

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

The domain in numbers

65
Practice questions
3
Objectives
45
Easy
20
Medium

Where people go wrong

  • Treating inference as training

    The wrong answers assign the production step to training, fine-tuning or hyperparameter tuning, or claim that both phases adjust parameters. Training is where a model learns its parameters from example data. Inference applies those fixed parameters to a new, unseen input to produce a prediction, so nothing is updated when a deployed model scores a live request.

    See it in a sample question
  • Confusing data drift, concept drift and training-serving skew

    The wrong answers swap three causes of degradation. Data drift is a shift in the distribution of input features. Concept drift is a change in the relationship between those inputs and the target, so the same feature values lead to different outcomes. Training-serving skew arises when inference computes features differently from training, and it appears straight after a pipeline change rather than gradually.

    See it in a sample question
  • Missing that an exact rule makes machine learning unnecessary

    The wrong answers explain why machine learning is unnecessary with dataset size, infrastructure limits, noisy targets or missing labels, or propose it for a fixed lookup table. The deciding fact is that a complete, deterministic rule already gives the correct answer, as with Dijkstra's shortest path or a published tax table. A coded rule is then exact and auditable, and a learned model only adds complexity.

    See it in a sample question
  • Matching the learning paradigm to the wrong labels

    The wrong answers pick a paradigm that ignores whether labels exist. Unsupervised learning is offered for agent-tagged emails or annotated reviews, and supervised classification is offered when no labels or categories exist. Reinforcement learning needs a reward signal from interaction, which a static dataset lacks. Supervised learning needs labelled pairs, unsupervised clustering finds groups without labels, and semi-supervised learning combines a small labelled set with a large unlabelled one.

    See it in a sample question
  • Placing an activity in the wrong lifecycle phase

    The wrong answers move an activity to a phase it does not belong to: deployment planning or data collection for problem framing, tuning or evaluation for data pre-processing, labelling or model selection for live monitoring. Framing and data preparation come before training, tuning belongs to training, and comparing live distributions against a baseline is post-deployment monitoring.

    See it in a sample question

Objectives in this domain

What to study

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

Sample questions from this domain

Free sampleFundamentals of AI and MLeasy

A trained fraud-detection model is deployed to a production API. When the API receives a new transaction, the model produces a fraud probability score in real time. What is the term for this production-time step where the model generates a prediction from new input?

  • ATraining, where the model updates its internal weights using labelled examples and a loss function.
  • BFine-tuning, where a pre-trained model is further adapted on a domain-specific labelled dataset.
  • CEvaluation, where model performance is measured against a held-out test set using metrics such as AUC-ROC.
  • DInference, where a deployed model applies learned parameters to new input data to produce an output. Correct
Identify inference as the phase in which a deployed ML model generates predictions on new input data. Once a model is trained, its parameters are frozen and it enters the inference phase. During inference the model applies its learned weights to new examples to produce predictions - in this case, a fraud probability score. Inference is distinct from training (weight update) and evaluation (batch quality measurement).

Why A is wrong: Tempting because training is the most prominent phase of the ML lifecycle, but training occurs before deployment. The stem describes a post-deployment step on new, unseen data.

Why B is wrong: Tempting because fine-tuning is a common deployment-adjacent concept, but it is still a training-time activity. It does not describe the act of generating a prediction from a deployed model on live input.

Why C is wrong: Tempting because evaluation also uses a model against real data, but it is a development-time step that measures quality. The stem describes live production scoring, not a benchmarking activity.

Why D is correct: Inference is the ML lifecycle phase in which a trained model uses its fixed parameters to process new inputs and generate predictions or outputs. This is exactly what happens when the API scores a live transaction.

Free sampleFundamentals of AI and MLmedium

A logistics company trains a demand forecasting model and then deploys it as a REST API endpoint behind a load balancer. Six months later, a newly hired engineer rewrites the data pre-processing pipeline, causing feature values to be computed differently from how they were computed during training. The model begins producing erratic forecasts. This situation exemplifies which ML lifecycle challenge?

  • ATraining-serving skew, where the features supplied to the model during inference differ from those seen during training due to inconsistent pre-processing. Correct
  • BConcept drift, where the relationship between demand signals and actual order volumes has changed in the market since the model was trained.
  • CModel decay, where the statistical patterns learned during training become less relevant as new products and routes are introduced over time.
  • DOverfitting, where the model memorised noise in the original training data and now fails to generalise to slightly different feature values.
Identify training-serving skew as the lifecycle challenge arising when inference-time feature computation differs from training-time feature computation. Training-serving skew is a deployment and monitoring concern in the ML lifecycle. It arises when the code path used to compute features at inference time diverges from the code path used during training, even when the raw input data is comparable. The model was optimised for a specific feature representation; any discrepancy causes the model to operate outside its training distribution. Preventing training-serving skew requires shared, versioned feature transformation code used in both training pipelines and serving systems.

Why A is correct: Correct. Training-serving skew occurs when the transformation applied to raw inputs at inference time diverges from the transformation applied during training. Even though the underlying raw data is similar, the model receives feature values outside its training distribution, producing unreliable outputs. This is a recurring operational challenge in the deployment and monitoring phase of the ML lifecycle.

Why B is wrong: Tempting because concept drift also causes previously accurate models to produce erratic forecasts, and it is a legitimate post-deployment risk. However, concept drift is a gradual market or environmental change, whereas the described problem began immediately after a specific code change. The direct causal link to the pipeline rewrite points to training-serving skew rather than an external distribution shift.

Why C is wrong: Tempting because model decay describes a temporal degradation that is common in logistics forecasting as the product catalogue and route network evolves. However, model decay is a slow process driven by real-world changes, not an immediate effect triggered by a code change in the pre-processing pipeline.

Why D is wrong: Tempting because overfitting does cause sensitivity to input variation, but overfitting is a training-phase problem that would have been visible in validation metrics before deployment. The scenario describes a model that performed well for six months before a specific pipeline change, which rules out pre-existing overfitting as the explanation.

Free sampleFundamentals of AI and MLeasy

A startup is deciding whether to use machine learning or a deterministic algorithm to calculate the shortest delivery route between two fixed points on a well-mapped city grid. Which consideration most strongly suggests ML is NOT necessary here?

  • AThe city grid has many intersections, which increases computational complexity for any approach.
  • BThe startup lacks GPU infrastructure required to run machine learning models in production.
  • CThe problem has a mathematically optimal solution computable by a deterministic algorithm such as Dijkstra's, with no need to learn from data. Correct
  • DThe dataset of past delivery routes is too small to train a reliable model.
Recognise that deterministic algorithms with provably optimal solutions make machine learning unnecessary and inappropriate for a given problem. A core principle of responsible AI adoption is knowing when NOT to use ML. When a problem has a correct, exact, and efficiently computable classical solution - such as shortest-path algorithms for routing on a fixed graph - ML introduces unnecessary complexity, latency, and potential error. ML should be reserved for problems where rules or exact solutions cannot be derived.

Why A is wrong: Computational complexity is a concern for all approaches but does not determine whether ML is appropriate. Established graph search algorithms handle large city grids efficiently without ML.

Why B is wrong: Infrastructure limitations are a deployment concern, not a reason that ML is conceptually inappropriate. Many ML models run on CPUs. The real reason here is that the problem has an exact classical solution.

Why C is correct: When a problem has a known, exact, deterministic solution, introducing ML adds complexity without benefit. Shortest-path problems on a graph are solved optimally by classical algorithms. ML is not needed and would likely produce inferior results compared to an exact method.

Why D is wrong: Data scarcity is one factor in ML feasibility, but the deeper reason to avoid ML here is that the problem does not require learning from data at all - it has an exact mathematical solution. Framing it as a data problem misses the core point.

Free sampleFundamentals of AI and MLeasy

A data science team labels thousands of customer reviews as positive, neutral, or negative, then trains a model on those labels. Which category of machine learning does this training approach represent?

  • ASupervised learning, where labelled training examples teach the model to map inputs to correct output categories. Correct
  • BUnsupervised learning, where the model groups similar reviews without any provided labels.
  • CReinforcement learning, where an agent receives reward signals based on actions taken in an environment.
  • DSelf-supervised learning, where the model creates its own training signal from the structure of unlabelled text.
Recognise supervised learning as the approach where human-labelled data trains a model to predict predefined output categories. In supervised learning, each training example has a known target label provided by a human annotator or an authoritative source. The model learns to map inputs to these labels by minimising prediction error. Sentiment classification with positive/neutral/negative labels is a textbook supervised learning task.

Why A is correct: Supervised learning trains on input-label pairs. Providing labelled sentiment categories (positive, neutral, negative) and using them to train a classifier is the canonical supervised learning workflow.

Why B is wrong: Tempting because unsupervised learning also processes text data, but it works without labels. The stem explicitly states that labels were created and used, ruling this out.

Why C is wrong: Tempting because reinforcement learning is a prominent ML paradigm, but it requires an agent-environment loop with reward signals, not a static labelled dataset of reviews.

Why D is wrong: Tempting because large language models do use self-supervised pre-training on text, but that approach does not involve human-created sentiment labels. The stem describes explicit human annotation followed by training.

Free sampleFundamentals of AI and MLmedium

An ML engineer sets up automated alerts that fire when the Kullback-Leibler divergence between the live prediction score distribution and the baseline training distribution exceeds a defined threshold. This practice belongs to which phase of the ML lifecycle?

  • AData labelling, where annotators flag ambiguous examples that fall near the decision boundary.
  • BModel selection, where multiple candidate architectures are compared using divergence metrics computed on the held-out validation set.
  • CFeature engineering, where distributional properties of raw features are measured to guide transformation choices.
  • DModel monitoring, where production behaviour is continuously compared against an established baseline to detect drift or degradation. Correct
Identify model monitoring as the ML lifecycle phase responsible for detecting production drift using statistical divergence metrics. Model monitoring is conducted after deployment and runs continuously throughout a model's production life. Tracking the KL divergence between live prediction distributions and a training baseline is a proven early-warning technique: changes in output score distributions often signal input data drift or concept drift before precision and recall metrics visibly degrade, giving teams time to retrain or adjust thresholds before business impact occurs.

Why A is wrong: Tempting because boundary proximity is related to the divergence concept, but data labelling is a pre-training activity performed on offline datasets. KL divergence monitoring of live prediction distributions is a production-time activity that cannot occur during labelling.

Why B is wrong: Tempting because KL divergence is a legitimate model comparison tool, but model selection uses held-out data before deployment. The scenario explicitly describes live prediction distributions, confirming the model is already in production, so this cannot be model selection.

Why C is wrong: Tempting because feature engineering does involve analysing distributions, but that analysis operates on offline training data before model training. The described monitoring uses live prediction scores from a deployed model, placing it firmly in the post-deployment monitoring phase rather than pre-training feature engineering.

Why D is correct: Correct. Model monitoring is the post-deployment phase responsible for tracking production model health. Measuring KL divergence between live score distributions and a training baseline is a canonical technique for detecting prediction drift, which often precedes measurable accuracy loss. Automated thresholded alerts are standard monitoring infrastructure.

Other domains in this exam

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

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