A developer wants GitHub Copilot CLI to remember billing-specific conventions, but they add the guidance as a root-level instruction file. The same repository also contains mobile, infrastructure, and analytics code. Which change best scopes the agent memory to the relevant task area? Select one answer.
cd ~/work/commerce-platform
cat > .github/copilot-instructions.md <<'EOF'
Use the billing rounding matrix in packages/billing/docs/rounding.md.
Prefer billing test fixtures from packages/billing/test-fixtures.
Use invoice-state terminology in all generated summaries.
Do not suggest changes outside the billing migration plan.
EOF
copilot
# Prompt:
# Update the mobile analytics event schema for checkout screen views.Choose an answer
Tap an option to check your answer.
Correct answer: Move billing guidance to path-specific instructions.
Why this is the answer
Moving the billing guidance to path-specific instructions (e.g., packages/billing/.copilot-instructions.md) is the best solution because it scopes the agent's memory to the relevant task area. GitHub Copilot CLI will then apply these instructions only when the current working directory or relevant files are within the packages/billing path, preventing the billing-specific rules from interfering with suggestions for mobile, infrastructure, or analytics code. Adding billing notes to every prompt is inefficient and clutters prompts. Disabling all repository instructions would remove useful context for all areas. Adding billing notes to personal instructions would apply them globally, again causing irrelevant suggestions outside the billing domain.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed