AB-731 Practice Questions

Answer Area

Larger datasets can increase the cost of a generative AI solution that uses an Azure Machine Learning workspace. Answer: Yes

The cost of consuming Azure OpenAI models is primarily identified by the number of input and output tokens processed. Answer: Yes

The cost of custom generative AI solutions always remains the same regardless of the model version or capability used. Answer: No

Yes — In Azure Machine Learning, cost is driven by the resources you consume to store, process, and train. Larger datasets typically require more storage, more data transfer, and more compute time for preprocessing, training, evaluation, and experimentation. Even if you are not training foundation models, handling larger corpora can increase pipeline duration and the number/size of compute instances used, which increases overall cost.

Yes — For Azure OpenAI usage under Standard (on-demand), pricing is primarily tied to token-based consumption (input tokens + output tokens). The more context you send and the longer the generated responses, the more tokens you consume, and the higher the cost. This is why prompt optimization, response length controls, and grounding strategies matter for cost management.

No — Costs vary with model choice and capability. Different model families and versions have different price points, and larger/more capable models generally cost more per token or per unit of throughput. Additionally, architecture choices (RAG, vector search, caching), usage patterns, and throughput requirements can significantly change total cost—so it is never “always the same.”

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.

Microsoft 365 Copilot

Microsoft Copilot Studio

Microsoft 365 Copilot is the correct match for creating financial summaries and visual reports from Excel workbooks because it is designed to work inside Microsoft 365 productivity apps, including Excel, and helps users analyze, summarize, and create business content. Microsoft Copilot Studio is the correct match for building an autonomous agent by using a low-code approach because Copilot Studio is Microsoft’s tool for creating, customizing, and managing agents that connect to business data and automate interactions. GitHub Copilot is focused on developer coding productivity, and Copilot in Power Automate is focused on workflow automation rather than building a full low-code conversational or autonomous agent. Therefore, Excel-based business analysis maps to Microsoft 365 Copilot, while low-code agent creation maps to Microsoft Copilot Studio.

Answer Area

Microsoft Foundry provides a unified platform for developers and data professionals to create custom end-to-end AI solutions. Answer: Yes

Microsoft Foundry provides a unified platform for low-code developers and business users to create custom end-to-end AI solutions. Answer: No

You need a Microsoft 365 Copilot license to access Microsoft Foundry services. Answer: No

Yes — Microsoft Foundry is positioned by Microsoft as a unified AI platform for building, deploying, and scaling AI apps and agents, with enterprise governance in a single environment. Microsoft explicitly describes Foundry as enabling developers (and, in broader descriptions, data professionals/enterprises) to build and operate AI solutions end-to-end, which aligns with the statement.

No — While Foundry can streamline AI development workflows and may include experiences that reduce complexity, the statement specifically targets low-code developers and business users creating custom end-to-end AI solutions. In Microsoft’s ecosystem, that “low-code/business-user” agent/app-building lane is more directly associated with tools like Copilot Studio/Power Platform , whereas Foundry is primarily presented as the platform for developers and technical teams building and governing AI solutions. Therefore, as written, the statement is not the best characterization.

No — Access to Microsoft Foundry services is not gated by a Microsoft 365 Copilot license. Foundry is part of the Azure AI platform experience (formerly Azure AI Studio) and is accessed through Azure, using Azure subscription-based service consumption. Microsoft 365 Copilot licensing is for Microsoft 365 Copilot experiences, not a prerequisite to use Foundry services.

Azure Machine Learning

Forecasting product demand from historical sales data is a predictive analytics / machine learning use case. It typically requires selecting an appropriate forecasting approach (for example, regression, tree-based methods, or time-series models), preparing and splitting historical data, training and validating the model, tuning hyperparameters, and then deploying the model for ongoing inference. The Microsoft service designed to support that end-to-end ML lifecycle is Azure Machine Learning , which is why it correctly completes the sentence.

Azure Machine Learning provides the tooling and infrastructure to: manage datasets, run training jobs on scalable compute, track experiments, compare model performance, register models, and operationalize them through managed endpoints and pipelines. This makes it well-suited for iterative forecasting work, where you may retrain on new data regularly, monitor drift, and update models as product lines, promotions, or seasonality patterns change.

The other options do not directly fit “train a model” for forecasting. Azure AI Search is an indexing/retrieval service used to search and ground generative AI responses, not for training predictive models. Azure OpenAI provides access to large language and multimodal models for generative tasks (drafting, summarizing, Q & A) and is not the primary platform for building classical forecasting models. Microsoft Foundry is a broader platform experience for building and governing AI apps and agents, but the specific service for training a forecasting model on historical sales data is Azure Machine Learning.

Microsoft Graph

Microsoft 365 Copilot connectors (built on Microsoft Graph connectors) are used to bring external, line-of-business content into the Microsoft 365 ecosystem by ingesting it into Microsoft Graph . Once connected, the content can be indexed and made discoverable through Microsoft Search and available for Copilot experiences, enabling users to use natural language prompts to find and summarize relevant LOB information—subject to permissions and governance controls.

The other choices don’t match how Copilot connectors are positioned. Azure AI Search is an Azure indexing/retrieval service used in custom RAG solutions, but Microsoft 365 Copilot connectors are specifically designed to surface external content through Microsoft 365 experiences via Graph. Microsoft Purview focuses on data governance, compliance, and risk management rather than being the primary ingestion target for Copilot connector content. SharePoint can store content, but the connector model is about indexing external systems into Microsoft Graph so the content becomes searchable and usable across Microsoft 365, not merely placing it into SharePoint as the destination.

So the correct completion is Microsoft Graph because that is the foundational data and indexing fabric Copilot uses to reason over organizational content with appropriate permission trimming.

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.