Orchestration at Scale — Final Exam
13 questions · pass mark 80% · 20 minute limit. The timer auto-submits at zero.
- Question 1easy
What is the prerequisite for scaling an LLM service with horizontal replicas?
- Question 2medium
Under heavy load, adding more replicas doesn't help throughput. What's the likely bottleneck for an LLM app?
- Question 3medium
How do you handle hitting a provider rate limit under load? (Select all that apply)
Select all that apply.
- Question 4medium
In Kubernetes, what does a Deployment guarantee?
- Question 5medium
What is a Kubernetes Service?
- Question 6medium
What does a HorizontalPodAutoscaler (HPA) do?
- Question 7hard
For a single scalable service, what is usually the right platform instead of Kubernetes?
- Question 8hard
Why is 'we'll put it on Kubernetes' often an over-engineering reflex?
- Question 9medium
Where should secrets live at scale, and how do they reach a container?
- Question 10hard
What does Infrastructure as Code (Terraform/Bicep) provide?
- Question 11hard
Which are orchestration/scaling pitfalls? (Select all that apply)
Select all that apply.
- Question 12medium
An app must be ____ (one word) — holding no per-user state in memory — to scale horizontally across replicas.
- Question 13hard
Which Kubernetes object (acronym) automatically adds/removes replicas based on load?