CCNA Implement Generative Ai And Agentic Solutions Questions — Page 3 of 3

151

MCQmedium

You are building an Azure AI Foundry agent that answers employee benefits questions from an HR policy PDF set. Legal requires that every response cite the exact source page, and that unsupported answers are refused. You must maximize groundedness while keeping the existing PDFs unchanged. Which approach should you implement?

A.Extend the agent with the Azure AI Search tool connected to an index built with integrated vectorization and semantic ranking, and instruct the agent to cite retrieved chunks.

B.Upload the PDFs as file attachments to the agent and rely on the model's built-in file search with the default chunking settings.

C.Increase the model temperature and top_p so the agent produces more varied, comprehensive answers with citations.

D.Fine-tune the underlying GPT-4o deployment on the HR policy PDFs and route all benefit questions to the fine-tuned model.

AnswerA

An Azure AI Search index with integrated vectorization and semantic ranker returns the most relevant policy chunks, which the agent can ground on and cite by source page. Because the PDFs stay in Blob Storage and are chunked and embedded during indexing, no source modification is required, and citation instructions keep answers tied to retrieved evidence.

Why this answer

Grounding an Azure AI Foundry agent on an Azure AI Search index with integrated vectorization and semantic ranking supplies the retrieved evidence needed for accurate, page-level citations without altering the source PDFs. Combining that retrieval tool with explicit citation instructions also enables the refusal behavior legal requires when no supporting chunk is found.

Exam trap

The trap here is assuming that attaching files or fine-tuning automatically yields page-accurate citations, when only a retrieval index with controlled chunking and semantic ranking provides verifiable source grounding.

Practice this question →

152

Multi-Selectmedium

When implementing prompt engineering for generative AI applications in Azure AI Foundry, which TWO practices are considered best practices for maintaining prompt maintainability and security? (Choose TWO)

Select 2 answers

A.Writing all prompts as single unending paragraphs without formatting

B.Embedding API keys directly inside prompt strings

C.Storing and versioning prompt templates as assets in Azure AI Foundry

D.Hardcoding user names and passwords into system prompts

E.Separating system instructions from untrusted user inputs using clear delimiters or XML tags

AnswersC, E

Storing and versioning prompt templates as assets in Azure AI Foundry gives prompts source control, audit history and rollback, satisfying the maintainability requirement. Changes are tracked centrally rather than scattered in code, so teams can review, compare and revert prompt revisions safely.

Why this answer

Option C is correct because Azure AI Foundry supports storing and versioning prompt templates as managed assets, which enables change tracking, rollback, reuse across deployments, and consistent governance instead of scattering prompts through application code. Option E is correct because separating system instructions from untrusted user input with clear delimiters or XML tags helps prevent prompt injection and instruction-override attacks, and it makes the prompt structure easier to read and maintain. Options A, B, and D are not best practices: unformatted single-paragraph prompts are hard to review and maintain, embedding API keys in prompt strings exposes secrets that can leak through logs or model output, and hardcoding user names and passwords into system prompts creates a serious credential disclosure risk and violates the principle of keeping secrets out of prompts.

Exam trap

AI-103 often tests the misconception that embedding secrets in prompts or using unformatted prompts is acceptable, when in fact secure and maintainable practices require versioned templates and clear delimiters.

Practice this question →

153

MCQhard

You are implementing indirect prompt injection protection for an agent that reads emails and summarizes them. An incoming email contains malicious instructions designed to trick the agent into exfiltrating user data. Which Azure AI feature should you configure to detect this threat?

A.Azure DDoS Protection standard tier

B.Prompt Shields for indirect prompt injection in Azure AI Content Safety

C.Azure Web Application Firewall (WAF) SQL injection rules

D.Microsoft Defender for Cloud threat detection

AnswerB

Prompt Shields specifically detects jailbreak and indirect prompt injection attacks embedded in external content such as emails. It flags the malicious instructions before the agent acts, satisfying the requirement to block data exfiltration triggered by untrusted input.

Why this answer

Prompt Shields in Azure AI Content Safety is specifically designed to detect both direct (user) and indirect (document/email-embedded) prompt injection attacks. For an agent that reads emails, indirect prompt injection is the threat model — malicious instructions hidden in email content — and Prompt Shields analyzes the content to flag it before the agent acts on it. This is the only option that addresses prompt injection at the AI layer.

Exam trap

AI-103 often tests whether candidates confuse network/infrastructure security controls (DDoS, WAF, Defender) with AI-specific content safety controls (Prompt Shields) that actually detect prompt injection in LLM inputs.

How to eliminate wrong answers

