Quiz Microsoft Azure Developer Advanced Solutions

===================================================
Topic 1, Case Study ABackground
Best For You Organics Company is a global restaurant franchise that has multiple locations.
The company wants to enhance user experiences and vendor integrations.
The company plans to implement automated mobile ordering and delivery services.
Best For You Organics hosts an Azure web app at the URL https://www.bestforyouorgdnics.com.
Users can use the web app to browse restaurant locations, menu items, nutritional, information, and
company information. The company developed and deployed a cross-platform mobile app.
Requirements
Chatbot
You must develop a cbatbot by using the Bot Builder SDK and Language Understanding Intelligence
Service (LUIS). The chatbot must allow users to order food for pickup or delivery.
The chatbot must meet the following requirements:
* Ensure that chatbot endpoint can be accessed only by the Bot framework connector
* Use natural language processing and speech recognition so that users can interact with the chatbot
by using text and voice. Processing must be server-based.
* Alert users about promotions at local restaurants.
* Enable users to place an order for delivery or pickup t/y using their voice.
* Greet the user upon sign in by displaying a graphical interface that contains action buttons.
* The chatbot greeting interface must match the formatting of the following example:

Tap the image to zoom
Vendor API
Vendors receive and provide updates for the restaurant inventory and delivery services by using
Azure API Management hosted APIs. Each vendor uses their own subscription to access each of the
APIs.
APIs must meet the following conditions:
* API usage must not exceed 5,000 calls and 50,000 kilobytes of bandwidth per hour per vendor.
* If a vendor is nearing the number of calls or bandwidth limit, the API must trigger email
notifications to the vendor.
* APIs must prevent API usage spikes on a per-subscription basis by limiting the call rate to 100 calls
per minute.
* The Inventory API must be written by using ASP.NET Core and Node.js.
* The API must be updated to provide an interface to Azure SQL Database. Database objects must be
managed by using code.
* The Delivery API must be protected by using the O Auth 2.0 protocol with Azure Active Directory
(Azure AD) when called from the Azure web app. You register the Delivery API and web app in Azure
AD.
You enable O Auth 2.0 in the web app.
* The delivery API must update the Products table, the Vendor transactions table, and the Billing
table in a single transaction.
Architecture
The Best For You Organics Company architecture team has created the following diagram depicting
the expected deployments into Azure:

Tap the image to zoom
Issues
Delivery API
The Delivery API intermittently throws the following exception:

Tap the image to zoom
App code
Chatbot greeting
The chalbot's greeting does not show the user's name. You need to debug the Chatbot locally.
Language processing
Users report that the bot fails to understand when a customer attempts to order dishes that use
Italian names.
Relevant portions of the app files are shown below. Line numbers are included for reference only and
include a two-character prefix that denotes the specific file to which they belong.
Startup.cs

Tap the image to zoom
Explanation:

Explanation:
Scenario: The chatbot's greeting does not show the user's name. You need to debug the chatbot
locally.
Debug your bot using an integrated development environment (IDE) such as Visual Studio or Visual
Studio Code and the Bot Framework Emulator. You can use these methods to debug any bot locally.
References:
https://docs.microsoft.com/en-us/azure/bot-service/bot-service-debug-bot?view=azure-bot-service-
4.0

Explanation:
Scenario:
If a vendor is nearing the number of calls or bandwidth limit, the API must trigger email notifications
to the vendor.
(API usage must not exceed 5,000 calls and 50,000 kilobytes of bandwidth per hour per vendor.) In
Azure API Management (APIM), policies are a powerful capability of the system that allow the
publisher to change the behavior of the API through configuration. Policies are a collection of
Statements that are executed sequentially on the request or response of an API. Popular Statements
include format conversion from XML to JSON and call rate limiting to restrict the amount of incoming
calls from a developer. Many more policies are available out of the box.
References:
https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-policies

Explanation:
Use a custom outbound Azure API Management policy.
Scenario:
If a vendor is nearing the number of calls or bandwidth limit, the API must trigger email notifications
to the vendor.
(API usage must not exceed 5,000 calls and 50,000 kilobytes of bandwidth per hour per vendor.)
References:
https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-policies
===================================================
Topic 2, Case Study B
Background
You are developer for Prose ware, Inc. You are developing an application that applies a set of
governance policies for Prosware's internal services, external services, and applications. The
application will also provide a shared library for common functionality.
Requirements
You are a developer for Proseware, Inc. You are developing an application that applies a set of
governance policies for Proseware's services, and applications. I he application will also provide a
shared library for common functionality.
Policy service
You develop and deploy a stateful ASP.NET Core 2.1 web application named Policy service to an
Azure App Service Web App. The application reacts to events from Azure Event Grid and performs
policy actions based on those events.
The application must include the Event Grid Event ID field in all Application Insights telemetry.
Policy service must use Application Insights to automatically scale with the number of policy actions
that it is performing.
Policies
Log policy
All Azure App Service Web Apps must write togs to Azure Blob storage. Al log files should be saved to
a named log drop. Logs must remains in the container for 15 days.
Authentication events
Authentication events are used to monitor users signing in and signing out. All authentication events
must be processed by Policy service. Sign outs must be processed as quickly as possible.
PolicyLib
You have a shared library named PolicyLib that contains functionality common to all ASP.NET Core
web services and applications. The PolicyLib library must:
* Exclude non-user actions from Application Insights telemetry.
* Provide methods that allow a web service to scale itself.
* Ensure that scaling actions do not disrupt application usage.
Other
Anomaly detection service
You have an anomaly detection service that analyzes log information for anomalies. It is implemented
as an Azure Machine Learning model. The model is deployed as a web service.
If an anomaly is detected, an Azure Function that emails administrators is called by using an HTTP
WebHook.
Health monitoring
All web applications and services have health monitoring at the /health service endpoint.
Issues
Policy loss
When you deploy Policy service, policies may not be applied if they were in the process of being
applied during the deployment.
Performance issue
When under heavy load, the anomaly detection service undergoes slowdowns and rejects
connections.
Notification latency
Users report that anomaly detection emails can sometimes arrive several minutes after an anomaly is
detected.
App code
EnventGridController.cs
Relevant portions of the app files are shown below. Line numbers are included for reference only and
include a two-character prefix that denotes the specific file to which they belong.

Tap the image to zoom

Tap the image to zoom
LoginEvents.cs
Relevant portions of the app files are shown below. Line numbers are included for reference only and
include a two-character prefix that denotes the specific file to which they belong.

Tap the image to zoom