REST API creation in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a REST API Gateway resource named 'MyApi'.

AWS

aws apigateway create-rest-api --name [1]

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

AMyApi

BTestApi

CSampleApi

DDemoApi

Attempts:

3 left

💡 Hint

Common Mistakes

Using a name different from 'MyApi'.

Omitting the --name parameter.

The command creates a REST API Gateway resource with the specified name. 'MyApi' is the correct name as per the instruction.

2fill in blank

medium

Complete the code to create a resource under the REST API with the path part 'users'.

AWS

aws apigateway create-resource --rest-api-id [1] --parent-id abc123 --path-part users

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

Adef456

Babc123

Cghi012

Dxyz789

Attempts:

3 left

💡 Hint

Common Mistakes

Using the parent ID instead of the API ID.

Using an incorrect API ID.

The REST API ID must be the correct one for the API. 'def456' is the correct ID for this example.

3fill in blank

hard

Fix the error in the command to create a GET method for the 'users' resource.

AWS

aws apigateway put-method --rest-api-id def456 --resource-id [1] --http-method GET --authorization-type NONE

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

Aabc123

Bxyz789

Cdef456

Dghi012

Attempts:

3 left

💡 Hint

Common Mistakes

Using the REST API ID as the resource ID.

Using an unrelated resource ID.

The resource ID must be the ID of the 'users' resource, which is 'xyz789' in this example.

4fill in blank

hard

Fill both blanks to integrate the GET method with a Lambda function named 'UserFunction'.

AWS

aws apigateway put-integration --rest-api-id def456 --resource-id xyz789 --http-method GET --type [1] --integration-http-method [2] --uri arn:aws:apigateway:us-east-1:lambda:path/2015-03-31/functions/arn:aws:lambda:us-east-1:123456789012:function:UserFunction/invocations

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

AAWS_PROXY

BPOST

CAWS

DGET

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'AWS_PROXY' instead of 'AWS' for integration type.

Using 'GET' instead of 'POST' for integration HTTP method.

The integration type for Lambda is 'AWS' and the integration HTTP method is 'POST' because Lambda functions are invoked via POST requests.

5fill in blank

hard

Fill all three blanks to deploy the API to a stage named 'prod' in region 'us-east-1'.

AWS

aws --region [2] apigateway create-deployment --rest-api-id def456 --stage-name [1] --description [3]

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

Adev

Bprod

Cus-east-1

D"Production deployment"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'dev' instead of 'prod' for stage name.

Omitting quotes around the description.

Using wrong region.

The stage name is 'prod', the region is 'us-east-1', and the description is 'Production deployment' to clearly identify the deployment.

Practice

1. What is the main purpose of creating a REST API in AWS?

easy

A. To store large amounts of data securely in the cloud.

B. To allow different applications to communicate over the internet using defined paths and actions.

C. To run virtual machines for hosting websites.

D. To create user accounts and manage permissions.

Solution

1. Step 1: Understand REST API purpose

   REST APIs enable communication between apps using simple commands over the internet.

2. Step 2: Identify AWS REST API role

   In AWS, REST APIs define resources (paths) and methods (actions) to allow this communication.

3. Final Answer:

   To allow different applications to communicate over the internet using defined paths and actions. -> Option B

4. Quick Check:

   REST API = communication interface [OK]

Hint: REST APIs connect apps via internet paths and actions [OK]

Common Mistakes:

• Confusing REST API with data storage services
• Thinking REST API runs virtual machines
• Mixing REST API with user management

2. Which AWS service is primarily used to create REST APIs?

easy

A. Amazon API Gateway

B. AWS Lambda

C. Amazon S3

D. Amazon EC2

Solution

1. Step 1: Identify AWS services for APIs

   Amazon API Gateway is designed to create, publish, and manage REST APIs.

2. Step 2: Differentiate other services

   Amazon S3 stores files, Lambda runs code, EC2 runs servers, but API Gateway manages APIs.

3. Final Answer:

   Amazon API Gateway -> Option A

4. Quick Check:

   API Gateway = REST API service [OK]

Hint: API Gateway is the AWS REST API builder [OK]

Common Mistakes:

• Choosing Lambda as the API creator
• Confusing S3 with API service
• Selecting EC2 for API management

3. Given this API Gateway setup: a resource path /books with a GET method using MOCK integration. What happens when a client sends a GET request to /books?

medium

A. The API fetches book data from a connected database.

B. The API returns an error because MOCK integration is invalid.

C. The API triggers a Lambda function to process the request.

D. The API returns a predefined mock response without calling any backend.

Solution

1. Step 1: Understand MOCK integration

   MOCK integration returns a fixed response defined in API Gateway without backend calls.

2. Step 2: Analyze GET method on /books

   Since GET uses MOCK, the client receives the mock response directly.

3. Final Answer:

   The API returns a predefined mock response without calling any backend. -> Option D

4. Quick Check:

   MOCK integration = fixed response [OK]

Hint: MOCK returns fixed response, no backend called [OK]

Common Mistakes:

• Assuming MOCK calls database or Lambda
• Thinking MOCK integration causes errors
• Confusing MOCK with real backend integration

4. You created a POST method on resource /orders in API Gateway but get a 403 Forbidden error when testing. What is the most likely cause?

medium

A. The MOCK integration is missing a response template.

B. The resource path /orders is misspelled in the client request.

C. The method does not have permission to invoke the backend service.

D. The API Gateway does not support POST methods.

Solution

1. Step 1: Understand 403 Forbidden in API Gateway

   403 usually means permission denied to invoke backend or access resource.

2. Step 2: Check method permissions

   POST method likely lacks permission to call backend service, causing 403 error.

3. Final Answer:

   The method does not have permission to invoke the backend service. -> Option C

4. Quick Check:

   403 = permission denied [OK]

Hint: 403 means permission denied to backend [OK]

Common Mistakes:

• Assuming API Gateway disallows POST
• Blaming client path spelling without checking
• Thinking MOCK integration causes 403

5. You want to create a REST API with a resource /users that supports GET and POST methods. You start with MOCK integration for both methods to test. Later, you want GET to fetch data from a Lambda function and POST to store data in DynamoDB via Lambda. What is the best approach to achieve this?

hard

A. Create the API with MOCK integration first, then update GET and POST methods to use Lambda integration with proper permissions.

B. Create separate APIs for MOCK and Lambda integrations and switch clients between them.

C. Use MOCK integration permanently because it is simpler and faster.

D. Directly connect POST method to DynamoDB without Lambda and keep GET as MOCK.

Solution

1. Step 1: Start with MOCK integration for testing

   MOCK lets you test API behavior without backend, a good first step.

2. Step 2: Update methods to Lambda integration

   Later, replace MOCK with Lambda integration for GET and POST to connect real backend logic.

3. Step 3: Ensure permissions and backend setup

   Configure Lambda permissions and DynamoDB access properly for smooth operation.

4. Final Answer:

   Create the API with MOCK integration first, then update GET and POST methods to use Lambda integration with proper permissions. -> Option A

5. Quick Check:

   Start MOCK, then switch to Lambda integration [OK]

Hint: Test with MOCK, then switch methods to Lambda integration [OK]

Common Mistakes:

• Trying to use MOCK and Lambda in separate APIs
• Keeping MOCK integration permanently
• Connecting POST directly to DynamoDB without Lambda