A parks agent may read park calendars through tools but must never modify billing systems. Which control best enforces that boundary?
Select an answer to reveal the explanation.
Short Explanation
Park staff keys open the calendar closet, not the cashier drawer—IAM should mirror that. Least privilege lets tools read calendars and blocks billing writes. Trusting a model’s polite promise without IAM is not a control.
Full Explanation
Parks agents allowed to read park calendars but forbidden from modifying billing systems need enforceable least-privilege IAM permissions and resource boundaries: tools may call calendar read APIs and must lack billing write actions. Identity and access controls—not prose—define the boundary for municipal agent tools so a scheduling assistant cannot touch cashier systems. Giving the agent AdministratorAccess to simplify troubleshooting violates least privilege and invites catastrophic misuse across account resources beyond parks. Putting billing write credentials in the prompt for “emergency overrides” exposes secrets to the model and logs and bypasses IAM entirely. Relying on the FM’s verbal promise not to call billing APIs without IAM enforcement is not a control; models can be prompted or tool-routed incorrectly under pressure. Exam caveat: resource-boundary stems require IAM least privilege—prompt promises and emergency credential stuffing are not authorization. Operational check: attach narrow roles to tool execution principals, deny billing write APIs explicitly in IAM, test that billing calls fail closed in staging, rotate any credentials outside prompts, and review CloudTrail for unexpected API attempts from the agent role.