A township uses one OpenAPI definition for its business-license API across environments, but each stage must call a different backend. How should that be deployed?
Select an answer to reveal the explanation.
Short Explanation
One blueprint, three job sites—different lumber suppliers on each lot. Keep the OpenAPI contract shared, then point each API Gateway stage at its own backend. Three drifting specs or everyone hitting prod is how towns get surprises.
Full Explanation
Deploying API resources across environments typically keeps a shared OpenAPI (or equivalent) definition while using API Gateway stages and stage-specific settings—such as stage variables or per-stage integrations—to target the correct backends. Divergent unmanaged contracts and single-prod-only approaches undermine consistent environment testing and promote accidental production coupling.