Claude Certified Architect – Foundations Practice Question 86: Effort Parameter Latency
Claude Certified Architect, Foundations · Test 9 · question 6 of 10
A company runs a high-volume FAQ assistant on a current Claude model. Most questions are simple lookups, and users complain about response time while finance complains about token spend. Quality is acceptable, and the team wants a single request-level setting that makes Claude spend fewer tokens on thinking and responding. Which change is most appropriate?
Show answer and explanation
Answer:
A is correct. The effort parameter (output_config.effort) trades thoroughness for token efficiency across all output tokens: text, tool calls and thinking. Lower levels give significant token savings for simpler, latency-sensitive work, with some capability reduction, so the change should be validated on the team's own evals. Where adaptive thinking is available, effort is the recommended way to control thinking depth.
B is wrong because a large thinking budget does not speed anything up, and manual budget_tokens thinking is not supported on Claude 4.7 and later models. C is wrong because max_tokens is a hard cutoff, not a hint: the answer is truncated rather than made more concise. D is wrong because batch processing is asynchronous and trades latency for a discount, so it would make users wait longer.
Reference: Effort - Claude API Docs