Free Practice Questions for Microsoft AB-731 Exam

For a product showcase website, the highest-impact, most directly relevant generative AI benefit is content creation at scale—producing consistent, high-quality product copy quickly. Option D matches a core generative AI capability: turning structured inputs (specifications such as dimensions, materials, features, compatibility, and use cases) into natural-language descriptions that are readable, persuasive, and formatted for web publishing. This accelerates catalog onboarding, reduces manual writing effort, and helps maintain a consistent tone and structure across thousands of SKUs.

Option A (translation) is also something generative AI can do, but it is a narrower, secondary capability compared to the primary website need: generating product copy from specs. Option B is predictive/analytical AI rather than generative content creation. Option C is plausible in ideation, but the scenario is about showcasing existing products, not inventing new ones. Therefore, D is the best answer because it aligns directly with the project’s core workflow (product specs → publishable descriptions) and delivers measurable business value through speed, consistency, and reduced content production costs.

Microsoft Foundry is positioned as a unified, enterprise-grade platform that helps organizations build, deploy, scale, and govern AI apps and agents—especially generative AI solutions that need to work with business context and internal data. That directly aligns with A: Foundry provides a scalable platform for developing and deploying generative AI solutions. Microsoft describes Foundry as an interoperable platform that makes it easier to build, deploy, and scale AI apps and agents, while also providing centralized security and governance features for organizations.

B is incorrect because Foundry does not remove model choice/configuration; in fact, it supports selecting among models and using tools/frameworks to build solutions. You still choose appropriate model(s), configure endpoints, and design grounding and safety controls.

C and D are not the best characterization of Foundry’s primary benefit. While Foundry offers “friendly interfaces,” Microsoft primarily positions it for developers, model builders, and enterprise AI operations—not as a low-code platform for business users (that role is more commonly filled by Copilot Studio/Power Platform).

This scenario is a clear violation of the fairness principle. Fairness in Microsoft’s Responsible AI framework is about ensuring AI systems do not create unjustified bias or discriminatory outcomes—especially when decisions affect people’s access to opportunities such as credit, employment, housing, or education. A rule or learned behavior that rejects all applicants over a certain age creates a systematic, categorical disadvantage for a protected demographic group and indicates a discriminatory decision boundary rather than an individualized assessment of creditworthiness.

Even if the model designers believed age correlates with risk, using a hard cutoff that rejects every applicant older than 60 is not an equitable approach. It suggests the model is either using age directly as a dominant feature or reflects biased training data/labels that encoded discriminatory outcomes. Fairness requires you to evaluate model outcomes across groups (for example, age brackets), measure disparate impact, and apply mitigations such as feature review (removing or constraining sensitive attributes), rebalancing training data, adjusting thresholds, or using fairness-aware training/evaluation methods. It also requires governance and review of high-stakes automated decisions.

The other principles are not the best match: transparency concerns explainability and user understanding, accountability concerns human oversight and ownership, and reliability and safety concerns consistent and safe operation. The core issue here is discriminatory treatment across an age group—fairness.

guide AI strategy, ensure responsible AI oversight, and promote alignment across business units.

A trustworthy AI program requires more than technical implementation; it requires enterprise governance: clear ownership, risk management, policy, and cross-functional coordination. An AI governance council’s primary role is to provide strategic direction and oversight so AI initiatives align with business goals while meeting Responsible/Trustworthy AI expectations (fairness, reliability and safety, privacy and security, transparency, accountability, and inclusiveness).

Therefore, the best completion is that the council should guide AI strategy, ensure responsible AI oversight, and promote alignment across business units. This captures why councils are created: to avoid siloed deployments, define guardrails and approval processes, standardize evaluation/monitoring practices, and coordinate stakeholders such as legal, compliance, security, data governance, HR, and business leadership. The council also helps prioritize use cases, establish policies for data use and access, set documentation requirements, and require ongoing monitoring and incident response for AI systems in production.

The other options are narrower operational responsibilities. Configuring and deploying models in Azure is typically owned by engineering/cloud teams. Day-to-day model training and labeling is handled by data science/ML teams. The council sits above those activities to ensure the organization’s AI work is consistent, accountable, and strategically aligned.

