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

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.

Question 501

Search results are paged, and documents with equal sort values jump between pages. What makes ordering more stable?

  1. Evaluate scoring weights against representative queries before changing production ranking
  2. Apply tenant-scope security filtering in the retrieval query and enforce source authorization
  3. Add a deterministic secondary sort key when supported by the query
  4. Interpret facet counts in the context of the actual query and filters sent

Explanation

Correct Answer

C:

A tie-breaker creates predictable ordering among records sharing the primary sort value. In the staff-facing search results page, confirm the fix by retesting the affected behavior after adding a deterministic secondary sort key when supported by the query.

Incorrect Answers

A:

Business boosts trade off freshness and textual relevance, so their effectiveness requires empirical review in its own workflow, but that is a different correction from the present requirement to add a deterministic secondary sort key when supported by the query. The reported issue would remain.

B:

That change addresses another failure mode: the model's instructions cannot prevent exposure once cross-tenant records are supplied by an unrestricted search query; it does not address this case, for which the relevant intervention is to add a deterministic secondary sort key when supported by the query.

D:

Although useful elsewhere in the staff-facing search results page, facet aggregation reflects the evaluated search context and configuration, not an unchanging global inventory; the present case is different and calls for the team to add a deterministic secondary sort key when supported by the query.

Question 502

A policy-search API must show the newest documents first, and its OData request currently uses the default ascending date order. What exact change fixes this?

  1. Use an OData filter on a department field configured as filterable
  2. Request descending order on the sortable revision-date field with an `orderby` expression
  3. Define an appropriate scoring profile that boosts authoritative metadata
  4. Make the intended text field searchable and query it appropriately

Explanation

Correct Answer

B:

Explicit descending order changes chronological presentation; defining a sortable field alone does not specify newest-first order. In the staff-facing search results page, confirm the fix by retesting the affected behavior after requesting descending order on the sortable revision-date field with an `orderby` expression.

Incorrect Answers

A:

That change addresses another failure mode: structured filtering evaluates metadata conditions; a full-text search for “Finance” may match irrelevant policy prose; it does not address this case, for which the relevant intervention is to request descending order on the sortable revision-date field with an `orderby` expression.

C:

Although useful elsewhere in the staff-facing search results page, scoring profiles allow business relevance boosts alongside standard text ranking; the present case is different and calls for the team to request descending order on the sortable revision-date field with an `orderby` expression.

D:

Full-text matching uses searchable fields; merely storing a string field does not imply it participates in lexical search in its own workflow, but that is a different correction from the present requirement to request descending order on the sortable revision-date field with an `orderby` expression. The reported issue would remain.

Question 503

An app searches across customer tenants and relies solely on a prompt saying “ignore other tenants.” What must enforce isolation?

  1. Evaluate scoring weights against representative queries before changing production ranking
  2. Apply tenant-scope security filtering in the retrieval query and enforce source authorization
  3. Interpret facet counts in the context of the actual query and filters sent
  4. Add a deterministic secondary sort key when supported by the query

Explanation

Correct Answer

B:

The model's instructions cannot prevent exposure once cross-tenant records are supplied by an unrestricted search query. In the staff-facing search results page, confirm the fix by retesting the affected behavior after applying tenant-scope security filtering in the retrieval query and enforce source authorization.

Incorrect Answers

A:

Business boosts trade off freshness and textual relevance, so their effectiveness requires empirical review in its own workflow, but that is a different correction from the present requirement to apply tenant-scope security filtering in the retrieval query and enforce source authorization. The reported issue would remain.

C:

That change addresses another failure mode: facet aggregation reflects the evaluated search context and configuration, not an unchanging global inventory; it does not address this case, for which the relevant intervention is to apply tenant-scope security filtering in the retrieval query and enforce source authorization.

D:

Although useful elsewhere in the staff-facing search results page, a tie-breaker creates predictable ordering among records sharing the primary sort value; the present case is different and calls for the team to apply tenant-scope security filtering in the retrieval query and enforce source authorization.

