Microsoft AI-102 (Designing and Implementing a Microsoft Azure AI Solution) Practice Test 50

Question 490

Deleted source files remain searchable after later indexing runs. What should be evaluated?

  1. Choose field attributes and query behavior appropriate for exact metadata versus analyzed text
  2. Review custom skill endpoint latency, retry behavior, and indexing batch settings
  3. Use a supported managed identity and grant it the required storage data access
  4. Configure supported deletion detection or an explicit index document deletion process

Explanation

Correct Answer

D:

Source removal does not automatically imply a corresponding index delete in every data-source configuration. In the enterprise policy-document search service, confirm the fix by retesting the affected behavior after configuring supported deletion detection or an explicit index document deletion process.

Incorrect Answers

A:

Identifiers and prose have different matching requirements; tokenization can change exact-match behavior in its own workflow, but that is a different correction from the present requirement to configure supported deletion detection or an explicit index document deletion process. The reported issue would remain.

B:

Although useful elsewhere in the enterprise policy-document search service, custom enrichment calls are external dependencies with resource limits and error-handling requirements; the present case is different and calls for the team to configure supported deletion detection or an explicit index document deletion process.

C:

That change addresses another failure mode: having a data-source definition is not equivalent to possessing authorization on the external data store; it does not address this case, for which the relevant intervention is to configure supported deletion detection or an explicit index document deletion process.

Question 491

The indexer failed halfway through ingestion and no engineer noticed. What operational control should be added?

  1. Verify the connection string or identity and source container reference
  2. Configure output field mappings or projections from enrichment nodes to index fields
  3. Define a unique document key field of the supported key type
  4. Monitor indexer execution history and alert on failed runs

Explanation

Correct Answer

D:

A schedule initiates jobs, but it does not guarantee they complete successfully. In the enterprise policy-document search service, confirm the fix by retesting the affected behavior after monitoring indexer execution history and alert on failed runs.

Incorrect Answers

A:

Although useful elsewhere in the enterprise policy-document search service, a valid but incorrect source reference can ingest the wrong corpus without causing an obvious schema error; the present case is different and calls for the team to monitor indexer execution history and alert on failed runs.

B:

Enrichment results are not searchable until mapped into stored index content in its own workflow, but that is a different correction from the present requirement to monitor indexer execution history and alert on failed runs. The reported issue would remain.

C:

That change addresses another failure mode: azure AI Search documents require an identifier to add, merge, or delete specific records; it does not address this case, for which the relevant intervention is to monitor indexer execution history and alert on failed runs.

Question 492

A skillset extracts organizations but the index always shows empty `organizations`. What mapping may be missing?

  1. Define the intended knowledge store objects or table projections and their destination
  2. Configure output field mappings or projections from enrichment nodes to index fields
  3. Define a unique document key field of the supported key type
  4. Verify the connection string or identity and source container reference

Explanation

Correct Answer

B:

Enrichment results are not searchable until mapped into stored index content. In the enterprise policy-document search service, confirm the fix by retesting the affected behavior after configuring output field mappings or projections from enrichment nodes to index fields.

Incorrect Answers

A:

Although useful elsewhere in the enterprise policy-document search service, enrichment applied to an index does not automatically create external reporting artifacts; the present case is different and calls for the team to configure output field mappings or projections from enrichment nodes to index fields.

C:

Azure AI Search documents require an identifier to add, merge, or delete specific records in its own workflow, but that is a different correction from the present requirement to configure output field mappings or projections from enrichment nodes to index fields. The reported issue would remain.

D:

That change addresses another failure mode: a valid but incorrect source reference can ingest the wrong corpus without causing an obvious schema error; it does not address this case, for which the relevant intervention is to configure output field mappings or projections from enrichment nodes to index fields.

Question 493

An Azure AI Search indexer's configured Blob Storage data source uses the search service managed identity, but ingestion fails with a storage authorization error. What permission should be verified?

  1. Set the field's `filterable` capability in a compatible index schema before indexing
  2. Add an OCR enrichment skill and project its extracted text into a searchable field
  3. Grant the indexer identity the required blob data-plane read permission on the intended storage scope
  4. Run the indexer on demand or adjust its supported refresh schedule

