Back to Amazon API Gateway

API Gateway Import and Export

5 minutes 5 Questions

API Gateway provides import and export features to help you create, manage, and share your APIs' configuration. You can import an existing API definition file in the OpenAPI or Swagger format and create a new REST API or update an existing one. This enables you to bring your existing APIs into API …

Test mode:
Start practice test
AWS Certified Solutions Architect - API Gateway Import and Export Example Questions

Test your knowledge of API Gateway Import and Export

Question 1

When exporting a REST API definition from Amazon API Gateway, which specification versions are supported for export?

Correct Answer: OpenAPI 3.0 and Swagger

Amazon API Gateway supports exporting REST API definitions in the OpenAPI specification, specifically OpenAPI 2.0 (commonly known as Swagger) and OpenAPI 3.0. The exported definitions can be serialized as either JSON or YAML, but those are file formats, not specification versions. Therefore, the option that correctly lists the supported specification versions is "OpenAPI 3.0 and Swagger." The choice "YAML and JSON" names serialization formats, not specs; "OpenAPI 2.0 and JSON" mixes a spec version with a file format and omits OpenAPI 3.0; and "Swagger and RAML" is incorrect because RAML is not supported by API Gateway export.

Question 2

In the AWS Management Console for API Gateway (REST APIs), how do you import an API from an OpenAPI (Swagger) definition?

Correct Answer: Use the 'Import API' option in the console

In the AWS Management Console for API Gateway (REST APIs), you import an API defined in an OpenAPI/Swagger file by selecting the 'Import API' action. This allows you to upload or paste the definition and have API Gateway create the resources and methods automatically. Uploading a file to S3 does not perform an import by itself, manually creating resources is not an import, and the generic action of creating a new API via CLI does not specify the required import operation.

Question 3

You keep your OpenAPI/Swagger definition in source control outside AWS and want reproducible deployments to Amazon API Gateway. What approach should you use?

Correct Answer: Use AWS SAM/CloudFormation and reference the OpenAPI file via DefinitionUri (S3 or packaged locally) to deploy the API to API Gateway.

The most reliable way to manage and version an API definition outside AWS while enabling repeatable deployments is to use Infrastructure as Code. With AWS SAM or CloudFormation, you define an API Gateway resource and reference the external OpenAPI/Swagger file using DefinitionUri (or BodyS3Location). The OpenAPI file remains in source control, SAM/CloudFormation packages it to S3 as needed, and the stack deploys the API consistently across environments. Manually editing the console is not versioned or repeatable, simply uploading a file to S3 does not perform deployment, and a custom Lambda for deployment is unnecessary and brittle compared to native IaC support.

More API Gateway Import and Export questions
18 questions (total)
Start 18 question test