The staging slot for a clerk-office web app must keep ENVIRONMENT=qa and a QA database connection through a swap so production never points at QA. How should the developer mark those app settings?
Select an answer to reveal the explanation.
Short Explanation
Sticky settings are name tags taped to the slot, not the luggage. Mark ENVIRONMENT and the QA connection sticky and they stay on staging when content swaps. If they ride with the swap, production suddenly talks to QA—bad day at the clerk office.
Full Explanation
Deployment slot sticky settings remain associated with a specific slot during swap; non-sticky settings move with the content. Database connection strings and environment markers that must differ per slot should be sticky. local.settings.json applies to Functions local development, not App Service slot stickiness.