Guide-linked quiz · Medium Level
Terraform for ML Infrastructure Quiz
Review Terraform configuration, plans and state, with attention to GPU capacity, remote-state security and controlled production changes.
Question 1 of 8
What does Terraform state primarily track?
Preview every question8 questions
Answers and explanations appear as you take the quiz.
- What does Terraform state primarily track?
- The relationship between declared resources and remote infrastructure
- The model's validation accuracy
- The latest GPU prediction output
- The Python package graph
- Which review step shows proposed infrastructure actions before they are applied?
- Guarantee cloud capacity at apply time
- Inspect proposed infrastructure changes before applying them
- Validate model fairness automatically
- Replace remote state
- Why protect remote Terraform state?
- It guarantees GPU availability
- It contains only public source code
- It can contain sensitive values and is needed to manage resources reliably
- It replaces provider credentials
- Why might a valid GPU plan still fail during apply?
- State automatically creates cloud stock
- Terraform plans are always stale by definition
- The GPU model determines Python syntax
- Regional capacity or account quota may be unavailable
- What does setting a variable as sensitive guarantee?
- That the secret is encrypted in every backend
- Display redaction, not automatic removal from state
- That no provider can read it
- That it is omitted from all logs and files
- Why separate model validation from infrastructure provisioning?
- Model evaluation changes cloud regions
- Terraform cannot reference container images
- Terraform can create resources without determining whether a model is fit to deploy
- Infrastructure plans contain no resources
- What should a team do with a plan that includes destructive production actions?
- Remove backups first
- Apply automatically because Terraform calculated it
- Ignore state and repeat the apply
- Inspect affected resources, dependencies and recovery needs before applying
- Why use narrow apply permissions in production?
- It limits who can make infrastructure changes
- It makes every plan smaller
- It prevents all provider outages
- It removes the need for source review
Keep testing yourself
More quizzes picked for your level.