An ops lead asks whether adopting serverless means the city has no security responsibility. What is the correct fundamentals distinction?
Select an answer to reveal the explanation.
Short Explanation
Handing off the kitchen does not mean the recipe can be reckless. The provider locks the building and maintains the stoves; the city still owns whether the chat-bot code and citizen data are handled safely. Serverless is not a “no security” free pass.
Full Explanation
Shared responsibility continues under serverless. The provider manages the underlying platform, while the customer remains accountable for application code, configuration, identity choices, and data protection appropriate to the workload. Defining serverless as “no customer security responsibility” confuses platform abstraction with elimination of security duties—an error AZ-900 expects candidates to avoid.