Advanced Prompting — Vocabulary
Learn advanced prompting vocabulary: tree of thoughts, self-consistency, meta-prompting, A/B testing prompts, prompt leaking, and sycophancy.
0 / 25 completed
1 / 25
What is the 'tree of thoughts' prompting technique?
Tree of Thoughts (ToT) extends chain-of-thought prompting by having the model generate and evaluate several intermediate reasoning steps as branches, selecting the most promising path — useful for complex problem solving that benefits from look-ahead reasoning.
2 / 25
What is 'self-consistency' as an advanced prompting strategy?
Self-consistency involves sampling multiple outputs from the model for the same question, then taking a majority vote or aggregating answers. This reduces the impact of individual stochastic errors, particularly on mathematical and logical reasoning tasks.
3 / 25
What does 'prompt leaking' refer to?
Prompt leaking occurs when a user crafts inputs that cause the model to repeat or expose its hidden system prompt. This is a known attack vector in deployed LLM applications where system prompts contain proprietary instructions or configurations.
4 / 25
What does 'the model is being sycophantic' mean in a prompting context?
Sycophancy in LLMs refers to the tendency to validate the user's beliefs, agree with incorrect statements if the user pushes back, or soften truthful but unwelcome answers. It is a known RLHF-induced behaviour that can undermine accuracy.
5 / 25
What is 'meta-prompting'?
Meta-prompting means using the model to generate, critique, or refine prompts — for example, 'Write an effective prompt for a model that needs to summarise legal documents.' This leverages the model's language understanding to improve prompt quality.
6 / 25
Reviewer: 'The response is overly verbose and doesn't directly address the request. It includes unnecessary details about the user's past interactions with the system.
PR Author: 'I was trying to provide context for better understanding, as the model sometimes struggles without it.'The core issue here isn't simply that context was provided—it's *how* it was provided. While adding context can be helpful, the PR author's justification suggests they were not optimizing the prompt for efficiency. The correct answer acknowledges this point: excessive detail can actually hinder performance by increasing computational load and potentially confusing the model. Providing relevant context is good, but prioritizing directness and conciseness is a key principle of advanced prompting.
7 / 25
Reviewer: 'This function lacks clear intent. The prompt is convoluted and doesn't clearly state what the API call should achieve. It's as if the model is trying to *guess* what I wanted instead of directly fulfilling it.' PR Author: 'I added more detail hoping to guide the model, but perhaps I over-specified.' Which phrase best captures Reviewer's primary concern regarding the prompt?
The reviewer's comment highlights the problem of an unclear or insufficiently focused prompt. They are expressing concern that the prompt doesn't clearly state *what* the API call should achieve – it's not about complexity itself, nor the API's design, but rather a lack of intent. The correct answer reflects this core issue: ambiguity leading to the model guessing instead of directly responding to the desired outcome. Options A and D are too broad; B correctly identifies the ambiguity, and C focuses on the technical aspect which isn't the primary concern here.
8 / 25
Reviewer commented on a PR draft: 'This prompt is exhibiting *hallucination*. It's confidently generating plausible-sounding code examples that are completely unrelated to the requested API endpoint and its intended function. The model seems to be inventing solutions rather than interpreting the specification.' Which of the following best describes what hallucination means in this context?
In the context of large language models and prompt engineering, 'hallucination' refers specifically to the model generating outputs that are factually incorrect or irrelevant to the given input. It's not about creativity; rather, it's a concerning behavior where the model confidently presents false information as if it were true—in this case, inventing code examples instead of correctly interpreting the API request. The key misconception is often equating 'hallucination' with general error correction or creative problem-solving, when it's a more serious issue of fabricated content.
9 / 25
Reviewer: 'The API response is returning a vague error message – 'Unexpected input format'. It doesn't specify *which* part of the request was problematic. The model seems to be avoiding providing actionable feedback.' PR Author: 'I tried to include more descriptive metadata in the prompt, hoping to guide the model towards identifying the specific validation failure.' Which term best describes the PR author's approach?The PR author attempted to improve the API response by adding more context. However, this demonstrates a misunderstanding of 'verbosity' in prompt engineering; simply providing *more* information doesn't guarantee actionable feedback. The core issue is that the model isn't effectively communicating the specific validation failure – 'unexpected input format' requires a precise diagnosis, not just surrounding details. This highlights the importance of prompts focusing on clarity and targeted guidance rather than broad contextualization.
10 / 25
Reviewer: 'The code is returning a JSON response with a `status_code` of 500 and an error message: `Invalid request parameters. Please check your input.' The model isn't explaining *which* parameters are causing the issue, just stating it's invalid. PR Author: 'I added more specific validation instructions to the prompt, detailing the expected data types for each field.' Which phrase best describes the PR author's attempt to improve the response?The PR author's approach – 'clarification' – is accurate. They were trying to address the problem of a vague error message by adding more detailed instructions to the prompt, specifically outlining the expected input parameters and their data types. The incorrect options misinterpret this as simply providing insufficient information or attempting over-engineering; instead, it's about guiding the model towards a more precise interpretation of the request and subsequently generating a more helpful response.
11 / 25
Reviewer: 'The response is overly verbose and doesn't directly address the request. It includes unnecessary details about the user's past interactions with the system.
PR Author: 'I was trying to provide context for better understanding, as the model sometimes struggles without it.'The core issue here isn't simply that context was provided—it's *how* it was provided. While adding context can be helpful, the PR author's justification suggests they were not optimizing the prompt for efficiency. The correct answer acknowledges this point: excessive detail can actually hinder performance by increasing computational load and potentially confusing the model. Providing relevant context is good, but prioritizing directness and conciseness is a key principle of advanced prompting.
12 / 25
Reviewer: 'This function lacks clear intent. The prompt is convoluted and doesn't clearly state what the API call should achieve. It's as if the model is trying to *guess* what I wanted instead of directly fulfilling it.' PR Author: 'I added more detail hoping to guide the model, but perhaps I over-specified.' Which phrase best captures Reviewer's primary concern regarding the prompt?
The reviewer's comment highlights the problem of an unclear or insufficiently focused prompt. They are expressing concern that the prompt doesn't clearly state *what* the API call should achieve – it's not about complexity itself, nor the API's design, but rather a lack of intent. The correct answer reflects this core issue: ambiguity leading to the model guessing instead of directly responding to the desired outcome. Options A and D are too broad; B correctly identifies the ambiguity, and C focuses on the technical aspect which isn't the primary concern here.
13 / 25
Reviewer commented on a PR draft: 'This prompt is exhibiting *hallucination*. It's confidently generating plausible-sounding code examples that are completely unrelated to the requested API endpoint and its intended function. The model seems to be inventing solutions rather than interpreting the specification.' Which of the following best describes what hallucination means in this context?
In the context of large language models and prompt engineering, 'hallucination' refers specifically to the model generating outputs that are factually incorrect or irrelevant to the given input. It's not about creativity; rather, it's a concerning behavior where the model confidently presents false information as if it were true—in this case, inventing code examples instead of correctly interpreting the API request. The key misconception is often equating 'hallucination' with general error correction or creative problem-solving, when it's a more serious issue of fabricated content.
14 / 25
Reviewer: 'The API response is returning a vague error message – 'Unexpected input format'. It doesn't specify *which* part of the request was problematic. The model seems to be avoiding providing actionable feedback.' PR Author: 'I tried to include more descriptive metadata in the prompt, hoping to guide the model towards identifying the specific validation failure.' Which term best describes the PR author's approach?The PR author attempted to improve the API response by adding more context. However, this demonstrates a misunderstanding of 'verbosity' in prompt engineering; simply providing *more* information doesn't guarantee actionable feedback. The core issue is that the model isn't effectively communicating the specific validation failure – 'unexpected input format' requires a precise diagnosis, not just surrounding details. This highlights the importance of prompts focusing on clarity and targeted guidance rather than broad contextualization.
15 / 25
Reviewer: 'The code is returning a JSON response with a `status_code` of 500 and an error message: `Invalid request parameters. Please check your input.' The model isn't explaining *which* parameters are causing the issue, just stating it's invalid. PR Author: 'I added more specific validation instructions to the prompt, detailing the expected data types for each field.' Which phrase best describes the PR author's attempt to improve the response?The PR author's approach – 'clarification' – is accurate. They were trying to address the problem of a vague error message by adding more detailed instructions to the prompt, specifically outlining the expected input parameters and their data types. The incorrect options misinterpret this as simply providing insufficient information or attempting over-engineering; instead, it's about guiding the model towards a more precise interpretation of the request and subsequently generating a more helpful response.
16 / 25
Reviewer: 'The response is overly verbose and doesn't directly address the request. It includes unnecessary details about the user's past interactions with the system.
PR Author: 'I was trying to provide context for better understanding, as the model sometimes struggles without it.'The core issue here isn't simply that context was provided—it's *how* it was provided. While adding context can be helpful, the PR author's justification suggests they were not optimizing the prompt for efficiency. The correct answer acknowledges this point: excessive detail can actually hinder performance by increasing computational load and potentially confusing the model. Providing relevant context is good, but prioritizing directness and conciseness is a key principle of advanced prompting.
17 / 25
Reviewer: 'This function lacks clear intent. The prompt is convoluted and doesn't clearly state what the API call should achieve. It's as if the model is trying to *guess* what I wanted instead of directly fulfilling it.' PR Author: 'I added more detail hoping to guide the model, but perhaps I over-specified.' Which phrase best captures Reviewer's primary concern regarding the prompt?
The reviewer's comment highlights the problem of an unclear or insufficiently focused prompt. They are expressing concern that the prompt doesn't clearly state *what* the API call should achieve – it's not about complexity itself, nor the API's design, but rather a lack of intent. The correct answer reflects this core issue: ambiguity leading to the model guessing instead of directly responding to the desired outcome. Options A and D are too broad; B correctly identifies the ambiguity, and C focuses on the technical aspect which isn't the primary concern here.
18 / 25
Reviewer commented on a PR draft: 'This prompt is exhibiting *hallucination*. It's confidently generating plausible-sounding code examples that are completely unrelated to the requested API endpoint and its intended function. The model seems to be inventing solutions rather than interpreting the specification.' Which of the following best describes what hallucination means in this context?
In the context of large language models and prompt engineering, 'hallucination' refers specifically to the model generating outputs that are factually incorrect or irrelevant to the given input. It's not about creativity; rather, it's a concerning behavior where the model confidently presents false information as if it were true—in this case, inventing code examples instead of correctly interpreting the API request. The key misconception is often equating 'hallucination' with general error correction or creative problem-solving, when it's a more serious issue of fabricated content.
19 / 25
Reviewer: 'The API response is returning a vague error message – 'Unexpected input format'. It doesn't specify *which* part of the request was problematic. The model seems to be avoiding providing actionable feedback.' PR Author: 'I tried to include more descriptive metadata in the prompt, hoping to guide the model towards identifying the specific validation failure.' Which term best describes the PR author's approach?The PR author attempted to improve the API response by adding more context. However, this demonstrates a misunderstanding of 'verbosity' in prompt engineering; simply providing *more* information doesn't guarantee actionable feedback. The core issue is that the model isn't effectively communicating the specific validation failure – 'unexpected input format' requires a precise diagnosis, not just surrounding details. This highlights the importance of prompts focusing on clarity and targeted guidance rather than broad contextualization.
20 / 25
Reviewer: 'The code is returning a JSON response with a `status_code` of 500 and an error message: `Invalid request parameters. Please check your input.' The model isn't explaining *which* parameters are causing the issue, just stating it's invalid. PR Author: 'I added more specific validation instructions to the prompt, detailing the expected data types for each field.' Which phrase best describes the PR author's attempt to improve the response?The PR author's approach – 'clarification' – is accurate. They were trying to address the problem of a vague error message by adding more detailed instructions to the prompt, specifically outlining the expected input parameters and their data types. The incorrect options misinterpret this as simply providing insufficient information or attempting over-engineering; instead, it's about guiding the model towards a more precise interpretation of the request and subsequently generating a more helpful response.
21 / 25
Reviewer: 'The response is overly verbose and doesn't directly address the request. It includes unnecessary details about the user's past interactions with the system.
PR Author: 'I was trying to provide context for better understanding, as the model sometimes struggles without it.'The core issue here isn't simply that context was provided—it's *how* it was provided. While adding context can be helpful, the PR author's justification suggests they were not optimizing the prompt for efficiency. The correct answer acknowledges this point: excessive detail can actually hinder performance by increasing computational load and potentially confusing the model. Providing relevant context is good, but prioritizing directness and conciseness is a key principle of advanced prompting.
22 / 25
Reviewer: 'This function lacks clear intent. The prompt is convoluted and doesn't clearly state what the API call should achieve. It's as if the model is trying to *guess* what I wanted instead of directly fulfilling it.' PR Author: 'I added more detail hoping to guide the model, but perhaps I over-specified.' Which phrase best captures Reviewer's primary concern regarding the prompt?
The reviewer's comment highlights the problem of an unclear or insufficiently focused prompt. They are expressing concern that the prompt doesn't clearly state *what* the API call should achieve – it's not about complexity itself, nor the API's design, but rather a lack of intent. The correct answer reflects this core issue: ambiguity leading to the model guessing instead of directly responding to the desired outcome. Options A and D are too broad; B correctly identifies the ambiguity, and C focuses on the technical aspect which isn't the primary concern here.
23 / 25
Reviewer commented on a PR draft: 'This prompt is exhibiting *hallucination*. It's confidently generating plausible-sounding code examples that are completely unrelated to the requested API endpoint and its intended function. The model seems to be inventing solutions rather than interpreting the specification.' Which of the following best describes what hallucination means in this context?
In the context of large language models and prompt engineering, 'hallucination' refers specifically to the model generating outputs that are factually incorrect or irrelevant to the given input. It's not about creativity; rather, it's a concerning behavior where the model confidently presents false information as if it were true—in this case, inventing code examples instead of correctly interpreting the API request. The key misconception is often equating 'hallucination' with general error correction or creative problem-solving, when it's a more serious issue of fabricated content.
24 / 25
Reviewer: 'The API response is returning a vague error message – 'Unexpected input format'. It doesn't specify *which* part of the request was problematic. The model seems to be avoiding providing actionable feedback.' PR Author: 'I tried to include more descriptive metadata in the prompt, hoping to guide the model towards identifying the specific validation failure.' Which term best describes the PR author's approach?The PR author attempted to improve the API response by adding more context. However, this demonstrates a misunderstanding of 'verbosity' in prompt engineering; simply providing *more* information doesn't guarantee actionable feedback. The core issue is that the model isn't effectively communicating the specific validation failure – 'unexpected input format' requires a precise diagnosis, not just surrounding details. This highlights the importance of prompts focusing on clarity and targeted guidance rather than broad contextualization.
25 / 25
Reviewer: 'The code is returning a JSON response with a `status_code` of 500 and an error message: `Invalid request parameters. Please check your input.' The model isn't explaining *which* parameters are causing the issue, just stating it's invalid. PR Author: 'I added more specific validation instructions to the prompt, detailing the expected data types for each field.' Which phrase best describes the PR author's attempt to improve the response?The PR author's approach – 'clarification' – is accurate. They were trying to address the problem of a vague error message by adding more detailed instructions to the prompt, specifically outlining the expected input parameters and their data types. The incorrect options misinterpret this as simply providing insufficient information or attempting over-engineering; instead, it's about guiding the model towards a more precise interpretation of the request and subsequently generating a more helpful response.
Frequently Asked Questions
What will I practice in "Advanced Prompting — Vocabulary"?
This is an AI Prompting exercise set. It walks through 25 scenario-based multiple-choice questions built around real usage of AI Prompting terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 25 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the AI Prompting vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more AI Prompting exercises?
See the AI Prompting exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — AI Prompting vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.