LPI 010-160 Exam Prep Course (Premium File)
AI-Powered Linux Essentials Certificate Exam, version 1.6 Exam - Pass on Your First Try

Question 382:

• Correct answer: C — Inability of a plan subscriber to locate and access fee information for nearby participating service providers.

• Why: The stated capabilities focus on helping subscribers find providers in their vicinity (real-time maps/GPS, search by postal code or radius) and, critically, enable downloading the fee schedule for those providers. Requirements 7–11 directly support locating providers and retrieving their fee information. While directions (B) are useful, the primary business need driven by the enhancements is to locate nearby providers and access their fee information (C). Options A and D refer to provider-to-provider alerts or provider awareness of subscribers, which are not the primary goals of these enhancements.

• Note: The problem statement’s official answer in this page shows D, which does not align with the described capabilities. The explanation above aligns the needs with the subscriber-centered benefits.

Question 116:

• Correct answer: IPSec

• Why: IPSec provides security at the IP layer by authenticating and encrypting each IP packet in transit, giving confidentiality, integrity, and authenticity for data moving within the private cloud (e.g., site-to-site or host-to-host VPNs).

• Why not the others:

Question 33:

• Correct concept: The Weather.Historic entity corresponds to the text "by month" in the utterance.

• Why: The sample export shows the entity spans characters 23 to 31, and the substring in that span is "by month." In LU/LUIS, an entity's value is the exact text matched in the utterance; startIndex/endIndex (or startPos/endPos in older versions) indicate where that text appears.

• Key takeaway: Weather.Historic is the phrase "by month" extracted from the user input, not the numeric value or a separate label. The positions illustrate where the entity text is located within the utterance.

Question 61:

• Correct answer: Run the Bot Framework Emulator.

• Why: When you start a bot locally, the Emulator is the standard tool to validate and debug your bot without publishing it. It lets you connect to your local endpoint (e.g., http://localhost:3978/api/messages), send test messages, inspect requests/responses, and verify dialogs and state.

• What to expect: You can test conversation flows, activities, and debugging traces, ensuring the bot behaves as intended before connecting to any Azure channels.

• Why the other options aren’t correct for this step:

Question 51:

• Correct answer: Waterfall and Prompt dialogs (options C and D).

• WaterfallDialog provides a simple, linear sequence of steps to collect multiple inputs. You can branch the flow based on the item type and decide which steps to execute next.
• Prompt dialogs (e.g., TextPrompt, NumberPrompt) handle asking for input and basic validation, reducing custom parsing code.
• Using a waterfall flow with prompts lets you minimize development effort: you define the sequence once and use prompts to gather the required details for each item type, rather than building complex adaptive logic.

Question 35:

• Correct answer: Waterfall (option C), i.e., use a WaterfallDialog.
• Why: A product setup process is a linear, guided flow. A WaterfallDialog runs a fixed sequence of steps (prompts, validations, and results) in order, which is ideal for collecting setup details step-by-step and finalizing the configuration.
• How it works:

• Why not the others:

Question 34:
Correct answers: Adaptive Card (D) and Dialog (E).
Explanation:

• Adaptive Card: Lets you render rich content, including multiple options each with an image. You can include images for every option and actions (like Submit) to capture the user’s choice.
• Dialog: Provides the flow control to show the card, wait for the user to pick an option, and then branch to the appropriate next steps. It manages multi-turn interactions and state.

• an entity: Used for extracting data from user input, not for presenting options with images.
• an Azure function: Backend code, not for UI presentation.
• an utterance: A user input phrase, not for building the option list.

Question 76:

• Correct answer: Spatial Analysis in Azure AI Vision

• Why this is correct:

• Why not the others:

• Quick implementation note:

Question 72:
Question 72 asks which Python package to add to App1 to use an Azure AI service model (Model1) that identifies text intent.

• Correct answer: azure-ai-language-conversations (Option B)

• The task uses the Language Service’s Conversation Analysis feature to identify intent from text. The appropriate Python SDK to call a deployed Conversation model is the azure-ai-language-conversations package.
• Other options are for different capabilities:

• Install: pip install azure-ai-language-conversations
• Use the ConversationAnalysisClient to call your deployed model (

Question 61:

• Correct answer: Azure Cognitive Services.

• Why: A single multi-service Azure Cognitive Services resource provides one endpoint and one credential that can be used to access multiple APIs (e.g., Decision and Language, plus others like Content Moderator). This meets the requirement of using a single endpoint/credential.

• Why not the others: If you created separate resources for each API (e.g., separate Language, Speech, Content Moderator resources), you’d have multiple endpoints and keys, violating the “single endpoint and credential” requirement. All listed services are part of Cognitive Services, so they share a single Cognitive Services resource.