You must specify compute for a bursty multi-agent workload: low traffic overnight, sharp peaks during business hours, strict per-tenant isolation goals, and cost sensitivity. Which compute approach best fits?
Select an answer to reveal the explanation.
Short Explanation
Correct answer: C. Bursty multi-agent traffic wants elastic compute—scale out when the business day hits, scale in overnight—and isolation that still lets you charge back tenants. Forever-max VMs and production-on-laptops are how budgets and SLAs die.
Full Explanation
Architects specify compute components that meet scalability, reliability, operational efficiency, security, and cost requirements. Option C describes elastic Azure hosting with autoscaling and isolation/cost allocation appropriate to multi-agent production systems.
Option A lacks elasticity and strong multi-tenant isolation.
Option B is not a production architecture for enterprise multi-agent solutions.
Option D wastes cost and ignores utilization-driven efficiency.
Exam tip: Pair bursty load language with autoscaling elastic compute and tenant isolation—not static overprovisioning alone.