Follow-up · depth 1
What metrics prove AWS VPC, Subnets, and Security Groups is healthy in prod?
What metrics prove AWS VPC, Subnets, and Security Groups is healthy in prod?
Answers use simple, clear English.
Audio N/AQuick interview answer
Prove AWS VPC, Subnets, and Security Groups is healthy with latency (p50/p95/p99), error/saturation rates, and queue/event-loop lag — not just CPU. Context: Baseline: VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless.
Detailed answer
Production health signals for AWS VPC, Subnets, and Security Groups: • Latency: p50/p95/p99 of the critical path that uses AWS VPC, Subnets, and Security Groups. • Errors: failure rate, timeouts, and retry storms. • Saturation: queue depth, event-loop delay, thread/pool utilization. • Business SLIs: request success and user-visible freshness where relevant. Trade-off lens: Pros: Strong network isolation primitives. Cons: Misconfigured routes cause outages. Explain thresholds + alerts, then how you triage. Parent context: Baseline: VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless.
Full explanation
Good answers name measurable signals and what “bad” looks like for AWS VPC, Subnets, and Security Groups. VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless. Private workloads without public IPs.
Follow-up questions
Only answered follow-ups are shown — click to open with full answers
Parent context — AWS VPC, Subnets, and Security Groups
Baseline: VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless.
View full parent question →