AB-731 Practice Questions

uses reasoning capabilities to generate deep insights based on organizational data and the web.

The sentence is best completed by the option describing Researcher as a research-oriented reasoning agent that combines information from the web and your work data to produce deeper insights. Microsoft describes Researcher as an agent built into Microsoft 365 Copilot to tackle complex, multistep research and to help users gather, analyze, and summarize information from “the web, your work documents, or both,” producing a structured output that supports decision-making. That is exactly what the completion “uses reasoning capabilities to generate deep insights based on organizational data and the web” captures.

The other dropdown options are better matches for different tools/agents: “creates visual dashboards from structured data in Excel and Power BI” is more aligned to BI/reporting workflows; “generates a pivot table and performs time series forecasting” is spreadsheet/analytics functionality; and “performs complex, multi-step, data analysis and code execution tasks over arbitrary datasets” is the hallmark positioning of the Analyst agent (“virtual data scientist”) rather than Researcher. Researcher’s differentiator is deep research across both organizational context and the open web, while Analyst’s differentiator is data analysis and computation .

Answer Area

Prompt engineering changes how a generative AI model was trained. Answer: No

Prompt engineering focuses on designing clear, concise, and context-rich instructions. Answer: Yes

Effective prompt engineering involves maximizing the number of tokens used in each request. Answer: No

No — Prompt engineering does not modify model weights or retrain the model. It is an inference-time technique : you steer outputs by improving the instructions and context you send to the model. Changing how a model was trained would involve pretraining, fine-tuning, or other training methods—separate from prompt engineering.

Yes — The primary goal of prompt engineering is to reduce ambiguity and variability by providing clear instructions , the right context , and explicit output constraints . This often includes specifying role and task, providing necessary facts or grounding text, defining format (bullets, JSON, headings), and adding examples (few-shot) when helpful. Well-constructed prompts improve consistency, relevance, and usefulness of outputs.

No — Good prompt engineering does not mean “use as many tokens as possible.” In fact, using unnecessary tokens can increase cost and may degrade quality by adding noise. Effective prompts are typically as short as possible but as long as necessary : enough context to achieve accuracy and alignment, but not bloated. Token discipline matters because most pricing is token-based and long contexts can dilute attention over what’s most important.