Bird
0
0

Identify the correct AWS CLI command to create a Gateway VPC endpoint for DynamoDB in a specified VPC.

easy📝 Syntax Q3 of 15
DynamoDB - Security and Access Control
Identify the correct AWS CLI command to create a Gateway VPC endpoint for DynamoDB in a specified VPC.
Aaws ec2 create-vpc-endpoint --vpc-id vpc-123abc --service-name com.amazonaws.region.dynamodb --route-table-ids rtb-456def --vpc-endpoint-type Gateway
Baws ec2 create-vpc-endpoint --vpc-id vpc-123abc --service-name com.amazonaws.region.dynamodb --subnet-ids subnet-789ghi --vpc-endpoint-type Interface
Caws dynamodb create-vpc-endpoint --vpc-id vpc-123abc --service-name dynamodb --route-table-ids rtb-456def
Daws ec2 create-vpc-endpoint --vpc-id vpc-123abc --service-name com.amazonaws.region.s3 --route-table-ids rtb-456def --vpc-endpoint-type Gateway
Step-by-Step Solution
Solution:
  1. Step 1: Identify service name and endpoint type

    The service name for DynamoDB VPC endpoint follows the pattern com.amazonaws..dynamodb and uses Gateway endpoint type.
  2. Step 2: Use route table IDs for Gateway endpoints

    Gateway endpoints require specifying route table IDs, not subnet IDs.
  3. Step 3: Validate command syntax

    aws ec2 create-vpc-endpoint --vpc-id vpc-123abc --service-name com.amazonaws.region.dynamodb --route-table-ids rtb-456def --vpc-endpoint-type Gateway correctly uses aws ec2 create-vpc-endpoint with proper parameters for DynamoDB Gateway endpoint.
  4. Final Answer:

    Option A -> Option A
  5. Quick Check:

    Gateway endpoint + route tables + DynamoDB service [OK]
Quick Trick: Gateway endpoints use route tables, not subnets [OK]
Common Mistakes:
MISTAKES
  • Using subnet IDs instead of route table IDs for Gateway endpoints
  • Confusing Interface endpoint with Gateway endpoint
  • Using incorrect service name or AWS CLI command

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More DynamoDB Quizzes