AWS - EKS
Which of the following is the correct AWS CLI command to create an EKS cluster named my-cluster with role ARN arn:aws:iam::123456789012:role/EKSRole and subnets subnet-abc123 and subnet-def456?
Which of the following is the correct AWS CLI command to create an EKS cluster named my-cluster with role ARN arn:aws:iam::123456789012:role/EKSRole and subnets subnet-abc123 and subnet-def456?
easy📝 Configuration Q12 of 15
Step-by-Step Solution
Solution:
Step 1: Check AWS CLI syntax for EKS cluster creation
The correct command uses--namefor cluster name,--role-arnfor IAM role, and--resources-vpc-config subnetIds=...for subnet IDs separated by commas.Step 2: Identify correct option
aws eks create-cluster --name my-cluster --role-arn arn:aws:iam::123456789012:role/EKSRole --resources-vpc-config subnetIds=subnet-abc123,subnet-def456 matches the correct syntax exactly. Options A and D use incorrect flags (--cluster-name,--role). aws eks create-cluster --name my-cluster --role-arn arn:aws:iam::123456789012:role/EKSRole --resources-vpc-config subnetIds=subnet-abc123 subnet-def456 misses a comma between subnet IDs.Final Answer:
aws eks create-cluster --name my-cluster --role-arn arn:aws:iam::123456789012:role/EKSRole --resources-vpc-config subnetIds=subnet-abc123,subnet-def456 -> Option CQuick Check:
Correct CLI syntax = aws eks create-cluster --name my-cluster --role-arn arn:aws:iam::123456789012:role/EKSRole --resources-vpc-config subnetIds=subnet-abc123,subnet-def456 [OK]
Quick Trick: Use --name, --role-arn, and comma-separated subnetIds [OK]
Common Mistakes:
- Using --role instead of --role-arn
- Missing commas between subnet IDs
- Using wrong flag names like --cluster-name
Master "EKS" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes