EKS Spot Production Experiments Quiz
Related guide: EKS Spot Production Experiments and Result Assessment
1. A drain test passes on a Spot node with a PDB. What does this establish?
- A) Actual Spot reclamation always preserves the same availability
- B) The voluntary eviction path works; actual reclamation needs a separate test
- C) EC2 waits for the PDB before terminating the instance
- D) The application always receives two minutes to exit
Show Answer
Answer: B) The voluntary eviction path works; actual reclamation needs a separate test
Explanation: A PDB cannot prevent EC2 instance loss. Test notice delivery, eviction delay, forced termination, and service impact through actual reclamation and loss without notice.
2. A Pending Pod has a Spot-only selector. What happens if you add an On-Demand node?
- A) The Pod moves immediately regardless of its selector
- B) The PDB changes the selector to On-Demand
- C) The Pod remains ineligible for the On-Demand node
- D) NodePool weight overrides the selector
Show Answer
Answer: C) The Pod remains ineligible for the On-Demand node
Explanation: Fallback requires both available capacity and compatible Pod constraints. Broadening NodePool capacity types alone does not remove a Spot-only Pod selector.
3. A service starts after changing a NodePool to On-Demand-only. What did the drill verify?
- A) Automatic fallback after EC2 returns insufficient Spot capacity
- B) Configuration-based transition, scheduling, and startup on On-Demand
- C) Guaranteed Spot supply in every AZ
- D) Immediate relocation of all existing Spot Pods
Show Answer
Answer: B) Configuration-based transition, scheduling, and startup on On-Demand
Explanation: The drill did not inject a capacity error. Verify the actual provisioning path's error handling and fallback separately; leave it unverified if it cannot be reproduced.
4. FIS reports completed and the replacement node is Ready. What establishes a service-level pass?
- A) The FIS state alone
- B) Node Ready alone
- C) Client errors, latency, throughput, and correctness all meet the criteria
- D) No LB 5xx responses, ignoring client timeouts
Show Answer
Answer: C) Client errors, latency, throughput, and correctness all meet the criteria
Explanation: FIS completion describes injection. Service recovery also requires Pod readiness, LB target health, actual request success, and work correctness.
5. Which comparison correctly assesses Spot savings?
- A) Report the Spot discount as the service saving
- B) Compare effective cost per unique successful operation passing correctness checks under equivalent conditions
- C) Exclude retry and On-Demand replacement costs
- D) Count replacement overlap in both the EC2 bill and an additional-cost line
Show Answer
Answer: B) Compare effective cost per unique successful operation passing correctness checks under equivalent conditions
Explanation: Include overhead, commitment discounts, replacements, and retries without counting charges twice. Label short-run monthly extrapolations as estimates.
6. How should results be recorded when no experiment data exists?
- A) Enter expected recovery times as measurements
- B) Enter zero errors and pass
- C) Record NOT RUN and missing measurements; hold production expansion
- D) Treat official documentation as a completed experiment
Show Answer
Answer: C) Record NOT RUN and missing measurements; hold production expansion
Explanation: Documented behavior, hypotheses, and measurements are different evidence. Missing run IDs and raw results cannot establish production readiness.
7. E2's mixed path had 0.0556% overall errors and 0.8333% in its worst full 60-second window. If the 60-second criterion is 0.1%, what follows?
- A) Pass because the overall error rate is low
- B) Ignore failures because p99 is low
- C) The window criterion failed; address the configuration and repeat testing
- D) Spot cannot be used in any production service
Show Answer
Answer: C) The window criterion failed; address the configuration and repeat testing
Explanation: A long healthy tail can lower the overall error rate. Match the assessment window to the actual business SLO, and do not generalize one synthetic run to every configuration.