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?
Suggested Answer: B
Get Premium DVA-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
22 comments · newest first
TH
Theodora
11 months ago
I disagree, C adds unnecessary steps.
TR
Trina
11 months ago
Surprised that no one mentioned the cost implications!
FA
Fannie
11 months ago
A is way too complicated for just testing.
GR
Gracia
12 months ago
I think D could work too, but it feels a bit clunky.
RH
Rhea
12 months ago
Option B seems the most straightforward.
LO
Loreen
12 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.
RO
Ronald
1 year 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.
SE
Sena
1 year 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.
GL
Glendora
1 year 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.
VI
Virgina
1 year 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.
YA
Yan
1 year 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.
BE
Bethanie
1 year 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.
BR
Brandee
1 year 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.
JA
Jacquline
1 year ago
"Redirect" seems like the logical choice here. I'm feeling good about selecting that for the exam.
JA
Janine
1 year 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.
KA
Karan
1 year 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.
MI
Miesha
3 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.
SH
Sharee
3 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.
EL
Elena
3 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.
PE
Penney
3 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.
LE
Leonie
3 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.
HO
Honey
3 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.