Explanation

Correct Answer

C:

A data-source object describes an ingestion connection but does not grant that connection authorization, so the configured managed identity must have suitable blob data-plane read rights at the source scope.

Incorrect Answers

A:

That change addresses another failure mode: full-text searchable and filterable flags serve different query behaviors; filter expressions require filterable fields; it does not address this case, for which the relevant intervention is to grant the indexer identity the required blob data-plane read permission on the intended storage scope.

B:

Image-only pages need recognized text before lexical search can match their contents in its own workflow, but that is a different correction from the present requirement to grant the indexer identity the required blob data-plane read permission on the intended storage scope. The reported issue would remain.

D:

Although useful elsewhere in the enterprise policy-document search service, indexer scheduling determines when source changes are processed; storage updates do not necessarily push immediately; the present case is different and calls for the team to grant the indexer identity the required blob data-plane read permission on the intended storage scope.

Question 494

A search index schema contains a metadata field `department`, but filters on that field fail. What attribute should be checked?

  1. Choose a supported knowledge store projection shape matching downstream table analytics
  2. Grant the indexer identity the required blob data-plane read permission on the intended storage scope
  3. Set the field's `filterable` capability in a compatible index schema before indexing
  4. Add an OCR enrichment skill and project its extracted text into a searchable field

Explanation

Correct Answer

C:

Full-text searchable and filterable flags serve different query behaviors; filter expressions require filterable fields. In the enterprise policy-document search service, confirm the fix by retesting the affected behavior after setting the field's `filterable` capability in a compatible index schema before indexing.

Incorrect Answers

A:

Although useful elsewhere in the enterprise policy-document search service, projection formats influence how consumers query enriched content; selecting a table-oriented shape is different from merely enabling enrichment; the present case is different and calls for the team to set the field's `filterable` capability in a compatible index schema before indexing.

B:

That change addresses another failure mode: a data-source object describes an ingestion connection but does not grant that connection authorization, so the configured managed identity must have suitable blob data-plane read rights at the source scope; it does not address this case, for which the relevant intervention is to set the field's `filterable` capability in a compatible index schema before indexing.

D:

Image-only pages need recognized text before lexical search can match their contents in its own workflow, but that is a different correction from the present requirement to set the field's `filterable` capability in a compatible index schema before indexing. The reported issue would remain.

Question 495

A compliance team wants to know which projected extraction came from which source file. What should the projection preserve?

  1. Configure supported deletion detection or an explicit index document deletion process
  2. Include stable source-document identifiers with stored enrichment outputs
  3. Use a supported managed identity and grant it the required storage data access
  4. Choose field attributes and query behavior appropriate for exact metadata versus analyzed text

Explanation

Correct Answer

B:

Provenance makes projected artifacts traceable and supports correction or deletion of originating content. In the enterprise policy-document search service, confirm the fix by retesting the affected behavior after including stable source-document identifiers with stored enrichment outputs.

Incorrect Answers

A:

Although useful elsewhere in the enterprise policy-document search service, source removal does not automatically imply a corresponding index delete in every data-source configuration; the present case is different and calls for the team to include stable source-document identifiers with stored enrichment outputs.

C:

That change addresses another failure mode: having a data-source definition is not equivalent to possessing authorization on the external data store; it does not address this case, for which the relevant intervention is to include stable source-document identifiers with stored enrichment outputs.

D:

Identifiers and prose have different matching requirements; tokenization can change exact-match behavior in its own workflow, but that is a different correction from the present requirement to include stable source-document identifiers with stored enrichment outputs. The reported issue would remain.

Question 496

The solution brief for an enterprise policy-document search service requires the system to run OCR, entity extraction, or other supported enrichment steps during indexing. A successful test confirms that enriched terms and extracted text become available in projected index fields. What should the team use?

  1. Define an enrichment skillset
  2. Create and schedule an indexer
  3. Configure knowledge store projections
  4. Define an Azure AI Search index schema

