Bird
0
0

An ECS service fails to launch any tasks after creation. Which of the following is the most probable cause?

medium📝 Debug Q6 of 15
AWS - ECS and Fargate
An ECS service fails to launch any tasks after creation. Which of the following is the most probable cause?
AInsufficient CPU or memory resources available on the cluster
BTask definition is missing a container image
CService is configured with desired count set to zero
DIAM role permissions are too permissive
Step-by-Step Solution
Solution:

  1. Step 1: Identify common launch failures

    Insufficient cluster resources (CPU/memory) prevent task placement.

  2. Step 2: Evaluate other options

    Missing container image would cause task definition errors; desired count zero means no tasks requested; overly permissive IAM roles do not block launches.

  3. Final Answer:

    Insufficient CPU or memory resources available on the cluster -> Option A

  4. Quick Check:

    Check cluster resource availability first [OK]
Quick Trick: Check cluster resources if tasks don't launch [OK]
Common Mistakes:
  • Assuming IAM permissions block task launch
  • Ignoring resource constraints on cluster
  • Overlooking desired count configuration

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
Advanced Security - Security Hub overview - Quiz 7medium Advanced Security - AWS WAF for web application firewall - Quiz 5medium Advanced Security - Secrets Manager for credentials - Quiz 7medium Architecture Best Practices - Why AWS Well-Architected matters - Quiz 11easy CloudFormation - Parameters for customization - Quiz 5medium Cost Optimization - Data transfer cost awareness - Quiz 7medium ECS and Fargate - Fargate serverless containers - Quiz 1easy EKS - Why managed Kubernetes matters - Quiz 14medium Route 53 - Hosted zones concept - Quiz 8hard Route 53 - Record types (A, AAAA, CNAME, Alias) - Quiz 9hard