Question 504

A staff-facing search results page must find indexed documents matching requested words using searchable text fields. Reviewers will accept the implementation when results are based on the user's textual search terms. Which approach best fulfills that requirement?

  1. Use a full-text search query
  2. Request faceting
  3. Use a scoring profile or ranking configuration
  4. Apply an OData filter

Explanation

Correct Answer

A:

Full-text search analyzes text and ranks matches according to the service's query behavior and configuration. For this staff-facing search results page, the intended evidence is that results are based on the user's textual search terms. A filter expression alone does not provide relevance-ranked keyword matching.

Incorrect Answers

B:

Facets aggregate result counts for suitable fields, enabling category navigation and filtering; it may be used to display counts grouped by a filterable category for an interactive refinement panel in a staff-facing search results page, but the current requirement is instead to find indexed documents matching requested words using searchable text fields. That separate capability does not prove that results are based on the user's textual search terms; Sorting documents by date does not produce a list of counts by category, so selecting that alternative would not meet the stated acceptance check.

C:

Search scoring configuration adjusts ranking using supported field weights or functions for an index; it may be used to promote results according to business-relevant relevance signals in addition to ordinary text matching in a staff-facing search results page, but the current requirement is instead to find indexed documents matching requested words using searchable text fields. That separate capability does not prove that results are based on the user's textual search terms; A scoring profile does not ingest new documents or create vector embeddings, so selecting that alternative would not meet the stated acceptance check.

D:

Filters evaluate supported expressions on fields marked filterable and constrain the result set; it may be used to restrict search results by exact metadata conditions such as region or publication state in a staff-facing search results page, but the current requirement is instead to find indexed documents matching requested words using searchable text fields. That separate capability does not prove that results are based on the user's textual search terms; A filter is not a natural-language summarizer or a token similarity search, so selecting that alternative would not meet the stated acceptance check.

Question 505

Sorting by a string-formatted date puts “12/01” ahead of “2/01” unexpectedly. What should the schema use?

  1. Store revision timestamps in a proper date/time field and sort by that type
  2. Check the filter expression, field data type, and filterable attribute for the date field
  3. Use full-text search against analyzed content fields rather than an exact metadata filter
  4. Apply authorization filters instead; relevance boosts are not access controls

Explanation

Correct Answer

A:

String sorting is lexicographic, whereas chronological sorting requires appropriately typed date values. In the staff-facing search results page, confirm the fix by retesting the affected behavior after storing revision timestamps in a proper date/time field and sort by that type.

Incorrect Answers

B:

Date comparisons depend on correct typed metadata and valid OData syntax, not only text search terms in its own workflow, but that is a different correction from the present requirement to store revision timestamps in a proper date/time field and sort by that type. The reported issue would remain.

C:

That change addresses another failure mode: lexical search uses terms and relevance; filters restrict by structured conditions without generating lexical relevance scores; it does not address this case, for which the relevant intervention is to store revision timestamps in a proper date/time field and sort by that type.

D:

Although useful elsewhere in the staff-facing search results page, a lower-ranked confidential hit can still be retrieved; scoring never guarantees exclusion; the present case is different and calls for the team to store revision timestamps in a proper date/time field and sort by that type.

Question 506

A team responsible for a staff-facing search results page needs to display counts grouped by a filterable category for an interactive refinement panel; the acceptance check is that the response includes category values and corresponding counts. Which capability should be selected?

  1. Specify result sorting
  2. Use a scoring profile or ranking configuration
  3. Request faceting
  4. Apply an OData filter

Explanation

Correct Answer

C:

Facets aggregate result counts for suitable fields, enabling category navigation and filtering. For this staff-facing search results page, the intended evidence is that the response includes category values and corresponding counts. Sorting documents by date does not produce a list of counts by category.

Incorrect Answers

A:

