Refer to the exhibit. The indexer using this skillset fails with an error that the skill cannot be executed. The Azure Function is deployed and responds correctly when tested directly. What is the most likely cause?
Azure AI Search requires HTTPS for custom skill endpoints.
Why this answer
Azure AI Search indexers that invoke custom skills via Azure Functions require the endpoint to use HTTPS. If the endpoint is configured with HTTP, the indexer will fail with a 'skill cannot be executed' error, even if the function itself works when tested directly. This is because the indexer enforces secure communication to protect data in transit.
Exam trap
The trap here is that candidates may assume a working function tested directly (often via HTTP) will work in the indexer, overlooking the indexer's strict HTTPS requirement for custom skill endpoints.
How to eliminate wrong answers
Option A is wrong because setting the context to '/document' is standard for document-level skills and does not cause a 'cannot execute' error; it would instead affect how the skill's output is mapped. Option B is wrong because '/document/content' is a valid input source for a document's content field, and if it were invalid, the error would be about missing input data, not skill execution failure. Option D is wrong because a mismatch in output targetName would cause a mapping or indexing error, not a 'skill cannot be executed' error, which occurs before output mapping is evaluated.