API deployment and stages in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new API deployment in AWS API Gateway.

AWS

aws apigateway create-deployment --rest-api-id [1] --stage-name prod

Drag options to blanks, or click blank then click option'

Aapi-123abc

Bdeployment-456def

Cstage-prod

Dlambda-function

Attempts:

3 left

💡 Hint

Common Mistakes

Using deployment ID instead of API ID

Using stage name instead of API ID

The --rest-api-id parameter requires the API's ID, such as 'api-123abc'.

2fill in blank

medium

Complete the code to create a new stage named 'dev' for an existing deployment.

AWS

aws apigateway create-stage --rest-api-id api-123abc --stage-name [1] --deployment-id dep-789xyz

Drag options to blanks, or click blank then click option'

Aprod

Bdev

Ctest

Drelease

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'prod' instead of 'dev'

Using deployment ID as stage name

The --stage-name parameter specifies the name of the stage, here 'dev'.

3fill in blank

hard

Fix the error in the command to deploy an API stage with a description.

AWS

aws apigateway create-deployment --rest-api-id api-123abc --stage-name [1] --description "[2]"

Drag options to blanks, or click blank then click option'

Aproduction deployment

Bdev

Cprod

Ddevelopment deployment

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'dev' stage name with production description

Mismatching stage and description

The --stage-name should be 'prod' to match the description of a production deployment.

4fill in blank

hard

Fill both blanks to create a deployment and assign it to the 'test' stage with a description.

AWS

aws apigateway create-deployment --rest-api-id [1] --stage-name [2] --description "Test deployment"

Drag options to blanks, or click blank then click option'

Aapi-456def

Bprod

Ctest

Ddev

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up stage names

Using wrong API ID

The API ID is 'api-456def' and the stage name is 'test' for this deployment.

5fill in blank

hard

Fill all three blanks to update the stage description and enable cache for the 'prod' stage.

AWS

aws apigateway update-stage --rest-api-id [1] --stage-name [2] --patch-operations op=replace,path=/cacheClusterEnabled,value=[3]

Drag options to blanks, or click blank then click option'

Aapi-789ghi

Bprod

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'false' instead of 'true' to enable cache

Wrong stage name or API ID

The command updates the 'prod' stage of API 'api-789ghi' to enable cache by setting value to 'true'.

Practice

1. What is the main purpose of an API stage in AWS API Gateway?

easy

A. To monitor network traffic outside AWS

B. To store API keys for users

C. To create backend Lambda functions

D. To manage different versions or environments of the API

Solution

1. Step 1: Understand API stages concept

   API stages in AWS API Gateway represent different versions or environments like development, testing, or production.

2. Step 2: Identify the role of stages

   Stages allow you to deploy and manage separate API versions independently.

3. Final Answer:

   To manage different versions or environments of the API -> Option D

4. Quick Check:

   API stages = version/environment management [OK]

Hint: Stages separate API versions or environments [OK]

Common Mistakes:

• Confusing stages with API keys
• Thinking stages create backend functions
• Assuming stages monitor external traffic

2. Which AWS CLI command is used to create a new deployment for an API Gateway REST API?

easy

A. aws apigateway create-deployment

B. aws apigateway create-stage

C. aws apigateway deploy-api

D. aws apigateway new-deployment

Solution

1. Step 1: Identify the correct AWS CLI command for deployment

   The command to create a deployment in API Gateway is create-deployment.

2. Step 2: Differentiate from other commands

   create-stage creates a stage, not a deployment. Other options are invalid commands.

3. Final Answer:

   aws apigateway create-deployment -> Option A

4. Quick Check:

   Deployment command = create-deployment [OK]

Hint: Deploy with 'create-deployment' command [OK]

Common Mistakes:

• Using create-stage instead of create-deployment
• Assuming deploy-api is a valid command
• Confusing deployment with stage creation

3. Given the following AWS CLI command:
aws apigateway create-stage --rest-api-id abc123 --stage-name prod --deployment-id dep456
What does this command do?

medium

A. Creates a new deployment named 'prod' for API 'abc123'

B. Creates a new stage 'prod' linked to deployment 'dep456' for API 'abc123'

C. Deletes the stage 'prod' from API 'abc123'

D. Updates the deployment 'dep456' with stage 'prod'

Solution

1. Step 1: Analyze the command parameters

   The command is create-stage with parameters for API ID, stage name, and deployment ID.

2. Step 2: Understand the effect of create-stage

   This creates a new stage named 'prod' that points to the deployment 'dep456' for the API 'abc123'.

3. Final Answer:

   Creates a new stage 'prod' linked to deployment 'dep456' for API 'abc123' -> Option B

4. Quick Check:

   create-stage + deployment-id = new stage linked to deployment [OK]

Hint: create-stage links stage to deployment by deployment-id [OK]

Common Mistakes:

• Confusing stage creation with deployment creation
• Thinking it deletes or updates instead
• Mixing up stage name and deployment ID

4. You ran this command to deploy your API stage:
aws apigateway create-stage --rest-api-id abc123 --stage-name test --deployment-id dep789
But you get an error saying the deployment ID does not exist. What is the likely cause?

medium

A. The deployment ID 'dep789' was not created before creating the stage

B. The stage name 'test' is invalid

C. The rest-api-id 'abc123' is incorrect format

D. You must create the stage before creating the deployment

Solution

1. Step 1: Understand the dependency between deployment and stage

   A stage must point to an existing deployment. If deployment ID does not exist, stage creation fails.

2. Step 2: Identify the error cause

   The error indicates deployment 'dep789' was not created or is invalid before stage creation.

3. Final Answer:

   The deployment ID 'dep789' was not created before creating the stage -> Option A

4. Quick Check:

   Stage needs existing deployment ID [OK]

Hint: Create deployment before stage with deployment ID [OK]

Common Mistakes:

• Assuming stage name format causes error
• Thinking API ID format is the issue
• Believing stage must be created before deployment

5. You want to deploy a new version of your API to a 'prod' stage without affecting the current live API. Which sequence of AWS CLI commands should you use?

hard

A. aws apigateway create-deployment -> aws apigateway create-stage with 'prod'

B. aws apigateway create-stage with 'prod' -> aws apigateway create-deployment

C. aws apigateway create-deployment -> aws apigateway update-stage with 'prod'

D. aws apigateway update-stage with 'prod' -> aws apigateway create-deployment

Solution

1. Step 1: Deploy new API version

   First, create a new deployment to capture the latest API changes.

2. Step 2: Update existing 'prod' stage to point to new deployment

   Use update-stage to switch the 'prod' stage to the new deployment without creating a new stage.

3. Final Answer:

   aws apigateway create-deployment -> aws apigateway update-stage with 'prod' -> Option C

4. Quick Check:

   Deploy then update stage to switch versions [OK]

Hint: Create deployment then update existing stage [OK]

Common Mistakes:

• Creating a new stage instead of updating existing
• Updating stage before deployment exists
• Assuming create-stage can update existing stage