Explanation

Box 1: Azure Functions
Azure Function is a (serverless) service to host functions (little piece of code) that can be used for e. g. event driven applications.
General rule is always difficult since everything depends on your requirement but if you have to analyze a data stream, you should take a look at Azure Stream Analytics and if you want to implement something like a serverless event driven or timer-based application, you should check Azure Function or Logic Apps.
Note: Azure IoT Edge allows you to deploy complex event processing, machine learning, image recognition, and other high value AI without writing it in-house. Azure services like Azure Functions, Azure Stream Analytics, and Azure Machine Learning can all be run on-premises via Azure IoT Edge.
Box 2: An Azure IoT Edge device
Azure IoT Edge moves cloud analytics and custom business logic to devices so that your organization can focus on business insights instead of data management.
References:
https://docs.microsoft.com/en-us/azure/iot-edge/about-iot-edge

Explanation:
Box 1: Self-hosted Integration Runtime
A self-hosted IR is capable of running copy activity between a cloud data stores and a data store in private network.
Not Azure-SSIS Integration Runtime, as you would need to write custom code.
Box 2: Azure Logic Apps
Azure Logic Apps helps you orchestrate and integrate different services by providing 100+ ready-to-use connectors, ranging from on-premises SQL Server or SAP to Microsoft Cognitive Services.
Incorrect:
Not Azure API Management: Use Azure API Management as a turnkey solution for publishing APIs to external and internal customers.
References:
https://docs.microsoft.com/en-us/azure/data-factory/concepts-integration-runtime
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-examples-and-scenarios
Topic 1, Contoso Case Study
Overview
Contoso. Ltd. has an office in New York to serve its North American customers and an office in Paris to serve its European customers.
Existing Environment
Contoso. Ltd. has an office in New York to serve its North American customers and an office in Paris to serve its European customers.
Infrastructure
Each office has a small data center that hosts Active Directory services and a few off-the-shelf software solutions used by internal users.
The network contains a single Active Directory forest that contains a single domain named contoso.com. Azure Active Directory (Azure AD) Connect is used to extend identity management to Azure.
The company has an Azure subscription. Each office has an Azure ExpressRoute connection to the subscription. The New York office connects to a virtual network hosted in the US East 2 Azure region. The Paris office connects to a virtual network hosted in the West Europe Azure region.
The New York office has an Azure Stack Development Kit (ASDK) deployment that is used for development and testing.
Current Business Model
Contoso has a web app named Bookings hosted in an App Service Environment (ASE). The ASE is in the virtual network in the East US 2 region. Contoso employees and customers use Bookings to reserve hotel rooms.
Data Environment
Bookings connects to a Microsoft SQL Server database named hotelDB in the New York office.
The database has a view named vwAvailability that consolidates columns from three tables named Hotels, Rooms, and RoomAvailability. The database contains data that was collected during the last 20 years.
Problem Statements
Contoso identifies the following issues with its current business model:
* European users report that access to Bookings is slow, and they lose customers who must wait on the phone while they search for available rooms.
* Users report that Bookings was unavailable during an outage in the New York data center for more than 24 hours.
Requirements
Contoso identifies the following issues with its current business model:
* European users report that access to Bookings is slow, and they lose customers who must wait on the phone while they search for available rooms.
Business Goals
* Users report that Bookings was unavailable during an outage in the New York data center for more than 24 hours.
Contoso wants to provide a new version of the Bookings app that will provide a highly available, reliable service for booking travel packages by interacting with a chatbot named Butler.
Contoso plans to move all production workloads to the cloud.
Technical Requirements
Contoso identifies the following technical requirements:
* Data scientists must test Butler by using ASDK.
* Whenever possible, solutions must minimize costs.
* Butler must greet users by name when they first connect.
* Butler must be able to handle up to 10.000 messages a day.
* Butler must recognize the users' intent based on basic utterances.
* All configurations to the Azure Bot Service must be logged centrally.
* Whenever possible, solutions must use the principle of least privilege.
* Internal users must be able to access Butler by using Microsoft Skype for Business.
* The new Bookings app must provide a user interface where users can interact with Butler.
* Users in an Azure AD group named KeyManagers must be able to manage keys for all Azure Cognitive Services.
* Butler must provide users with the ability to reserve a room, cancel a reservation, and view existing reservations.
* The new Bookings app must be available to users in North America and Europe if a single data center or Azure region fails.
* For continuous improvement, you must be able to test Butler by sending sample utterances and comparing the chatbot's responses to the actua intent.

Explanation

References:
https://docs.microsoft.com/en-us/azure/storage/common/storage-auth