AB-731 Exam Questions 2026 – Practice Test with Answers

Explanation:
The requirement is to analyze text and identify “people, locations, and companies” mentioned in news articles. This is a classic Named Entity Recognition (NER) / entity extraction scenario, which falls under natural language processing. Azure Language in Foundry Tools is the correct choice because it provides text analytics capabilities that detect and categorize entities in unstructured text―commonly including Person, Location, and Organization. This enables downstream experiences such as topic tagging, search filters (e.g., “all articles mentioning Company X”), trend dashboards (top people/places mentioned this week), and improved content discovery.
The other options do not match the requirement. Content Safety focuses on moderating harmful or policy-violating content (for example, hate, violence, self-harm, sexual content) and is not the primary tool for extracting named entities. Azure Vision is for analyzing images and performing OCR; it would only be relevant if the articles were images or scans, but the task here is entity extraction from text articles. Azure Speech is for speech-to-text, text-to-speech, and audio analysis; it would be used if your input were audio recordings rather than written articles. Therefore, to identify key entities (people, locations, companies) from daily news article text, the best recommendation is Azure Language in Foundry Tools.

Explanation:
The correct selections are Yes, Yes, Yes. Lack of trust is a common AI adoption barrier because users and leaders may worry about security, privacy, hallucinations, inaccurate outputs, and unclear accountability. If people do not trust the system, they will avoid using it or over-escalate decisions outside the intended workflow. AI adoption also fails when organizations overlook high-quality data. Poor, outdated, incomplete, or poorly governed data weakens grounding, reduces output quality, and damages user confidence. Finally, adoption is strongest when business and compliance stakeholders are involved early. Business stakeholders ensure the solution solves real problems and delivers measurable value, while compliance, legal, risk, and privacy teams ensure the solution aligns with policy and regulatory obligations.

Explanation:
crafting clear instructions to guide generative AI solutions in generating context-appropriate content.
Prompt engineering is fundamentally about how you communicate intent to a generative AI model so it produces outputs that meet business expectations. The best completion is “crafting clear instructions to guide generative AI solutions in generating context-appropriate content” because it captures the practical, day-to-day discipline: shaping the input (prompt) with the right task framing, constraints, context, and output format.
In real deployments, prompt engineering includes specifying the role and objective (for example, “act as a customer support agent”), providing the necessary context (product details, policy excerpts, audience), adding explicit requirements (tone, length, must/must-not statements), and defining structured output (JSON fields, bullet sections, headings). It can also include adding examples (few-shot prompting), clarifying what to do when information is missing, and instructing the model to cite only provided sources or to ask follow-up questions. These techniques reduce ambiguity, improve consistency, and lower the risk of hallucinations or off-brand responses.
The other options are not accurate definitions. “Integrating AI-powered tools into business workflows” describes solution adoption/integration, not prompt engineering. “Identifying and fixing errors in AI-generated content” is review/editing or quality assurance. “Designing, developing, and training generative AI models” is model development/ML engineering. Prompt engineering operates without changing model weights; it’s about steering model behavior through well-constructed instructions and context.