Pearson AB-731 New Attempt

Answer Area

Extracting structured data from forms and invoices: Answer: Azure Document Intelligence in Foundry Tools

Summarizing written content from business reports: Answer: Azure Language in Foundry Tools

Generating descriptive text for uploaded images: Answer: Azure Vision in Foundry Tools

These three tasks align to three different Azure AI capability families: document processing, language understanding/generation, and computer vision.

Forms and invoices are semi-structured documents where the business need is to extract specific fields (IDs, names, totals, dates) reliably into structured output. Azure Document Intelligence is designed for intelligent document processing and includes prebuilt models (such as invoices) as well as custom extraction options, making it the correct choice for structured data extraction from documents.

Summarizing written business reports is an NLP task focused on compressing long text into key points, themes, and action items. Azure Language provides language processing capabilities (including summarization features within language service capabilities), so it is the best fit for summarization scenarios.

Generating descriptive text for images (image captioning/description) is a computer vision task. Azure Vision can analyze uploaded images and return descriptions/captions and other visual insights, which directly matches the requirement to produce descriptive text from images.

To reduce Azure OpenAI costs with minimal quality loss, you target the biggest cost drivers: token usage and model price per token (or throughput unit). C (Optimize the prompts) is a best practice because shorter, clearer prompts reduce unnecessary input tokens and often reduce output length by tightening instructions and formatting. Prompt optimization can preserve or even improve quality by removing ambiguity, adding constraints, and using compact context (for example, only the most relevant grounding passages). Lower token consumption directly lowers cost while maintaining response usefulness.

D (Switch to an alternate model) is also effective because different models have different price/performance tradeoffs. Moving from a premium model to a more cost-efficient model (or a smaller variant) can significantly reduce spend. You can minimize quality impact by validating outputs on representative scenarios and using a tiered approach (cheap model by default, expensive model only for complex cases).

The other options are less aligned to the goal. A (Fine-tune) typically increases cost (training and ongoing evaluation) and is not the first-line cost reducer. B (Content moderation) is primarily a safety control; it can add overhead and doesn’t directly reduce token costs. E (Decrease hosting hours) applies to capacity-based hosting scenarios, but the question states a prebuilt Azure OpenAI model for content generation—cost reduction is best achieved by prompt/token optimization and selecting the right model.

The correct answer is D. Microsoft Copilot Studio. The requirement is to create an AI assistant for a public customer support portal that can answer customer questions and initiate follow-up actions with minimal development effort. Microsoft Copilot Studio is designed for building custom agents using a low-code approach. It can connect to knowledge sources, provide generative answers, define conversation behavior, and trigger actions through connectors or workflows. Microsoft 365 Copilot Chat is intended for workplace productivity and organizational users, not public customer support portals. Microsoft Security Copilot is for security operations and incident investigation. Microsoft 365 Copilot connectors only make external data available to Copilot experiences; they do not by themselves create a public-facing customer support assistant.

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.”