A developer manages an Amazon API Gateway REST API used by customers via a frontend UI with Amazon Cognito authentication. The developer has a new API version that introduces new endpoints and includes breaking interface changes. The developer needs to give other team developers beta access to the new API without impacting existing customers. Which approach accomplishes this with the LEAST operational overhead?

Creating a development stage on the existing API Gateway API is the most efficient solution. API Gateway stages are designed precisely for this scenario, allowing different versions of an API to coexist under the same API ID but with distinct endpoints. This isolates the beta version for developers without affecting the production stage used by customers, minimizing operational overhead as it reuses the existing API Gateway configuration. Creating a separate API Gateway API would incur more operational overhead due to managing an entirely new API Gateway instance. Adding a query parameter to the application code would require changes to the backend logic for versioning, which is less ideal than using API Gateway's built-in staging features. Creating new API Gateway endpoints only for new features doesn't address the breaking changes to existing endpoints, which also need to be tested in isolation.