To align an AI customer support agent with Microsoft’s Responsible AI principles, two high-impact actions are fairness/inclusiveness validation and transparency to users. B is correct because testing for inclusive and culturally sensitive responses directly supports fairness and helps reduce harm. In practice, you evaluate responses across diverse user personas, languages/dialects, accessibility scenarios, and sensitive contexts. You look for biased assumptions, stereotyping, exclusionary language, and disparate quality of service. This also implies ongoing monitoring because model behavior can drift as prompts, knowledge sources, and user inputs evolve.

E is correct because a clear disclaimer supports transparency: customers should know they are interacting with an AI system, understand the type of assistance it can provide, and know what to do if the response is incorrect or they need a human. A disclosure is also a practical risk-control that reduces overreliance and sets expectations about limitations.

The other options are not best for Responsible AI alignment: A (retain all conversations) can conflict with privacy/data minimization; retention must be justified and governed, not automatic. C (operate independently) undermines accountability and human oversight. D (multiple purposes) increases scope and risk rather than improving responsible use.

model inaccuracy

The scenario describes a model producing plausible-sounding content that is factually wrong—a common generative AI failure mode often referred to as a “hallucination.” Since “hallucination” is not offered in the dropdown, the best matching choice is model inaccuracy because the core problem is that the model’s output is incorrect even though it appears confident and coherent.

The other options do not fit the definition of the behavior: data leakage is about sensitive information being exposed (for example, proprietary prompts, secrets, or personal data). Prompt injection is an attack technique where a user tries to override system instructions or cause unsafe actions. Overreliance describes a human/organizational risk —trusting the model too much—rather than the model’s intrinsic behavior of generating incorrect facts. Overreliance can be a consequence of this behavior, but it is not what the behavior itself is called.

In practice, you mitigate this kind of inaccuracy by grounding responses in trusted sources (for example, RAG), constraining prompts with explicit requirements, using verification steps (citations, cross-checking, tool-based validation), and adding human review for high-impact use cases.

Most generative AI language model pricing is based on token consumption, which measures the amount of text processed by the model. Tokens are sub-word units used internally by language models (for example, parts of words, whole words, or punctuation). When you send a prompt, the model consumes input tokens (your prompt + any system instructions + retrieved grounding context). When it generates a response, it consumes output tokens (the generated completion). Costs typically scale with the total input + output tokens processed, which is why long prompts, large grounding passages, and lengthy responses increase spend. This also explains why prompt optimization, response length limits, caching, and careful grounding are common cost-control techniques in enterprise solutions.

By contrast, “documents” is too coarse (a document can be 1 page or 500 pages). “Requests” is not the primary unit for most LLM pricing models because request sizes vary dramatically. “Words” is not used because the model’s actual compute unit is tokens, and tokenization differs across languages and text patterns. Therefore, the most accurate completion is tokens.

Answer Area

A text-to-image generator can be used to translate content into other languages. Answer: No

A predictive analytics model can generate new marketing content for a company’s online ads. Answer: No

A generative AI chatbot can engage customers in personalized conversations and recommend products. Answer: Yes

No — A text-to-image generator’s primary function is to create images from text prompts , not translate text between languages. Translation is a natural language processing task typically handled by language models or dedicated translation services. A text-to-image model could illustrate translated content (e.g., generate an image based on a translated prompt), but it is not the tool used to perform the translation itself.

No — Predictive analytics models are designed to predict outcomes (forecasts, probabilities, classifications) from historical patterns, such as predicting click-through rate, churn, or next-quarter demand. They are not designed to create new ad copy or marketing creatives. Generating new marketing content is a generative AI capability (text generation), not predictive analytics.

Yes — A generative AI chatbot is well-suited to interactive, natural-language conversations . With access to product catalogs and business rules, it can ask clarifying questions, tailor responses to customer needs, and recommend products (for example, suggesting tents based on group size, season, and budget). This combines conversational generation with retrieval/recommendation logic behind the scenes, enabling personalized customer engagement at scale.