Amazon DVA-C02 Exam - 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

Theodora

3 months ago

I disagree, C adds unnecessary steps.

upvoted 0 times

...

Trina

3 months ago

Surprised that no one mentioned the cost implications!

upvoted 0 times

...

Fannie

4 months ago

A is way too complicated for just testing.

upvoted 0 times

...

Gracia

4 months ago

I think D could work too, but it feels a bit clunky.

upvoted 0 times

...

Rhea

4 months ago

Option B seems the most straightforward.

upvoted 0 times

...

Loreen

4 months ago

I vaguely recall that creating a new API from scratch, as in option C, could lead to more issues down the line. It seems like it would be better to just update the existing one and test it in a new stage.

upvoted 0 times

...

Ronald

4 months ago

I practiced a similar question where we had to test changes in an API. I think cloning the API, like in option D, could work, but it might still involve more steps than necessary.

upvoted 0 times

...

Sena

4 months ago

I'm not entirely sure, but I feel like option A could be too complicated. Exporting and importing an OpenAPI file seems like it would take more time than just modifying the existing API directly.

upvoted 0 times

...

Glendora

5 months ago

I remember we discussed the importance of minimizing operational overhead in our last study session. I think option B might be the best choice since it allows testing in a new stage without creating a whole new API.

upvoted 0 times

...

Virgina

5 months ago

This is a tricky one. I'm tempted to go with Option A, since it seems the most straightforward, but I'm worried about the extra steps involved in creating a new API and then modifying the existing one. I'll need to weigh the trade-offs carefully.

upvoted 0 times

...

Yan

5 months ago

Hmm, I'm a bit confused by the wording of the question. It's asking for the solution with the "least operational overhead," but I'm not sure exactly what that means in this context. I'll need to think through the pros and cons of each approach.

upvoted 0 times

...

Bethanie

5 months ago

This seems like a straightforward question, but I want to make sure I understand the requirements correctly. I'll need to carefully read through each option and think about the operational overhead involved.

upvoted 0 times

...

Brandee

5 months ago

Okay, I think I've got a handle on this. Option B looks like the way to go - it allows me to test the changes in a new stage before deploying to production, which seems like the lowest-risk approach. I'll make sure to thoroughly test the updated API before promoting it to production.

upvoted 0 times

...

Jacquline

5 months ago

"Redirect" seems like the logical choice here. I'm feeling good about selecting that for the exam.

upvoted 0 times

...

Janine

5 months ago

Okay, I think I've got a good handle on this. The key is to look at the structure and hierarchy of the elements in the panel and match that to the JSON code. I'm feeling confident I can nail this one.

upvoted 0 times

...

Karan

5 months ago

I remember discussing Cisco's sales approach in class. I believe the key is that they take a customer-centric view, looking at the client's business needs and desired outcomes. So I think B is the correct answer here.

upvoted 0 times

...

Miesha

2 years 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

2 years 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

2 years 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

2 years 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

2 years 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

2 years 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

...