Microsoft AB-100: Plan AI-powered business solutions Practice Questions

Correct - Timeliness: HR policies change frequently; stale documents would cause agents to give employees incorrect guidance, directly undermining trust. Correct - Accuracy: Factually incorrect policy information could expose the company to legal or compliance risk. | Wrong - Visual formatting: Formatting consistency is a nice-to-have for readability but does not affect the semantic correctness of grounding data. | Wrong - Volume (10,000 documents): Grounding quality is about relevance and correctness, not raw document count; a handful of accurate, current policies outperforms thousands of outdated ones. | Wrong - Geographic distribution: Data residency and replication are infrastructure concerns, not grounding quality dimensions; they do not affect whether the content itself is suitable for answering HR questions.

Correct - Data source permissions: Defining permissible data sources ensures the agent only accesses authorized knowledge bases and does not inadvertently expose sensitive systems, which is a fundamental constraint. Correct - Escalation rules: Determining handoff conditions (e.g., unresolved tickets, security incidents) ensures the agent operates within safe boundaries and maintains human oversight where needed. | Wrong - Retraining the LLM: Prebuilt agents use existing foundation models; retraining the underlying LLM is neither required nor typically possible for prebuilt agent deployments. | Wrong - Physical data center region for LLM weights: This is a Microsoft infrastructure concern outside the architect's control and is not part of defining agent rules and constraints. | Wrong - Custom neural network architecture: Replacing the prebuilt agent's inference engine contradicts the premise of using a prebuilt agent and is out of scope for this activity.

Correct - Task complexity: Matching task complexity to model capability is the primary routing criterion — it reduces cost by avoiding over-provisioning powerful models for trivial tasks. Correct - Required latency: Latency-sensitive tasks (e.g., real-time translation during a call) must be routed to low-latency models regardless of their depth; latency is a hard constraint. Correct - Task domain and modality: Different models have domain-specific strengths (e.g., multilingual models for translation, long-context models for legal documents); routing by domain ensures quality. | Wrong - Browser font size: Font size is a UI rendering preference with no relevance to AI model selection or request characteristics. | Wrong - Alphabetical order of last name: User surname is irrelevant to task requirements and would result in arbitrary, non-optimized model assignment. | Wrong - Model endpoint load (option B): While this is actually a valid real-world consideration for resilience, in this question context the three MOST correct answers are complexity, latency, and domain/modality as primary routing logic criteria; load-based fallback is a secondary operational concern.

Correct: When Microsoft 365 Copilot's out-of-the-box capabilities are insufficient for complex, domain-specific workflows requiring custom integrations, the correct approach is to build a custom agent in Copilot Studio that extends Copilot — leveraging existing licenses while adding the required logic and API connectivity. | Wrong - M365 Copilot out of the box: Out-of-the-box Copilot does not support custom multi-step conditional branching or direct REST API integration with arbitrary legacy systems; it would not meet the business unit's requirements. | Wrong - Replace with third-party platform: Replacing an already-licensed Microsoft platform increases cost and complexity without justification when Copilot Studio extension is purpose-built for exactly this scenario. | Wrong - Manual copy-paste: Manual data transfer is error-prone, time-consuming, defeats the purpose of AI automation, and introduces data integrity risks.

Correct: Well-defined, repeatable workflows with deterministic rules and structured data are ideal for agentic automation because agents can reliably follow consistent logic, access data sources, and execute actions without ambiguity. | Wrong - Subjective aesthetic judgments: Tasks requiring subjective human judgment are poor candidates for full automation because AI agents lack reliable grounding for highly subjective decisions. | Wrong - Real-time physical inspection: Tasks requiring physical-world sensing before a decision can be made cannot be fully automated by software agents without specialized hardware integration, making them unsuitable as primary automation candidates. | Wrong - Unstructured free-text negotiations: While agents can handle some natural language, tasks that depend entirely on open-ended negotiation introduce too much variability and risk for unassisted end-to-end automation.