Explanation

Correct Answer

A:

A skillset chains built-in or custom AI skills to produce enriched fields from source content. For this enterprise policy-document search service, the intended evidence is that enriched terms and extracted text become available in projected index fields. A skillset does not replace the target index or the indexer's source connection.

Incorrect Answers

B:

An indexer pulls data from configured sources, applies configured mappings or skills, and writes searchable documents; it may be used to automate extraction and refresh of supported source data into an Azure AI Search index in a enterprise policy-document search service, but the current requirement is instead to run OCR, entity extraction, or other supported enrichment steps during indexing. That separate capability does not prove that enriched terms and extracted text become available in projected index fields; A query request is not an indexing schedule and cannot refresh stale source records, so selecting that alternative would not meet the stated acceptance check.

C:

Knowledge store projections persist selected AI-enrichment outputs outside the search index in supported storage structures; it may be used to retain enrichment outputs as projected objects, files, or tables for downstream analysis in a enterprise policy-document search service, but the current requirement is instead to run OCR, entity extraction, or other supported enrichment steps during indexing. That separate capability does not prove that enriched terms and extracted text become available in projected index fields; They are not equivalent to retrieving ranked documents through the search endpoint, so selecting that alternative would not meet the stated acceptance check.

D:

An index schema defines field types and attributes controlling indexing and query behavior; one suitable field serves as the document key; it may be used to establish searchable, filterable, sortable, and key fields for the queryable document collection in a enterprise policy-document search service, but the current requirement is instead to run OCR, entity extraction, or other supported enrichment steps during indexing. That separate capability does not prove that enriched terms and extracted text become available in projected index fields; A data-source connection alone does not specify which fields are filterable or searchable, so selecting that alternative would not meet the stated acceptance check.

Question 497

Search works but a reporting job cannot find enriched data in the storage account. What object is missing?

  1. Define a unique document key field of the supported key type
  2. Define the intended knowledge store objects or table projections and their destination
  3. Monitor indexer execution history and alert on failed runs
  4. Verify the connection string or identity and source container reference

Explanation

Correct Answer

B:

Enrichment applied to an index does not automatically create external reporting artifacts. In the enterprise policy-document search service, confirm the fix by retesting the affected behavior after defining the intended knowledge store objects or table projections and their destination.

Incorrect Answers

A:

Although useful elsewhere in the enterprise policy-document search service, azure AI Search documents require an identifier to add, merge, or delete specific records; the present case is different and calls for the team to define the intended knowledge store objects or table projections and their destination.

C:

A schedule initiates jobs, but it does not guarantee they complete successfully in its own workflow, but that is a different correction from the present requirement to define the intended knowledge store objects or table projections and their destination. The reported issue would remain.

D:

That change addresses another failure mode: a valid but incorrect source reference can ingest the wrong corpus without causing an obvious schema error; it does not address this case, for which the relevant intervention is to define the intended knowledge store objects or table projections and their destination.

Question 498

A field intended only for exact SKU lookup was configured for linguistic full-text analysis. What design distinction matters?

  1. Use a supported managed identity and grant it the required storage data access
  2. Configure supported deletion detection or an explicit index document deletion process
  3. Review custom skill endpoint latency, retry behavior, and indexing batch settings
  4. Choose field attributes and query behavior appropriate for exact metadata versus analyzed text

Explanation

Correct Answer

D:

Identifiers and prose have different matching requirements; tokenization can change exact-match behavior. In the enterprise policy-document search service, confirm the fix by retesting the affected behavior after choosing field attributes and query behavior appropriate for exact metadata versus analyzed text.

Incorrect Answers

A:

Although useful elsewhere in the enterprise policy-document search service, having a data-source definition is not equivalent to possessing authorization on the external data store; the present case is different and calls for the team to choose field attributes and query behavior appropriate for exact metadata versus analyzed text.

B:

Source removal does not automatically imply a corresponding index delete in every data-source configuration in its own workflow, but that is a different correction from the present requirement to choose field attributes and query behavior appropriate for exact metadata versus analyzed text. The reported issue would remain.

