Design and implement an MLOps infrastructure
Learning goals
- Configure workspaces, datastores, compute, and identity and access management
- Manage data assets, environments and components, and share them across workspaces with registries
- Automate environment setup with Bicep, Azure CLI and GitHub Actions, and restrict networking
Key points
- A workspace is the management unit for ML assets. A datastore holds connection information to storage; a data asset is a (versionable) reference to that data.
- Choose compute by use: compute instances for development, autoscaling clusters for training, serverless with no management, and so on.
- Defining environments (dependencies, images) improves reproducibility of training and inference. Components are reusable building blocks of pipelines.
- Registries let you share models, environments and components across multiple workspaces (development, production and so on).
- IaC: define workspaces with Bicep and Azure CLI and provision automatically with GitHub Actions. For Azure authentication, consider federated credentials (OIDC) rather than long-lived secrets.
- Restrict access to production workspaces with private networking and similar, and manage code in Git.
Workplace uses
- SalesKeep the order-forecast model’s development and production environments identical with Bicep, preventing “it worked in dev but not in production.”
- General AffairsSeparate workspaces per department and keep view and run permissions minimal with RBAC.
- AccountingShare credit score model assets through a registry and place only approved versions in production.
Exam objectives (from the exam guide)
- Create and manage resources in a Machine Learning workspace
- Create and manage assets in a Machine Learning workspace
- Implement IaC for Machine Learning