A two-person team must ship a Claude-backed summarisation service in three weeks. They are deciding between calling the Messages API over plain HTTP with a hand-written client and using the official SDK for their language. Their stated constraints are the three-week deadline and a requirement that request and response handling be covered by the same maintenance as the rest of their dependencies. Select TWO sound reasons to take the SDK.
- AThe SDK wraps the same REST endpoints and already implements request construction, response parsing and retry handling that the team would otherwise write and test itself. Correct
- BThe SDK removes the need to design the prompt or decide which model to call, because those choices are made inside the client library on the team's behalf.
- CThe SDK is versioned and installed through the team's existing package manager, so upgrades and security fixes follow the dependency process they already run. Correct
- DThe SDK opens a persistent connection to the service for the lifetime of the process, which a client written against plain HTTP cannot be made to do.
- EThe SDK guarantees that responses never need validating in the application, because everything it returns has already been checked against the team's own schema.
Why A is correct: Correct: an SDK is a maintained client over the published REST surface, so the boilerplate the deadline does not allow for is already written and exercised by other users.
Why B is wrong: Tempting because the SDK does supply sensible defaults, but prompt design and model choice stay application decisions the team must make and own.
Why C is correct: Correct: this satisfies the stated maintenance requirement directly, since the client is tracked and upgraded like any other pinned dependency.
Why D is wrong: Tempting because connection reuse is a real performance concern, but any competent HTTP client can pool connections, so this is not an SDK-only capability.
Why E is wrong: Tempting because the SDK does give typed responses, but it knows nothing of the team's schema, so validating generated content remains the application's job.