Amazon Exam DVA-C02 Topic 1 Question 19 Discussion

Actual exam question for Amazon's DVA-C02 exam

Question #: 19
Topic #: 1

A developer wants to add request validation to a production environment Amazon API Gateway API. The developer needs to test the changes

before the API is deployed to the production environment. For the test, the developer will send test requests to the API through a testing tool.

Which solution will meet these requirements with the LEAST operational overhead?

AExport the existing API to an OpenAPI file. Create a new API. Import the OpenAPI file. Modify the new API to add request validation. Perform the tests. Modify the existing API to add request validation. Deploy the existing API to production.

BModify the existing API to add request validation. Deploy the updated API to a new API Gateway stage. Perform the tests. Deploy the updated API to the API Gateway production stage.

CCreate a new API. Add the necessary resources and methods, including new request validation. Perform the tests. Modify the existing API to add request validation. Deploy the existing API to production.

DClone the existing API. Modify the new API to add request validation. Perform the tests. Modify the existing API to add request validation. Deploy the existing API to production.

Show Suggested Answer

Suggested Answer: B

Amazon API Gateway allows you to create, deploy, and manage a RESTful API to expose backend HTTP endpoints, AWS Lambda functions, or other AWS services1.You can use API Gateway to perform basic validation of an API request before proceeding with the integration request1.When the validation fails, API Gateway immediately fails the request, returns a 400 error response to the caller, and publishes the validation results in CloudWatch Logs1.

To test changes before deploying to a production environment, you can modify the existing API to add request validation and deploy the updated API to a new API Gateway stage1. This allows you to perform tests without affecting the production environment.Once testing is complete and successful, you can then deploy the updated API to the API Gateway production stage1.

This approach has the least operational overhead as it avoids unnecessary creation of new APIs or exporting and importing of APIs.It leverages the existing infrastructure and only requires changes in the configuration of the existing API1.

by Lili at Jan 25, 2024, 10:40 PM

Limited Time Offer

25%

Off

Get Premium DVA-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Miesha

8 months ago

Hmm, I'm not convinced. What if we run into issues with the new stage? I think option A might be the best compromise - we can create a new API, test the changes, and then update the production API. That way, we have a clear separation between the test and production environments.

upvoted 0 times

...

Sharee

8 months ago

I'm not so sure about that, Elena. Cloning the API sounds like a lot of extra work, and we might end up with some synchronization issues between the two versions. I think option B is the way to go - it's straightforward and minimizes the risk.

upvoted 0 times

...

Elena

8 months ago

I see what you mean, Honey. But option D also seems promising - cloning the API and testing the changes on the clone could work well too. That way, we don't have to worry about modifying the production API at all.

upvoted 0 times

Penney

8 months ago

D) Clone the existing API. Modify the new API to add request validation. Perform the tests. Modify the existing API to add request validation. Deploy the existing API to production.

upvoted 0 times

...

Leonie

8 months ago

B) Modify the existing API to add request validation. Deploy the updated API to a new API Gateway stage. Perform the tests. Deploy the updated API to the API Gateway production stage.

upvoted 0 times

...

Honey

8 months ago

Hmm, this is a tricky one. I don't want to risk breaking the production API, so I'm leaning towards option B. Modifying the existing API and deploying to a new stage seems like the safest approach. That way, we can test the changes without impacting the live API.

upvoted 0 times

...