Option A is wrong because Azure DDoS Protection defends against volumetric network-layer attacks, not semantic prompt injection embedded in email content. Option C is wrong because WAF SQL injection rules protect against SQLi in HTTP requests to web apps — they do not inspect natural-language email content for prompt injection. Option D is wrong because Microsoft Defender for Cloud provides cloud security posture management and threat detection for infrastructure, not LLM prompt injection detection.

Practice this question →

154

Multi-Selecthard

You are auditing a generative AI application for responsible AI compliance. Which THREE practices should you implement to mitigate risks? (Choose 3)

Select 3 answers

A.Store all user PII in plain text logs

B.Increase the temperature of the model to 1.0

C.Configure system messages to explicitly define boundaries

D.Enable Azure AI Content Safety filtering

E.Implement manual review cycles for high-impact outputs

AnswersC, D, E

System messages set behavioural guardrails by instructing the model to refuse out-of-scope requests, which directly mitigates harmful or off-topic outputs. This satisfies the responsible AI requirement to constrain generated content at inference time, before responses reach users, without retraining or additional infrastructure.

Why this answer

Option C is correct because configuring system messages to explicitly define boundaries constrains the model's behavior, scope, and tone, helping prevent prompt injection, off-topic responses, and harmful or non-compliant outputs. Option D is correct because enabling Azure AI Content Safety filtering applies classifiers for hate, violence, sexual, and self-harm content (plus prompt shields and groundedness detection), directly reducing the risk of harmful or unsafe generated content. Option E is correct because implementing manual review cycles for high-impact outputs adds human oversight, which is a core responsible AI requirement for consequential decisions where automated errors could cause real harm.

Option A is not appropriate because storing user PII in plain text logs violates privacy and data-protection principles and increases breach exposure rather than mitigating risk. Option B is not appropriate because raising the temperature to 1.0 increases randomness and creativity, which raises the likelihood of hallucinated, inconsistent, or unsafe outputs instead of reducing risk.

Exam trap

AI-103 often tests whether candidates confuse model-tuning parameters (temperature, max_tokens) with governance controls, so the trap is picking a sampling knob as if it were a responsible AI safeguard.

Practice this question →

155

MCQeasy

When designing an agentic workflow in Azure AI Foundry, which component is used to manage the execution order and decision-making logic of multiple agents?

A.Orchestrator

B.Vector Index

C.Model Catalog

D.Prompt Template

AnswerA

The orchestrator defines the control flow that sequences agent invocations and routes decisions between them, satisfying the stem's requirement to manage execution order and decision-making logic across multiple agents. Other components handle model hosting, retrieval or tool access, but none govern inter-agent coordination.

Why this answer

The orchestrator component in Azure AI Foundry manages the execution order and decision-making logic of multiple agents. It coordinates tasks, routes requests, and determines which agent acts next based on the workflow. This is essential for building complex agentic systems.

Exam trap

AI-103 often tests the confusion between orchestration components and data storage or model management components, leading candidates to pick vector indexes or model catalogs for execution logic.

How to eliminate wrong answers

Option B is wrong because a vector index is used for storing and retrieving embeddings for similarity search, not for orchestrating agents. Option C is wrong because the model catalog is a repository of prebuilt models, not a control mechanism for agent execution. Option D is wrong because a prompt template is a reusable text structure for prompts, not a logic manager.

Practice this question →

156

MCQmedium

You are configuring an agent that must call a REST API to get current stock prices. Where must you define this integration to ensure the agent can reliably call the tool?

A.In the Azure OpenAI deployment configuration.

B.In the Search index field mapping.

C.In the Agent Tool Definition.

D.In the System Prompt.

AnswerC

Defining the REST API call in the Agent Tool Definition gives the agent the endpoint schema, parameters and authentication it needs at invocation time. This satisfies the stem's reliability constraint: the tool contract is bound to the agent, so stock-price calls resolve consistently rather than depending on external orchestration.

Why this answer

In Azure AI Foundry, tools (including REST API calls, function calling, and OpenAPI-defined tools) are declared in the Agent Tool Definition, which the agent runtime uses to decide when and how to invoke the tool. This is where you register the API schema, authentication, and parameters so the agent can reliably call the stock price endpoint.

Exam trap

AI-103 often tests the misconception that the system prompt is where tools are defined — candidates must know the System Prompt only instructs behavior, while the Agent Tool Definition provides the callable schema and integration.

How to eliminate wrong answers

Option A is wrong because the Azure OpenAI deployment configuration controls model selection, capacity, and content filtering — it does not define tool integrations for an agent. Option B is wrong because the Search index field mapping is specific to Azure AI Search and controls how fields are indexed/retrieved, not how an agent calls a REST API. Option D is wrong because the System Prompt can instruct the model to use a tool, but it does not define the tool's schema, endpoint, or authentication — without a tool definition, the model has no callable function.

Practice this question →