Q24 of 60 — CCA Practice Exam

Code Generation with Claude Code

Your team uses Claude Code's Remote Control feature to allow developers to start long-running code generation tasks at their desks and monitor progress from their phones. A senior developer reports that roughly once per week, while reviewing a large refactor from their phone, they switch into an ultraplan session to think through a complex architectural decision — and immediately lose the Remote Control connection. They then have to reconnect and re-establish context. What is the root cause of this disruption, and what is the correct architectural response?

A. The ultraplan session exhausts the token budget reserved for Remote Control, causing a timeout. The fix is to increase --capacity so the server can handle both sessions simultaneously.

B. Both ultraplan and Remote Control compete for the single claude.ai/code interface, and only one can be connected at a time. The fix is to complete or pause Remote Control review before starting an ultraplan session, treating them as mutually exclusive workflows.

C. The network drop from switching apps causes the Remote Control process to exit after the 10-minute outage threshold. The fix is to keep the local claude process alive by pinning it in a background terminal multiplexer.

D. The /remote-control command on VS Code does not support concurrent session features. The fix is to re-launch with claude remote-control server mode and set --spawn=session so a dedicated session is reserved for the developer.