Exam AWS Certified Developer - Associate DVA-C02 topic 1 question 21 discussion

Option A is the correct solution to meet the requirements with the least operational overhead. Defining a development stage on the API Gateway API enables other developers to test the new version of the API without affecting the production environment. This approach allows the developers to work on the new version of the API independently and avoid conflicts with the production environment. The other options involve creating a new API or new endpoints, which could introduce additional operational overhead, such as managing multiple APIs or endpoints, configuring access control, and updating the frontend UI to point to the new endpoints or API. Option C also introduces additional complexity by requiring the implementation of a query parameter to determine which code version to call.

A is correct. DEV/SIT/QA/STG/PT are shared env before release to PROD

A) Correct - The developer can deploy the new version of the API to a development stage while keeping the existing API in the production stage for customers. Beta users (team developers) can use the unique URL of the development stage to access the new API version. B) Eliminated - This involves duplicating the API Gateway setup and potentially managing additional resources C) Eliminated - This requires modifying the application logic, which increases the development effort and complexity. - Add complexity and operational overhead. D) Eliminated - The goal is to let beta users test the new API without affecting existing customers. Mixing endpoints in the same API Gateway does not provide a clean separation, which increases the risk of customer impact.

keyword: LEAST operational overhead, backward-incompatible, beta access to other developers on the team without affecting customers.(separate) ==> Discard B: take effort to operation and maintain many API gateway instances ==> Discard C: It is not separate API production and beta, make effort to understand, transfer, or fixing something when misunderstading. Violate backward-incompitable, when new version can also use old endpoint version 100% (just adding, not delete or modify) ==> Discard D: like a bit with C, mixing 2 environment prod and beta,

A is correct as the Q asked for 'with the LEAST operational overhead' C got less operation than B but more than A

It is A you chutiyas

This question was on my exam July 23rd, 2024. Answer is A

A is the correct answer.

B ra unga amma

The correct answer is A (development stage). You can configure a development stage for your API Gateway API and then integrate it with the new version of the backend functionality that has new endpoints and backward-incompatible interface changes. The customers can continue to use the existing API.

The option that meets the requirements with the least operational overhead is: B. Define a new API Gateway API that points to the new API application code. Instruct the other developers to point the endpoints to the new API. Here's why: A. Defining a development stage on the existing API Gateway API could potentially affect customers if not managed properly. It might introduce changes or issues to the existing API that customers are using. C. Implementing a query parameter in the API application code to determine the code version introduces complexity and potential risk, as it requires changes to the application code itself. It also doesn't isolate the beta access from the main API. D. Specifying new API Gateway endpoints for the new API endpoints adds complexity and overhead. It requires managing multiple endpoints, potentially affecting the API's simplicity and increasing maintenance overhead.

A is answer

LEAST operational overhead would be B.

The stages gives the capacity to tests a new version in an APIg without affecting customers in others stages

The best practice is to define a development stage.

Option A is the right answer. Defining a development stage on the API Gateway API would provide other developers with a way to test the newer version of the API without affecting prod. The rest of the options would create a lot of operational overhead.

The developer should define a development stage on the API Gateway API. They should then instruct the other developers to point the endpoints to the development stage. This solution will meet the requirements with the least operational overhead