Order-by clauses sort the returned set on fields whose index definitions permit sorting; it may be used to order matching records by a sortable field such as revision date in a staff-facing search results page, but the current requirement is instead to display counts grouped by a filterable category for an interactive refinement panel. That separate capability does not prove that the response includes category values and corresponding counts; Sorting is distinct from enforcing permission checks on individual documents, so selecting that alternative would not meet the stated acceptance check.

B:

Search scoring configuration adjusts ranking using supported field weights or functions for an index; it may be used to promote results according to business-relevant relevance signals in addition to ordinary text matching in a staff-facing search results page, but the current requirement is instead to display counts grouped by a filterable category for an interactive refinement panel. That separate capability does not prove that the response includes category values and corresponding counts; A scoring profile does not ingest new documents or create vector embeddings, so selecting that alternative would not meet the stated acceptance check.

D:

Filters evaluate supported expressions on fields marked filterable and constrain the result set; it may be used to restrict search results by exact metadata conditions such as region or publication state in a staff-facing search results page, but the current requirement is instead to display counts grouped by a filterable category for an interactive refinement panel. That separate capability does not prove that the response includes category values and corresponding counts; A filter is not a natural-language summarizer or a token similarity search, so selecting that alternative would not meet the stated acceptance check.

Question 507

A release for a staff-facing search results page is blocked until the application can order matching records by a sortable field such as revision date. The tester will verify that returned items follow the requested date or numeric order. What should be implemented?

  1. Specify result sorting
  2. Request faceting
  3. Use a scoring profile or ranking configuration
  4. Use a full-text search query

Explanation

Correct Answer

A:

Order-by clauses sort the returned set on fields whose index definitions permit sorting. For this staff-facing search results page, the intended evidence is that returned items follow the requested date or numeric order. Sorting is distinct from enforcing permission checks on individual documents.

Incorrect Answers

B:

Facets aggregate result counts for suitable fields, enabling category navigation and filtering; it may be used to display counts grouped by a filterable category for an interactive refinement panel in a staff-facing search results page, but the current requirement is instead to order matching records by a sortable field such as revision date. That separate capability does not prove that returned items follow the requested date or numeric order; Sorting documents by date does not produce a list of counts by category, so selecting that alternative would not meet the stated acceptance check.

C:

Search scoring configuration adjusts ranking using supported field weights or functions for an index; it may be used to promote results according to business-relevant relevance signals in addition to ordinary text matching in a staff-facing search results page, but the current requirement is instead to order matching records by a sortable field such as revision date. That separate capability does not prove that returned items follow the requested date or numeric order; A scoring profile does not ingest new documents or create vector embeddings, so selecting that alternative would not meet the stated acceptance check.

D:

Full-text search analyzes text and ranks matches according to the service's query behavior and configuration; it may be used to find indexed documents matching requested words using searchable text fields in a staff-facing search results page, but the current requirement is instead to order matching records by a sortable field such as revision date. That separate capability does not prove that returned items follow the requested date or numeric order; A filter expression alone does not provide relevance-ranked keyword matching, so selecting that alternative would not meet the stated acceptance check.

Question 508

The solution brief for a staff-facing search results page requires the system to restrict search results by exact metadata conditions such as region or publication state. A successful test confirms that only records satisfying the structured metadata condition appear. What should the team use?

  1. Specify result sorting
  2. Use a scoring profile or ranking configuration
  3. Use a full-text search query
  4. Request faceting
  5. Apply an OData filter

Explanation

Correct Answer

E:

Filters evaluate supported expressions on fields marked filterable and constrain the result set. For this staff-facing search results page, the intended evidence is that only records satisfying the structured metadata condition appear. A filter is not a natural-language summarizer or a token similarity search.

Incorrect Answers

A:

