Claude Certified Architect – Foundations Practice Question 34: Permission Rule Precedence
Claude Certified Architect, Foundations · Test 4 · question 4 of 10
An enterprise deploys managed settings to all laptops that include a deny rule for Bash(curl:*). A developer's project .claude/settings.json contains an allow rule for Bash(curl:*), and the developer's user settings also allow it. The developer asks Claude Code to run curl https://example.com. What happens?
Show answer and explanation
Answer:
Claude Code evaluates permission rules in the order deny, then ask, then allow, and the first matching rule wins, so a deny always beats an allow. In addition, managed settings sit at the top of the settings hierarchy and cannot be overridden by user or project settings or by command-line arguments. Both facts lead to the same result: the command is blocked.
A is wrong because specificity of scope does not lift a deny; scope precedence puts managed first. C is wrong because a deny is not a prompt (that is the behavior of an ask rule), so there is no approval step. D is wrong because user settings are lower precedence than managed settings.
Reference: Configure permissions - Claude Code