C:

That change addresses another failure mode: custom enrichment calls are external dependencies with resource limits and error-handling requirements; it does not address this case, for which the relevant intervention is to choose field attributes and query behavior appropriate for exact metadata versus analyzed text.

Question 499

An enterprise policy-document search service must automate extraction and refresh of supported source data into an Azure AI Search index. Reviewers will accept the implementation when changed source material is processed on the expected indexing runs. Which approach best fulfills that requirement?

  1. Create and schedule an indexer
  2. Configure an indexer data source
  3. Configure knowledge store projections
  4. Define an Azure AI Search index schema

Explanation

Correct Answer

A:

An indexer pulls data from configured sources, applies configured mappings or skills, and writes searchable documents. For this enterprise policy-document search service, the intended evidence is that changed source material is processed on the expected indexing runs. A query request is not an indexing schedule and cannot refresh stale source records.

Incorrect Answers

B:

A data source supplies a connection and source configuration for supported Azure AI Search indexing pipelines; it may be used to describe the supported external store from which an indexer will ingest content in a enterprise policy-document search service, but the current requirement is instead to automate extraction and refresh of supported source data into an Azure AI Search index. That separate capability does not prove that changed source material is processed on the expected indexing runs; It does not define the searchable field mapping for an index by itself, so selecting that alternative would not meet the stated acceptance check.

C:

Knowledge store projections persist selected AI-enrichment outputs outside the search index in supported storage structures; it may be used to retain enrichment outputs as projected objects, files, or tables for downstream analysis in a enterprise policy-document search service, but the current requirement is instead to automate extraction and refresh of supported source data into an Azure AI Search index. That separate capability does not prove that changed source material is processed on the expected indexing runs; They are not equivalent to retrieving ranked documents through the search endpoint, so selecting that alternative would not meet the stated acceptance check.

D:

An index schema defines field types and attributes controlling indexing and query behavior; one suitable field serves as the document key; it may be used to establish searchable, filterable, sortable, and key fields for the queryable document collection in a enterprise policy-document search service, but the current requirement is instead to automate extraction and refresh of supported source data into an Azure AI Search index. That separate capability does not prove that changed source material is processed on the expected indexing runs; A data-source connection alone does not specify which fields are filterable or searchable, so selecting that alternative would not meet the stated acceptance check.

Question 500

An Azure AI Search indexer must read a private blob container without storing storage keys in the data-source definition. Which TWO steps enable the intended access? (Choose TWO.)

  1. Choose field attributes and query behavior appropriate for exact metadata versus analyzed text
  2. Configure the supported indexer data source to authenticate using the search service's managed identity
  3. Grant the search service identity an appropriate Storage Blob data-access role
  4. Configure supported deletion detection or an explicit index document deletion process
  5. Review custom skill endpoint latency, retry behavior, and indexing batch settings

Explanation

Correct Answers

B:

The connection must identify the intended identity-based access path rather than supplying a long-lived shared storage key.

C:

The managed identity cannot read container contents unless Azure Storage authorizes the required data-plane operations at the correct scope.

Incorrect Answers

A:

That change addresses another failure mode: identifiers and prose have different matching requirements; tokenization can change exact-match behavior; it does not address this case, for which the relevant intervention is to configure the supported indexer data source to authenticate using the search service's managed identity and grant the search service identity an appropriate Storage Blob data-access role.

D:

Source removal does not automatically imply a corresponding index delete in every data-source configuration in its own workflow, but that is a different correction from the present requirement to configure the supported indexer data source to authenticate using the search service's managed identity and grant the search service identity an appropriate Storage Blob data-access role. The reported issue would remain.

E:

Although useful elsewhere in the enterprise policy-document search service, custom enrichment calls are external dependencies with resource limits and error-handling requirements; the present case is different and calls for the team to configure the supported indexer data source to authenticate using the search service's managed identity and grant the search service identity an appropriate Storage Blob data-access role.

Designing and Implementing a Microsoft Azure AI Solution (AI-102) Practice Tests