Question 450
An Azure AI workload passes basic health probes but has this issue: A search result exposes a chunk but loses its parent document and version context. Which fix targets it?
- Add the appropriate embedding skill and index projections to the ingestion pipeline
- Configure chunk-level index projections with parent identifiers and source metadata
- Implement a validated custom enrichment skill with clear input and output mappings
- Use an appropriate text split strategy with contextual metadata and modest overlap
Explanation
Correct Answer
B:The fault signal is that a search result exposes a chunk but loses its parent document and version context; the targeted fix works because index projections can place chunk records in a retrieval index with parent keys so answers can link back to source files, restoring the ability to search fine-grained passages while preserving links to complete source documents.
Incorrect Answers
A:If the failing function were to avoid writing a custom service for every supported text-to-vector conversion, this change could be relevant because integrated vectorization uses an indexer and enrichment pipeline to chunk and embed content; query-side vectorization still needs compatible settings; the actual symptom is that a search result exposes a chunk but loses its parent document and version context, which calls for a different repair.
C:If the failing function were to apply a proprietary extraction algorithm that the built-in search skillset cannot express, this change could be relevant because custom Web API skills can call external enrichment code and return structured outputs to an indexer pipeline; the actual symptom is that a search result exposes a chunk but loses its parent document and version context, which calls for a different repair.
D:If the failing function were to keep retrieval passages within embedding and prompt size limits without losing section context, this change could be relevant because chunking creates smaller units for indexing and grounding; titles and parent identifiers should accompany chunks; the actual symptom is that a search result exposes a chunk but loses its parent document and version context, which calls for a different repair.
Question 451
A project needs to complete all of these distinct tasks: (1) diagnose whether poor RAG answers originate from missing passages rather than generation itself; and (2) make an agent's grounded answer traceable back to the correct document chunk. Select one suitable capability for each task. Choose TWO.
- Use freshness monitoring and incremental refresh
- Generate embeddings during indexing with a skillset
- Apply retrieval quality evaluation before model tuning
- Attach retrieved source identifiers to agent tools
- Filter retrieved evidence by user entitlements
Explanation
Correct Answers
C:For the stated requirement to diagnose whether poor RAG answers originate from missing passages rather than generation itself, search relevance and recall metrics isolate retrieval defects; changing prompts cannot create facts absent from the context; this is the mechanism that the system must implement. This choice satisfies the specific deliverable to diagnose whether poor RAG answers originate from missing passages rather than generation itself, while the other deliverables require separate capabilities.
D:For the stated requirement to make an agent's grounded answer traceable back to the correct document chunk, a retrieval tool should return source identity and relevant snippet metadata along with content, not text alone; this is the mechanism that the system must implement. This choice satisfies the specific deliverable to make an agent's grounded answer traceable back to the correct document chunk, while the other deliverables require separate capabilities.
Incorrect Answers
A:For a system whose objective is to avoid answering from superseded policy versions after files change, scheduled or change-aware ingestion and indexed version checks keep the retrieval corpus aligned with its authority; this does not directly meet the required outcome to make an agent's grounded answer traceable back to the correct document chunk.
B:For a system whose objective is to avoid writing a custom service for every supported text-to-vector conversion, integrated vectorization uses an indexer and enrichment pipeline to chunk and embed content; query-side vectorization still needs compatible settings; this does not directly meet the required outcome to make an agent's grounded answer traceable back to the correct document chunk.
E:For a system whose objective is to stop an agent from using search hits that the current requester is not allowed to read, permission-aware retrieval or correctly enforced security filters keep restricted chunks out of prompt context; this does not directly meet the required outcome to make an agent's grounded answer traceable back to the correct document chunk.
Question 452
A cloud engineering team must keep search content synchronized with periodically changing files in a connected repository. What is the most appropriate Azure AI implementation?
- Apply OCR to scanned document images
- Project chunks to a secondary retrieval index
- Split large documents into meaningful chunks
- Use an indexer for supported data sources
Explanation
Correct Answer
D:For the stated requirement to keep search content synchronized with periodically changing files in a connected repository, Azure AI Search indexers read supported sources and drive enrichment and indexing on a schedule; external custom sources may need a push path; this is the mechanism that the system must implement.
Incorrect Answers
A:For a system whose objective is to make text from photographed forms available for retrieval and citation, OCR converts visible characters into machine-readable text; text splitters cannot recover words from image-only pages; this does not directly meet the required outcome to keep search content synchronized with periodically changing files in a connected repository.
B:For a system whose objective is to search fine-grained passages while preserving links to complete source documents, index projections can place chunk records in a retrieval index with parent keys so answers can link back to source files; this does not directly meet the required outcome to keep search content synchronized with periodically changing files in a connected repository.
C:For a system whose objective is to keep retrieval passages within embedding and prompt size limits without losing section context, chunking creates smaller units for indexing and grounding; titles and parent identifiers should accompany chunks; this does not directly meet the required outcome to keep search content synchronized with periodically changing files in a connected repository.
Question 453
After implementing a workflow to use layout-aware extraction for tables and headings, the team needs a robust release gate. Which check should it choose?
- Check indexed vector coverage and embedding failures by document batch
- Measure retrieval accuracy on visually described equipment and diagram questions
- Check table-cell relationships and heading attribution on representative document queries
- Measure character recognition quality and retrieval recall on annotated scans
Explanation
Correct Answer
C:The accepted change is to use layout-aware extraction for tables and headings; this evaluation checks whether it can preserve relationships between headings, cells and surrounding text during document ingestion, since layout processing detects document structure and table boundaries beyond simple plain-text OCR.
Incorrect Answers
A:This test concerns the ability to avoid writing a custom service for every supported text-to-vector conversion, for which integrated vectorization uses an indexer and enrichment pipeline to chunk and embed content; query-side vectorization still needs compatible settings; it does not establish whether the change to use layout-aware extraction for tables and headings works for the current release.
B:This test concerns the ability to index meaningful visual content of diagrams that contains no searchable text, for which image captioning or multimodal understanding produces descriptors for visual semantics; OCR alone reads only visible characters; it does not establish whether the change to use layout-aware extraction for tables and headings works for the current release.
D:This test concerns the ability to make text from photographed forms available for retrieval and citation, for which OCR converts visible characters into machine-readable text; text splitters cannot recover words from image-only pages; it does not establish whether the change to use layout-aware extraction for tables and headings works for the current release.
Question 454
A solution architect is deciding how to avoid writing a custom service for every supported text-to-vector conversion. Which Azure AI pattern addresses that task?
- Project chunks to a secondary retrieval index
- Generate embeddings during indexing with a skillset
- Split large documents into meaningful chunks
- Apply OCR to scanned document images
Explanation
Correct Answer
B:For the stated requirement to avoid writing a custom service for every supported text-to-vector conversion, integrated vectorization uses an indexer and enrichment pipeline to chunk and embed content; query-side vectorization still needs compatible settings; this is the mechanism that the system must implement.
Incorrect Answers
A:For a system whose objective is to search fine-grained passages while preserving links to complete source documents, index projections can place chunk records in a retrieval index with parent keys so answers can link back to source files; this does not directly meet the required outcome to avoid writing a custom service for every supported text-to-vector conversion.
C:For a system whose objective is to keep retrieval passages within embedding and prompt size limits without losing section context, chunking creates smaller units for indexing and grounding; titles and parent identifiers should accompany chunks; this does not directly meet the required outcome to avoid writing a custom service for every supported text-to-vector conversion.
D:For a system whose objective is to make text from photographed forms available for retrieval and citation, OCR converts visible characters into machine-readable text; text splitters cannot recover words from image-only pages; this does not directly meet the required outcome to avoid writing a custom service for every supported text-to-vector conversion.
Question 455
A cloud engineering team needs its AI workflow to search fine-grained passages while preserving links to complete source documents. What technical approach most directly enables that?
- Use an indexer for supported data sources
- Project chunks to a secondary retrieval index
- Split large documents into meaningful chunks
- Add semantic reranking for answer relevance
Explanation
Correct Answer
B:For the stated requirement to search fine-grained passages while preserving links to complete source documents, index projections can place chunk records in a retrieval index with parent keys so answers can link back to source files; this is the mechanism that the system must implement.
Incorrect Answers
A:For a system whose objective is to keep search content synchronized with periodically changing files in a connected repository, Azure AI Search indexers read supported sources and drive enrichment and indexing on a schedule; external custom sources may need a push path; this does not directly meet the required outcome to search fine-grained passages while preserving links to complete source documents.
C:For a system whose objective is to keep retrieval passages within embedding and prompt size limits without losing section context, chunking creates smaller units for indexing and grounding; titles and parent identifiers should accompany chunks; this does not directly meet the required outcome to search fine-grained passages while preserving links to complete source documents.
D:For a system whose objective is to promote passages that directly answer questions over textually similar but less useful chunks, semantic ranking reranks a first-stage candidate list using language understanding; it cannot rescue documents never retrieved; this does not directly meet the required outcome to search fine-grained passages while preserving links to complete source documents.
Question 456
After deployment, the team observes: A handbook is updated but the assistant continues quoting text from the previous index snapshot. Which remediation addresses the likely cause?
- Enforce effective user permissions in retrieval queries and document mappings
- Evaluate query-to-passage recall and repair retrieval before adjusting generation behavior
- Refresh changed documents and verify version stamps before serving critical policy answers
- Add appropriately typed filterable metadata fields and populate them during indexing
Explanation
Correct Answer
C:The fault signal is that a handbook is updated but the assistant continues quoting text from the previous index snapshot; the targeted fix works because scheduled or change-aware ingestion and indexed version checks keep the retrieval corpus aligned with its authority, restoring the ability to avoid answering from superseded policy versions after files change.
Incorrect Answers
A:If the failing function were to stop an agent from using search hits that the current requester is not allowed to read, this change could be relevant because permission-aware retrieval or correctly enforced security filters keep restricted chunks out of prompt context; the actual symptom is that a handbook is updated but the assistant continues quoting text from the previous index snapshot, which calls for a different repair.
B:If the failing function were to diagnose whether poor RAG answers originate from missing passages rather than generation itself, this change could be relevant because search relevance and recall metrics isolate retrieval defects; changing prompts cannot create facts absent from the context; the actual symptom is that a handbook is updated but the assistant continues quoting text from the previous index snapshot, which calls for a different repair.
D:If the failing function were to support both full-text answers and exact filtering by department and policy year, this change could be relevant because Azure AI Search index fields must be configured for the operations used; searchable text differs from structured filterable metadata; the actual symptom is that a handbook is updated but the assistant continues quoting text from the previous index snapshot, which calls for a different repair.
Question 457
The engineering change request is to use freshness monitoring and incremental refresh. What is the most direct acceptance criterion?
- Check table-cell relationships and heading attribution on representative document queries
- Measure ingestion lag and stale-citation rate following a controlled source update
- Check each quoted claim against the cited source record and revision
- Track retrieval recall at k separately from answer faithfulness and fluency
Explanation
Correct Answer
B:The accepted change is to use freshness monitoring and incremental refresh; this evaluation checks whether it can avoid answering from superseded policy versions after files change, since scheduled or change-aware ingestion and indexed version checks keep the retrieval corpus aligned with its authority.
Incorrect Answers
A:This test concerns the ability to preserve relationships between headings, cells and surrounding text during document ingestion, for which layout processing detects document structure and table boundaries beyond simple plain-text OCR; it does not establish whether the change to use freshness monitoring and incremental refresh works for the current release.
C:This test concerns the ability to make an agent's grounded answer traceable back to the correct document chunk, for which a retrieval tool should return source identity and relevant snippet metadata along with content, not text alone; it does not establish whether the change to use freshness monitoring and incremental refresh works for the current release.
D:This test concerns the ability to diagnose whether poor RAG answers originate from missing passages rather than generation itself, for which search relevance and recall metrics isolate retrieval defects; changing prompts cannot create facts absent from the context; it does not establish whether the change to use freshness monitoring and incremental refresh works for the current release.
Question 458
An Azure AI workload passes basic health probes but has this issue: An agent can quote a policy but the evidence lacks a link to the right version and section. Which fix targets it?
- Apply semantic reranking to the initial results and tune the candidate pool
- Evaluate query-to-passage recall and repair retrieval before adjusting generation behavior
- Expose source IDs and versioned citations in the retrieval tool response contract
- Enforce effective user permissions in retrieval queries and document mappings
Explanation
Correct Answer
C:The fault signal is that an agent can quote a policy but the evidence lacks a link to the right version and section; the targeted fix works because a retrieval tool should return source identity and relevant snippet metadata along with content, not text alone, restoring the ability to make an agent's grounded answer traceable back to the correct document chunk.
Incorrect Answers
A:If the failing function were to promote passages that directly answer questions over textually similar but less useful chunks, this change could be relevant because semantic ranking reranks a first-stage candidate list using language understanding; it cannot rescue documents never retrieved; the actual symptom is that an agent can quote a policy but the evidence lacks a link to the right version and section, which calls for a different repair.
B:If the failing function were to diagnose whether poor RAG answers originate from missing passages rather than generation itself, this change could be relevant because search relevance and recall metrics isolate retrieval defects; changing prompts cannot create facts absent from the context; the actual symptom is that an agent can quote a policy but the evidence lacks a link to the right version and section, which calls for a different repair.
D:If the failing function were to stop an agent from using search hits that the current requester is not allowed to read, this change could be relevant because permission-aware retrieval or correctly enforced security filters keep restricted chunks out of prompt context; the actual symptom is that an agent can quote a policy but the evidence lacks a link to the right version and section, which calls for a different repair.
Question 459
An operator can reproduce this error: Employees upload approved documents but new revisions never reach the retrieval index. Which targeted repair is justified?
- Configure an indexer and scheduled refresh for the supported source connection
- Align the embedding deployment and vector field schema, then regenerate incompatible vectors
- Configure chunk-level index projections with parent identifiers and source metadata
- Use an appropriate text split strategy with contextual metadata and modest overlap
Explanation
Correct Answer
A:The fault signal is that employees upload approved documents but new revisions never reach the retrieval index; the targeted fix works because Azure AI Search indexers read supported sources and drive enrichment and indexing on a schedule; external custom sources may need a push path, restoring the ability to keep search content synchronized with periodically changing files in a connected repository.
Incorrect Answers
B:If the failing function were to ensure the index's vector field accepts embeddings produced by the selected model, this change could be relevant because an Azure AI Search vector field must have dimensions compatible with the embedding output and a valid vector search configuration; mismatched vectors fail at indexing or query time; the actual symptom is that employees upload approved documents but new revisions never reach the retrieval index, which calls for a different repair.
C:If the failing function were to search fine-grained passages while preserving links to complete source documents, this change could be relevant because index projections can place chunk records in a retrieval index with parent keys so answers can link back to source files; the actual symptom is that employees upload approved documents but new revisions never reach the retrieval index, which calls for a different repair.
D:If the failing function were to keep retrieval passages within embedding and prompt size limits without losing section context, this change could be relevant because chunking creates smaller units for indexing and grounding; titles and parent identifiers should accompany chunks; the actual symptom is that employees upload approved documents but new revisions never reach the retrieval index, which calls for a different repair.
Question 460
A Foundry-based application is being scoped for production. The non-negotiable task is to ensure the index's vector field accepts embeddings produced by the selected model. Which implementation fits?
- Define searchable and filterable fields appropriately
- Match index vector dimensions to embedding model outputs
- Add semantic reranking for answer relevance
- Generate embeddings during indexing with a skillset
Explanation
Correct Answer
B:For the stated requirement to ensure the index's vector field accepts embeddings produced by the selected model, an Azure AI Search vector field must have dimensions compatible with the embedding output and a valid vector search configuration; mismatched vectors fail at indexing or query time; this is the mechanism that the system must implement.
Incorrect Answers
A:For a system whose objective is to support both full-text answers and exact filtering by department and policy year, Azure AI Search index fields must be configured for the operations used; searchable text differs from structured filterable metadata; this does not directly meet the required outcome to ensure the index's vector field accepts embeddings produced by the selected model.
C:For a system whose objective is to promote passages that directly answer questions over textually similar but less useful chunks, semantic ranking reranks a first-stage candidate list using language understanding; it cannot rescue documents never retrieved; this does not directly meet the required outcome to ensure the index's vector field accepts embeddings produced by the selected model.
D:For a system whose objective is to avoid writing a custom service for every supported text-to-vector conversion, integrated vectorization uses an indexer and enrichment pipeline to chunk and embed content; query-side vectorization still needs compatible settings; this does not directly meet the required outcome to ensure the index's vector field accepts embeddings produced by the selected model.