Order-by clauses sort the returned set on fields whose index definitions permit sorting; it may be used to order matching records by a sortable field such as revision date in a staff-facing search results page, but the current requirement is instead to restrict search results by exact metadata conditions such as region or publication state. That separate capability does not prove that only records satisfying the structured metadata condition appear; Sorting is distinct from enforcing permission checks on individual documents, so selecting that alternative would not meet the stated acceptance check.

B:

Search scoring configuration adjusts ranking using supported field weights or functions for an index; it may be used to promote results according to business-relevant relevance signals in addition to ordinary text matching in a staff-facing search results page, but the current requirement is instead to restrict search results by exact metadata conditions such as region or publication state. That separate capability does not prove that only records satisfying the structured metadata condition appear; A scoring profile does not ingest new documents or create vector embeddings, so selecting that alternative would not meet the stated acceptance check.

C:

Full-text search analyzes text and ranks matches according to the service's query behavior and configuration; it may be used to find indexed documents matching requested words using searchable text fields in a staff-facing search results page, but the current requirement is instead to restrict search results by exact metadata conditions such as region or publication state. That separate capability does not prove that only records satisfying the structured metadata condition appear; A filter expression alone does not provide relevance-ranked keyword matching, so selecting that alternative would not meet the stated acceptance check.

D:

Facets aggregate result counts for suitable fields, enabling category navigation and filtering; it may be used to display counts grouped by a filterable category for an interactive refinement panel in a staff-facing search results page, but the current requirement is instead to restrict search results by exact metadata conditions such as region or publication state. That separate capability does not prove that only records satisfying the structured metadata condition appear; Sorting documents by date does not produce a list of counts by category, so selecting that alternative would not meet the stated acceptance check.

Question 509

A search sidebar must show “Policy (32)” and “Procedure (18)” counts. Which response capability provides this?

  1. Request facets over the configured filterable document-type field
  2. Use an OData filter on a department field configured as filterable
  3. Make the intended text field searchable and query it appropriately
  4. Define an appropriate scoring profile that boosts authoritative metadata

Explanation

Correct Answer

A:

Faceting aggregates category counts for navigation; a sort clause only changes result order. In the staff-facing search results page, confirm the fix by retesting the affected behavior after requesting facets over the configured filterable document-type field.

Incorrect Answers

B:

Although useful elsewhere in the staff-facing search results page, structured filtering evaluates metadata conditions; a full-text search for “Finance” may match irrelevant policy prose; the present case is different and calls for the team to request facets over the configured filterable document-type field.

C:

Full-text matching uses searchable fields; merely storing a string field does not imply it participates in lexical search in its own workflow, but that is a different correction from the present requirement to request facets over the configured filterable document-type field. The reported issue would remain.

D:

That change addresses another failure mode: scoring profiles allow business relevance boosts alongside standard text ranking; it does not address this case, for which the relevant intervention is to request facets over the configured filterable document-type field.

Question 510

Employees should see only policies for `department eq 'Finance'`. What field capability and query are needed?

  1. Request facets over the configured filterable document-type field
  2. Make the intended text field searchable and query it appropriately
  3. Use an OData filter on a department field configured as filterable
  4. Define an appropriate scoring profile that boosts authoritative metadata

Explanation

Correct Answer

C:

Structured filtering evaluates metadata conditions; a full-text search for “Finance” may match irrelevant policy prose. In the staff-facing search results page, confirm the fix by retesting the affected behavior after using an OData filter on a department field configured as filterable.

Incorrect Answers

A:

That change addresses another failure mode: faceting aggregates category counts for navigation; a sort clause only changes result order; it does not address this case, for which the relevant intervention is to use an OData filter on a department field configured as filterable.

B:

Although useful elsewhere in the staff-facing search results page, full-text matching uses searchable fields; merely storing a string field does not imply it participates in lexical search; the present case is different and calls for the team to use an OData filter on a department field configured as filterable.

D:

Scoring profiles allow business relevance boosts alongside standard text ranking in its own workflow, but that is a different correction from the present requirement to use an OData filter on a department field configured as filterable. The reported issue would remain.

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