A developer is using Hugging Face Transformers to fine-tune a BERT model for sentiment analysis. They want to track experiments, log metrics, and compare runs. Which MLOps tool should they integrate?
MLflow's Tracking API is simple to integrate and supports logging parameters, metrics, and artifacts.
Why this answer
MLflow is the correct choice because it is purpose-built for experiment tracking, metric logging, and run comparison in machine learning workflows. It provides an API to log parameters, metrics, and artifacts, and its UI allows easy comparison of different fine-tuning runs, which directly matches the developer's need to track experiments and compare runs for a BERT sentiment analysis model.
Exam trap
Cisco often tests the distinction between infrastructure tools (Airflow, Docker, Kubeflow) and ML-specific experiment tracking tools (MLflow), trapping candidates who confuse orchestration or containerization with MLOps tracking capabilities.
How to eliminate wrong answers
Option A is wrong because Apache Airflow is a workflow orchestration tool for scheduling and managing DAGs (Directed Acyclic Graphs) of tasks, not for experiment tracking or metric logging; it lacks native ML run comparison capabilities. Option B is wrong because Docker is a containerization platform for packaging applications and dependencies, not an MLOps tool for logging metrics or comparing experiments; it provides environment consistency but no tracking or logging features. Option C is wrong because Kubeflow is a Kubernetes-native platform for deploying and managing ML pipelines at scale, but it is overkill for simple experiment tracking and does not offer the lightweight, focused metric logging and run comparison that MLflow provides out of the box.