Correct Answer: D  🗳️

Explanation: Only visible for BraindumpsPrep members. You can sign-up / login (it's free).

Correct Answer: A  🗳️

Explanation: Only visible for BraindumpsPrep members. You can sign-up / login (it's free).

Correct Answer:

Explanation:
tools: [ ' search ' , ' read ' , ' fetch ' ]
send: false
The completed configuration is:
name: planner-agent
description: Planning
tools: [ ' search ' , ' read ' , ' fetch ' ]
handoffs:
- label: Start Implementation
agent: implementer
prompt: Now implement the plan outlined above.
send: false
The planner must be restricted to read-only capabilities, so [ ' search ' , ' read ' , ' fetch ' ] is the correct tool set. search locates repository information, read inspects file contents, and fetch retrieves supporting information without modifying source files. The other available tool combinations contain write-capable operations such as edit, commit, push, merge, or publish, which would violate the requirement that the planner must not alter the repository before approval. VS Code custom agents explicitly support scoping tools so that planning agents can be constrained to research and analysis capabilities.
The send property must be false. A handoff appears as an interactive transition after the planner produces its response. With send: false, selecting the handoff switches to the implementation agent and pre-fills the implementation prompt, but the prompt is not automatically submitted. This provides the necessary human approval gate: the plan can be reviewed before implementation begins. By contrast, send: true immediately submits the handoff prompt after the transition.
Study Guide Reference Topics: agent role separation, least-privilege tool assignment, planning versus execution, multi-agent handoffs, and human approval gates.

Correct Answer:

Explanation:
Target
Selection
Dropdown 1
' search '
Dropdown 2
' read '
The visible configuration describes an implementation planner. Providing search and read supports the information-gathering work needed to produce a technically grounded plan: locating relevant code and inspecting its contents. The listed documentation tools supplement repository context with external technical reference material.
This tool selection also establishes a practical boundary between planning and implementation. A planner can explain proposed changes and produce Markdown in its response without needing permission to modify repository files. Granting editing or command-execution capabilities would expand its authority beyond the visible planning role.
The distinction between generating Markdown and saving a Markdown file is important. The selected tools support producing a plan in conversation. If the requirements instead demanded that the planner write that plan directly into the repository, an appropriate file-writing capability or a separate persistence step would be necessary.
Tool names must also resolve to capabilities available in the configured environment. Merely listing a documentation tool does not install or authenticate its MCP server.
Study-guide topics: tool selection, least-privilege planning, and environment capabilities. Reference: VS Code-Use tools with agents .

Correct Answer: B  🗳️

Explanation: Only visible for BraindumpsPrep members. You can sign-up / login (it's free).