Which three actions should you perform in sequence?
###BeginCaseStudy###
Testlet 1
Background:
You are the new cloud architect for Fourth Coffee. The company hosts an on-premises ASP.NET MVC web
application to allow online purchases and to support their retail store operations.
The new chief information officer (CIO) has announced several initiatives for the new year, including a new
mobile application, online training for retail store employees, and moving the current web application and other
services to the cloud.
The marketing team hopes to see an increase in the up-time for the web application. The team would also like
to allow users to use social logins in addition to the current username and password system.
Fourth Coffee has chosen Microsoft Azure to support their initiatives.
Current environment
In the Azure portal, you create an Azure Mobile App for the API. You create a Service Bus queue in Azure and
install the Azure Storage SDK for Node.js.
Problem statements
The mobile team attempts to use continuous deployment with the Azure App Service and new API project. They
receive the following error message: “Unable to access http://fourthcoffeeapi.azurewebsites.net/: Failed to
connect to https://fourthcoffeeapi.scm.azurewebsites.net/”
Business requirements
Web Application
You must increase up-time for the application.
The application must support additional regions and languages.
Marketing must be able to validate the web application before updates to the application are published to the
production environment.
Mobile
The marketing team must be able to send frequent and timely updates to specific users and devices
including Apple iPad, iPhone, Android, Windows, and Windows Phone devices.
Users must be able to use their social accounts to sign in to the application. You must support LinkedIn,
Facebook and Google logons.
The application must remain responsive, even during peak periods.
Training
Video streaming content must be made available and streamed to employee’s browsers. Training content must
only include on-demand streaming. There will be no live content.
Technical requirements
Web Application
You must update the deployment process to support cloud deployments.
All data must be formatted as JSON during transport.
You must implement Team Foundation Version Control (TFVC) as the version control system for the web
application.
Incoming messages to the API must be persisted to queue storage to ensure they are delivered and
processed. You must restrict the size of messages between the mobile app and the API to no more than 5
gigabytes (GB).
The web application must use geo-redundant replication.
Mobile
You must use Node.js as a technology platform. You must support all mobile initiatives when possible.
You must implement Git as the version control system for the mobile app.
You must develop a REST API by using Node.js Express, and MongoDB. You must use the Mobile Apps
feature of the Azure App Service to host the API in Standard mode.
You must implement the following Push Notification Services by using Azure Media Services:
– Apple Push Notification Service (APNS) for iPad and iPhone devices- Google Cloud Messaging service (GCM) for Android devices
– Windows Notification Service (WNS) for Windows devices
– Microsoft Push Notification Service (MPNS) for Windows Phone devices
Security and disaster Recovery
You must integrate the on-premises Active Directory Domain Services with Azure Active Directory (Azure
AD).
You must implement the latest federated identity standards to provide authentication and authorization to
applications.
You must implement Multi-Factor Authentication.
The web application and the API must be able to recover from a disaster.
Scaling
The web application and API must auto-scale according to the following rules:
Scale up by one instance if CPU is above 70%.
Scale down by one instance if CPU is below 50%.
Training
Streaming must include Content Delivery Network (CDN) capabilities to support global locations.
Content must be encrypted and protected by using AES and PlayReady.
Streaming must include one gigabit (GB) per second of dedicated egress capacity.
All videos must use adaptive bitrate MP4 encoded content and include a streaming manifest file (.ism).
You must support the following streaming formats for video files: MPEG DASH, HLS, Smooth Streaming,
HDS. You must not to re-encode the content.
###EndCaseStudy###
DRAG DROP
Marketing is ready to start their web application validations and is excited to be expanding globally.
You need to support the global web application requirements.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of
actions to the answer area and arrange them in the correct order.Select and Place:
Which technology should you use?
###BeginCaseStudy###
Testlet 1
Background:
You are the new cloud architect for Fourth Coffee. The company hosts an on-premises ASP.NET MVC web
application to allow online purchases and to support their retail store operations.
The new chief information officer (CIO) has announced several initiatives for the new year, including a new
mobile application, online training for retail store employees, and moving the current web application and other
services to the cloud.
The marketing team hopes to see an increase in the up-time for the web application. The team would also like
to allow users to use social logins in addition to the current username and password system.
Fourth Coffee has chosen Microsoft Azure to support their initiatives.
Current environment
In the Azure portal, you create an Azure Mobile App for the API. You create a Service Bus queue in Azure and
install the Azure Storage SDK for Node.js.
Problem statements
The mobile team attempts to use continuous deployment with the Azure App Service and new API project. They
receive the following error message: “Unable to access http://fourthcoffeeapi.azurewebsites.net/: Failed to
connect to https://fourthcoffeeapi.scm.azurewebsites.net/”
Business requirements
Web Application
You must increase up-time for the application.
The application must support additional regions and languages.
Marketing must be able to validate the web application before updates to the application are published to the
production environment.
Mobile
The marketing team must be able to send frequent and timely updates to specific users and devices
including Apple iPad, iPhone, Android, Windows, and Windows Phone devices.
Users must be able to use their social accounts to sign in to the application. You must support LinkedIn,
Facebook and Google logons.
The application must remain responsive, even during peak periods.
Training
Video streaming content must be made available and streamed to employee’s browsers. Training content must
only include on-demand streaming. There will be no live content.
Technical requirements
Web Application
You must update the deployment process to support cloud deployments.
All data must be formatted as JSON during transport.
You must implement Team Foundation Version Control (TFVC) as the version control system for the web
application.
Incoming messages to the API must be persisted to queue storage to ensure they are delivered and
processed. You must restrict the size of messages between the mobile app and the API to no more than 5
gigabytes (GB).
The web application must use geo-redundant replication.
Mobile
You must use Node.js as a technology platform. You must support all mobile initiatives when possible.
You must implement Git as the version control system for the mobile app.
You must develop a REST API by using Node.js Express, and MongoDB. You must use the Mobile Apps
feature of the Azure App Service to host the API in Standard mode.
You must implement the following Push Notification Services by using Azure Media Services:
– Apple Push Notification Service (APNS) for iPad and iPhone devices- Google Cloud Messaging service (GCM) for Android devices
– Windows Notification Service (WNS) for Windows devices
– Microsoft Push Notification Service (MPNS) for Windows Phone devices
Security and disaster Recovery
You must integrate the on-premises Active Directory Domain Services with Azure Active Directory (Azure
AD).
You must implement the latest federated identity standards to provide authentication and authorization to
applications.
You must implement Multi-Factor Authentication.
The web application and the API must be able to recover from a disaster.
Scaling
The web application and API must auto-scale according to the following rules:
Scale up by one instance if CPU is above 70%.
Scale down by one instance if CPU is below 50%.
Training
Streaming must include Content Delivery Network (CDN) capabilities to support global locations.
Content must be encrypted and protected by using AES and PlayReady.
Streaming must include one gigabit (GB) per second of dedicated egress capacity.
All videos must use adaptive bitrate MP4 encoded content and include a streaming manifest file (.ism).
You must support the following streaming formats for video files: MPEG DASH, HLS, Smooth Streaming,
HDS. You must not to re-encode the content.
###EndCaseStudy###
You need to support web and mobile application secure logons.
Which technology should you use?
Which two services should you use?
###BeginCaseStudy###
Testlet 1
Background:
You are the new cloud architect for Fourth Coffee. The company hosts an on-premises ASP.NET MVC web
application to allow online purchases and to support their retail store operations.
The new chief information officer (CIO) has announced several initiatives for the new year, including a new
mobile application, online training for retail store employees, and moving the current web application and other
services to the cloud.
The marketing team hopes to see an increase in the up-time for the web application. The team would also like
to allow users to use social logins in addition to the current username and password system.
Fourth Coffee has chosen Microsoft Azure to support their initiatives.
Current environment
In the Azure portal, you create an Azure Mobile App for the API. You create a Service Bus queue in Azure and
install the Azure Storage SDK for Node.js.
Problem statements
The mobile team attempts to use continuous deployment with the Azure App Service and new API project. They
receive the following error message: “Unable to access http://fourthcoffeeapi.azurewebsites.net/: Failed to
connect to https://fourthcoffeeapi.scm.azurewebsites.net/”
Business requirements
Web Application
You must increase up-time for the application.
The application must support additional regions and languages.
Marketing must be able to validate the web application before updates to the application are published to the
production environment.
Mobile
The marketing team must be able to send frequent and timely updates to specific users and devices
including Apple iPad, iPhone, Android, Windows, and Windows Phone devices.
Users must be able to use their social accounts to sign in to the application. You must support LinkedIn,
Facebook and Google logons.
The application must remain responsive, even during peak periods.
Training
Video streaming content must be made available and streamed to employee’s browsers. Training content must
only include on-demand streaming. There will be no live content.
Technical requirements
Web Application
You must update the deployment process to support cloud deployments.
All data must be formatted as JSON during transport.
You must implement Team Foundation Version Control (TFVC) as the version control system for the web
application.
Incoming messages to the API must be persisted to queue storage to ensure they are delivered and
processed. You must restrict the size of messages between the mobile app and the API to no more than 5
gigabytes (GB).
The web application must use geo-redundant replication.
Mobile
You must use Node.js as a technology platform. You must support all mobile initiatives when possible.
You must implement Git as the version control system for the mobile app.
You must develop a REST API by using Node.js Express, and MongoDB. You must use the Mobile Apps
feature of the Azure App Service to host the API in Standard mode.
You must implement the following Push Notification Services by using Azure Media Services:
– Apple Push Notification Service (APNS) for iPad and iPhone devices- Google Cloud Messaging service (GCM) for Android devices
– Windows Notification Service (WNS) for Windows devices
– Microsoft Push Notification Service (MPNS) for Windows Phone devices
Security and disaster Recovery
You must integrate the on-premises Active Directory Domain Services with Azure Active Directory (Azure
AD).
You must implement the latest federated identity standards to provide authentication and authorization to
applications.
You must implement Multi-Factor Authentication.
The web application and the API must be able to recover from a disaster.
Scaling
The web application and API must auto-scale according to the following rules:
Scale up by one instance if CPU is above 70%.
Scale down by one instance if CPU is below 50%.
Training
Streaming must include Content Delivery Network (CDN) capabilities to support global locations.
Content must be encrypted and protected by using AES and PlayReady.
Streaming must include one gigabit (GB) per second of dedicated egress capacity.
All videos must use adaptive bitrate MP4 encoded content and include a streaming manifest file (.ism).
You must support the following streaming formats for video files: MPEG DASH, HLS, Smooth Streaming,
HDS. You must not to re-encode the content.
###EndCaseStudy###
You need to choose an Azure service for the training initiative.
Which two services should you use? Each correct answer presents part of the solution.
Which three actions should you recommend performing in …
###BeginCaseStudy###
Testlet 1
Background
Overview
Northwind Electric Cars is the premier provider of private, low-cost transportation in Denver. Northwind drivers
are company employees who work together as a team. The founding partners believe that by hiring their drivers
as employees, their drivers focus on providing a great customer experience. Northwind Electric Cars has a
reputation for offering fast, reliable, and friendly service, due largely to their extensive network of drivers and
their proprietary dispatching software named NorthRide.
Northwind Electric Cars drivers depend on frequent, automatic updates for the NorthRide mobile app. The
Northwind management team is concerned about unplanned system downtime and slow connection speeds
caused by high usage. Additionally, Northwind’s in-house data storage solution is unsustainable because of the
new influx of customer data that is retained. Data backups are made periodically on DVDs and stored onpremises at corporate headquarters.
Apps
NorthRide App
Northwind drivers use the NorthRide app to meet customer pickup requests. The app uses a GPS transponder
in each Northwind vehicle and Bing Maps APIs to monitor the location of each vehicle in the fleet in real time.
NorthRide allows Northwind dispatchers to optimize their driver coverage throughout the city.
When new customers call, the dispatcher enters their pickup locations into NorthRide. NorthRide identifies the
closest available driver. The dispatcher then contacts the driver with the pick-up details. This process usually
results in a pick-up time that is far faster than the industry average.
Drivers use NorthRide to track the number of miles they drive and the number of customers they transport.
Drivers also track their progress towards their established goals, which are measured by using key
performance indicators (KPIs).
NorthRide App 2.0
Northwind Electric Cars is growing quickly. New callers often wait for their calls to be answered because the
dispatchers are contacting their drivers to arrange pickups for other customers.
To support the growth of the business, Northwind’s development team completes an overhaul of the NorthRide
system that it has named NorthRide 2.0. When a dispatcher enters a customer’s pickup location, the address
and driving directions are automatically sent to the driver who is closest to the customer’s pickup location.
Drivers indicate their availability on the NorthRide mobile app and can view progress towards their KPI’s in real
time. Drivers can also record customer ratings and feedback for each pickup.
Business Requirements
Apps
NorthRideFinder App
Northwind Electric Cars needs a customer-facing website and mobile app that allows customers to schedule
pickups. Customers should also be able to create profiles that will help ensure the customer gets a ride faster
by storing customer information.
Predictor App
Northwind Electric Cars needs a new solution named Predictor. Predictor is an employee-facing mobile app.
The app predicts periods of high usage and popular pickup locations and provides various ways to view this
predictive data. Northwind uses this information to better distribute its drivers. Northwind wants to use the latest
Azure technology to create this solution.
Other Requirements
On-premises data must be constantly backed up.
Mobile data must be protected from loss, even if connectivity with the backend is lost.Dispatch offices need to have seamless access to both their primary data center and the applications and
services that are hosted in the Azure cloud.
Connectivity needs to be redundant to on-premises and cloud services, while providing a way for each
dispatch office to continue to operate even if one or all of the connection options fail.
The management team requires that operational data is accessible 24/7 from any office location.
Technical Requirements
Apps and Website
NorthRide / NorthRideFinder Apps:
The solution must support on-premises and Azure data storage.
The solution must scale as necessary based on the current number of concurrent users.
Customer pickup requests from NorthRideFinder must be asynchronous.
The customer pickup request system will be high in volume, and each request will have a short life span.
Data for NorthRideFinder must be protected during a loss of connectivity.
NorthRide users must authenticate to the company’s Azure Active Directory.
Northwind Public Website
The customer website must use a WebJob to process profile images into thumbnails
The customer website must be developed with lowest cost and difficulty in mind.
The customer website must automatically scale to minimize response times for customers.
Other Requirements
Data Storage:
The data storage must interface with an on-premises Microsoft SQL backend database.
A disaster recovery system needs to be in place for large amounts of data that will backup to Azure.
Backups must be fully automated and managed the Azure Management Portal.
The recovery system for company data must use a hybrid solution to back up both the on-premises
Microsoft SQL backend and any Azure storage.
Predictive Routing:
An Azure solution must be used for prediction systems.
Predictive analytics must be published as a web service and accessible by using the REST API.
Security:
The NorthRide app must use an additional level of authentication other than the employee’s password.
Access must be secured in NorthRide without opening a firewall port.
Company policy prohibits inbound connections from internet callers to the on-premises network.
Customer usernames in NorthRideFinder cannot exceed 10 characters.
Customer data in NorthRideFinder can be received only by the user ID that is associated with the data.
###EndCaseStudy###
DRAG DROP
You need to recommend the steps required to deploy the Northwind Electric Cars website.
Which three actions should you recommend performing in sequence? To answer, move the appropriate actions
from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
which four actions should you perform in sequence?
###BeginCaseStudy###
Testlet 1
Background:
You are the new cloud architect for Fourth Coffee. The company hosts an on-premises ASP.NET MVC web
application to allow online purchases and to support their retail store operations.
The new chief information officer (CIO) has announced several initiatives for the new year, including a new
mobile application, online training for retail store employees, and moving the current web application and other
services to the cloud.
The marketing team hopes to see an increase in the up-time for the web application. The team would also like
to allow users to use social logins in addition to the current username and password system.
Fourth Coffee has chosen Microsoft Azure to support their initiatives.
Current environment
In the Azure portal, you create an Azure Mobile App for the API. You create a Service Bus queue in Azure and
install the Azure Storage SDK for Node.js.
Problem statements
The mobile team attempts to use continuous deployment with the Azure App Service and new API project. They
receive the following error message: “Unable to access http://fourthcoffeeapi.azurewebsites.net/: Failed to
connect to https://fourthcoffeeapi.scm.azurewebsites.net/”
Business requirements
Web Application
You must increase up-time for the application.
The application must support additional regions and languages.
Marketing must be able to validate the web application before updates to the application are published to the
production environment.
Mobile
The marketing team must be able to send frequent and timely updates to specific users and devices
including Apple iPad, iPhone, Android, Windows, and Windows Phone devices.
Users must be able to use their social accounts to sign in to the application. You must support LinkedIn,
Facebook and Google logons.
The application must remain responsive, even during peak periods.
Training
Video streaming content must be made available and streamed to employee’s browsers. Training content must
only include on-demand streaming. There will be no live content.
Technical requirements
Web Application
You must update the deployment process to support cloud deployments.
All data must be formatted as JSON during transport.
You must implement Team Foundation Version Control (TFVC) as the version control system for the web
application.
Incoming messages to the API must be persisted to queue storage to ensure they are delivered and
processed. You must restrict the size of messages between the mobile app and the API to no more than 5
gigabytes (GB).
The web application must use geo-redundant replication.
Mobile
You must use Node.js as a technology platform. You must support all mobile initiatives when possible.
You must implement Git as the version control system for the mobile app.
You must develop a REST API by using Node.js Express, and MongoDB. You must use the Mobile Apps
feature of the Azure App Service to host the API in Standard mode.
You must implement the following Push Notification Services by using Azure Media Services:
– Apple Push Notification Service (APNS) for iPad and iPhone devices- Google Cloud Messaging service (GCM) for Android devices
– Windows Notification Service (WNS) for Windows devices
– Microsoft Push Notification Service (MPNS) for Windows Phone devices
Security and disaster Recovery
You must integrate the on-premises Active Directory Domain Services with Azure Active Directory (Azure
AD).
You must implement the latest federated identity standards to provide authentication and authorization to
applications.
You must implement Multi-Factor Authentication.
The web application and the API must be able to recover from a disaster.
Scaling
The web application and API must auto-scale according to the following rules:
Scale up by one instance if CPU is above 70%.
Scale down by one instance if CPU is below 50%.
Training
Streaming must include Content Delivery Network (CDN) capabilities to support global locations.
Content must be encrypted and protected by using AES and PlayReady.
Streaming must include one gigabit (GB) per second of dedicated egress capacity.
All videos must use adaptive bitrate MP4 encoded content and include a streaming manifest file (.ism).
You must support the following streaming formats for video files: MPEG DASH, HLS, Smooth Streaming,
HDS. You must not to re-encode the content.
###EndCaseStudy###
DRAG DROP
You need to scale the API.
In the Azure portal, which four actions should you perform in sequence? To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
Which five steps should you perform in sequence?
###BeginCaseStudy###
Testlet 1
Background:
You are the new cloud architect for Fourth Coffee. The company hosts an on-premises ASP.NET MVC web
application to allow online purchases and to support their retail store operations.
The new chief information officer (CIO) has announced several initiatives for the new year, including a new
mobile application, online training for retail store employees, and moving the current web application and other
services to the cloud.
The marketing team hopes to see an increase in the up-time for the web application. The team would also like
to allow users to use social logins in addition to the current username and password system.
Fourth Coffee has chosen Microsoft Azure to support their initiatives.
Current environment
In the Azure portal, you create an Azure Mobile App for the API. You create a Service Bus queue in Azure and
install the Azure Storage SDK for Node.js.
Problem statements
The mobile team attempts to use continuous deployment with the Azure App Service and new API project. They
receive the following error message: “Unable to access http://fourthcoffeeapi.azurewebsites.net/: Failed to
connect to https://fourthcoffeeapi.scm.azurewebsites.net/”
Business requirements
Web Application
You must increase up-time for the application.
The application must support additional regions and languages.
Marketing must be able to validate the web application before updates to the application are published to the
production environment.
Mobile
The marketing team must be able to send frequent and timely updates to specific users and devices
including Apple iPad, iPhone, Android, Windows, and Windows Phone devices.
Users must be able to use their social accounts to sign in to the application. You must support LinkedIn,
Facebook and Google logons.
The application must remain responsive, even during peak periods.
Training
Video streaming content must be made available and streamed to employee’s browsers. Training content must
only include on-demand streaming. There will be no live content.
Technical requirements
Web Application
You must update the deployment process to support cloud deployments.
All data must be formatted as JSON during transport.
You must implement Team Foundation Version Control (TFVC) as the version control system for the web
application.
Incoming messages to the API must be persisted to queue storage to ensure they are delivered and
processed. You must restrict the size of messages between the mobile app and the API to no more than 5
gigabytes (GB).
The web application must use geo-redundant replication.
Mobile
You must use Node.js as a technology platform. You must support all mobile initiatives when possible.
You must implement Git as the version control system for the mobile app.
You must develop a REST API by using Node.js Express, and MongoDB. You must use the Mobile Apps
feature of the Azure App Service to host the API in Standard mode.
You must implement the following Push Notification Services by using Azure Media Services:
– Apple Push Notification Service (APNS) for iPad and iPhone devices- Google Cloud Messaging service (GCM) for Android devices
– Windows Notification Service (WNS) for Windows devices
– Microsoft Push Notification Service (MPNS) for Windows Phone devices
Security and disaster Recovery
You must integrate the on-premises Active Directory Domain Services with Azure Active Directory (Azure
AD).
You must implement the latest federated identity standards to provide authentication and authorization to
applications.
You must implement Multi-Factor Authentication.
The web application and the API must be able to recover from a disaster.
Scaling
The web application and API must auto-scale according to the following rules:
Scale up by one instance if CPU is above 70%.
Scale down by one instance if CPU is below 50%.
Training
Streaming must include Content Delivery Network (CDN) capabilities to support global locations.
Content must be encrypted and protected by using AES and PlayReady.
Streaming must include one gigabit (GB) per second of dedicated egress capacity.
All videos must use adaptive bitrate MP4 encoded content and include a streaming manifest file (.ism).
You must support the following streaming formats for video files: MPEG DASH, HLS, Smooth Streaming,
HDS. You must not to re-encode the content.
###EndCaseStudy###
DRAG DROP
You need to persist the API messages.
Which five steps should you perform in sequence? To answer, move the appropriate actions from the list of
actions to the answer area and arrange them in the correct order.
Select and Place:
Which two actions should you perform?
###BeginCaseStudy###
Testlet 1
Background:
You are the new cloud architect for Fourth Coffee. The company hosts an on-premises ASP.NET MVC web
application to allow online purchases and to support their retail store operations.
The new chief information officer (CIO) has announced several initiatives for the new year, including a new
mobile application, online training for retail store employees, and moving the current web application and other
services to the cloud.
The marketing team hopes to see an increase in the up-time for the web application. The team would also like
to allow users to use social logins in addition to the current username and password system.
Fourth Coffee has chosen Microsoft Azure to support their initiatives.
Current environment
In the Azure portal, you create an Azure Mobile App for the API. You create a Service Bus queue in Azure and
install the Azure Storage SDK for Node.js.
Problem statements
The mobile team attempts to use continuous deployment with the Azure App Service and new API project. They
receive the following error message: “Unable to access http://fourthcoffeeapi.azurewebsites.net/: Failed to
connect to https://fourthcoffeeapi.scm.azurewebsites.net/”
Business requirements
Web Application
You must increase up-time for the application.
The application must support additional regions and languages.
Marketing must be able to validate the web application before updates to the application are published to the
production environment.
Mobile
The marketing team must be able to send frequent and timely updates to specific users and devices
including Apple iPad, iPhone, Android, Windows, and Windows Phone devices.
Users must be able to use their social accounts to sign in to the application. You must support LinkedIn,
Facebook and Google logons.
The application must remain responsive, even during peak periods.
Training
Video streaming content must be made available and streamed to employee’s browsers. Training content must
only include on-demand streaming. There will be no live content.
Technical requirements
Web Application
You must update the deployment process to support cloud deployments.
All data must be formatted as JSON during transport.
You must implement Team Foundation Version Control (TFVC) as the version control system for the web
application.
Incoming messages to the API must be persisted to queue storage to ensure they are delivered and
processed. You must restrict the size of messages between the mobile app and the API to no more than 5
gigabytes (GB).
The web application must use geo-redundant replication.
Mobile
You must use Node.js as a technology platform. You must support all mobile initiatives when possible.
You must implement Git as the version control system for the mobile app.
You must develop a REST API by using Node.js Express, and MongoDB. You must use the Mobile Apps
feature of the Azure App Service to host the API in Standard mode.
You must implement the following Push Notification Services by using Azure Media Services:
– Apple Push Notification Service (APNS) for iPad and iPhone devices- Google Cloud Messaging service (GCM) for Android devices
– Windows Notification Service (WNS) for Windows devices
– Microsoft Push Notification Service (MPNS) for Windows Phone devices
Security and disaster Recovery
You must integrate the on-premises Active Directory Domain Services with Azure Active Directory (Azure
AD).
You must implement the latest federated identity standards to provide authentication and authorization to
applications.
You must implement Multi-Factor Authentication.
The web application and the API must be able to recover from a disaster.
Scaling
The web application and API must auto-scale according to the following rules:
Scale up by one instance if CPU is above 70%.
Scale down by one instance if CPU is below 50%.
Training
Streaming must include Content Delivery Network (CDN) capabilities to support global locations.
Content must be encrypted and protected by using AES and PlayReady.
Streaming must include one gigabit (GB) per second of dedicated egress capacity.
All videos must use adaptive bitrate MP4 encoded content and include a streaming manifest file (.ism).
You must support the following streaming formats for video files: MPEG DASH, HLS, Smooth Streaming,
HDS. You must not to re-encode the content.
###EndCaseStudy###
You need to support the disaster recovery requirements of the web application and API.
Which two actions should you perform? Each correct answer presents part of the solution.
Which two solutions should you use?
###BeginCaseStudy###
Testlet 1
Background
Overview
Northwind Electric Cars is the premier provider of private, low-cost transportation in Denver. Northwind drivers
are company employees who work together as a team. The founding partners believe that by hiring their drivers
as employees, their drivers focus on providing a great customer experience. Northwind Electric Cars has a
reputation for offering fast, reliable, and friendly service, due largely to their extensive network of drivers and
their proprietary dispatching software named NorthRide.
Northwind Electric Cars drivers depend on frequent, automatic updates for the NorthRide mobile app. The
Northwind management team is concerned about unplanned system downtime and slow connection speeds
caused by high usage. Additionally, Northwind’s in-house data storage solution is unsustainable because of the
new influx of customer data that is retained. Data backups are made periodically on DVDs and stored onpremises at corporate headquarters.
Apps
NorthRide App
Northwind drivers use the NorthRide app to meet customer pickup requests. The app uses a GPS transponder
in each Northwind vehicle and Bing Maps APIs to monitor the location of each vehicle in the fleet in real time.
NorthRide allows Northwind dispatchers to optimize their driver coverage throughout the city.
When new customers call, the dispatcher enters their pickup locations into NorthRide. NorthRide identifies the
closest available driver. The dispatcher then contacts the driver with the pick-up details. This process usually
results in a pick-up time that is far faster than the industry average.
Drivers use NorthRide to track the number of miles they drive and the number of customers they transport.
Drivers also track their progress towards their established goals, which are measured by using key
performance indicators (KPIs).
NorthRide App 2.0
Northwind Electric Cars is growing quickly. New callers often wait for their calls to be answered because the
dispatchers are contacting their drivers to arrange pickups for other customers.
To support the growth of the business, Northwind’s development team completes an overhaul of the NorthRide
system that it has named NorthRide 2.0. When a dispatcher enters a customer’s pickup location, the address
and driving directions are automatically sent to the driver who is closest to the customer’s pickup location.
Drivers indicate their availability on the NorthRide mobile app and can view progress towards their KPI’s in real
time. Drivers can also record customer ratings and feedback for each pickup.
Business Requirements
Apps
NorthRideFinder App
Northwind Electric Cars needs a customer-facing website and mobile app that allows customers to schedule
pickups. Customers should also be able to create profiles that will help ensure the customer gets a ride faster
by storing customer information.
Predictor App
Northwind Electric Cars needs a new solution named Predictor. Predictor is an employee-facing mobile app.
The app predicts periods of high usage and popular pickup locations and provides various ways to view this
predictive data. Northwind uses this information to better distribute its drivers. Northwind wants to use the latest
Azure technology to create this solution.
Other Requirements
On-premises data must be constantly backed up.
Mobile data must be protected from loss, even if connectivity with the backend is lost.Dispatch offices need to have seamless access to both their primary data center and the applications and
services that are hosted in the Azure cloud.
Connectivity needs to be redundant to on-premises and cloud services, while providing a way for each
dispatch office to continue to operate even if one or all of the connection options fail.
The management team requires that operational data is accessible 24/7 from any office location.
Technical Requirements
Apps and Website
NorthRide / NorthRideFinder Apps:
The solution must support on-premises and Azure data storage.
The solution must scale as necessary based on the current number of concurrent users.
Customer pickup requests from NorthRideFinder must be asynchronous.
The customer pickup request system will be high in volume, and each request will have a short life span.
Data for NorthRideFinder must be protected during a loss of connectivity.
NorthRide users must authenticate to the company’s Azure Active Directory.
Northwind Public Website
The customer website must use a WebJob to process profile images into thumbnails
The customer website must be developed with lowest cost and difficulty in mind.
The customer website must automatically scale to minimize response times for customers.
Other Requirements
Data Storage:
The data storage must interface with an on-premises Microsoft SQL backend database.
A disaster recovery system needs to be in place for large amounts of data that will backup to Azure.
Backups must be fully automated and managed the Azure Management Portal.
The recovery system for company data must use a hybrid solution to back up both the on-premises
Microsoft SQL backend and any Azure storage.
Predictive Routing:
An Azure solution must be used for prediction systems.
Predictive analytics must be published as a web service and accessible by using the REST API.
Security:
The NorthRide app must use an additional level of authentication other than the employee’s password.
Access must be secured in NorthRide without opening a firewall port.
Company policy prohibits inbound connections from internet callers to the on-premises network.
Customer usernames in NorthRideFinder cannot exceed 10 characters.
Customer data in NorthRideFinder can be received only by the user ID that is associated with the data.
###EndCaseStudy###
You need to configure the Northwind website.
Which two solutions should you use? Each correct answer presents part of the solution.
What should you include in the recommendation?
###BeginCaseStudy###
Testlet 1
Background
Overview
Northwind Electric Cars is the premier provider of private, low-cost transportation in Denver. Northwind drivers
are company employees who work together as a team. The founding partners believe that by hiring their drivers
as employees, their drivers focus on providing a great customer experience. Northwind Electric Cars has a
reputation for offering fast, reliable, and friendly service, due largely to their extensive network of drivers and
their proprietary dispatching software named NorthRide.
Northwind Electric Cars drivers depend on frequent, automatic updates for the NorthRide mobile app. The
Northwind management team is concerned about unplanned system downtime and slow connection speeds
caused by high usage. Additionally, Northwind’s in-house data storage solution is unsustainable because of the
new influx of customer data that is retained. Data backups are made periodically on DVDs and stored onpremises at corporate headquarters.
Apps
NorthRide App
Northwind drivers use the NorthRide app to meet customer pickup requests. The app uses a GPS transponder
in each Northwind vehicle and Bing Maps APIs to monitor the location of each vehicle in the fleet in real time.
NorthRide allows Northwind dispatchers to optimize their driver coverage throughout the city.
When new customers call, the dispatcher enters their pickup locations into NorthRide. NorthRide identifies the
closest available driver. The dispatcher then contacts the driver with the pick-up details. This process usually
results in a pick-up time that is far faster than the industry average.
Drivers use NorthRide to track the number of miles they drive and the number of customers they transport.
Drivers also track their progress towards their established goals, which are measured by using key
performance indicators (KPIs).
NorthRide App 2.0
Northwind Electric Cars is growing quickly. New callers often wait for their calls to be answered because the
dispatchers are contacting their drivers to arrange pickups for other customers.
To support the growth of the business, Northwind’s development team completes an overhaul of the NorthRide
system that it has named NorthRide 2.0. When a dispatcher enters a customer’s pickup location, the address
and driving directions are automatically sent to the driver who is closest to the customer’s pickup location.
Drivers indicate their availability on the NorthRide mobile app and can view progress towards their KPI’s in real
time. Drivers can also record customer ratings and feedback for each pickup.
Business Requirements
Apps
NorthRideFinder App
Northwind Electric Cars needs a customer-facing website and mobile app that allows customers to schedule
pickups. Customers should also be able to create profiles that will help ensure the customer gets a ride faster
by storing customer information.
Predictor App
Northwind Electric Cars needs a new solution named Predictor. Predictor is an employee-facing mobile app.
The app predicts periods of high usage and popular pickup locations and provides various ways to view this
predictive data. Northwind uses this information to better distribute its drivers. Northwind wants to use the latest
Azure technology to create this solution.
Other Requirements
On-premises data must be constantly backed up.
Mobile data must be protected from loss, even if connectivity with the backend is lost.Dispatch offices need to have seamless access to both their primary data center and the applications and
services that are hosted in the Azure cloud.
Connectivity needs to be redundant to on-premises and cloud services, while providing a way for each
dispatch office to continue to operate even if one or all of the connection options fail.
The management team requires that operational data is accessible 24/7 from any office location.
Technical Requirements
Apps and Website
NorthRide / NorthRideFinder Apps:
The solution must support on-premises and Azure data storage.
The solution must scale as necessary based on the current number of concurrent users.
Customer pickup requests from NorthRideFinder must be asynchronous.
The customer pickup request system will be high in volume, and each request will have a short life span.
Data for NorthRideFinder must be protected during a loss of connectivity.
NorthRide users must authenticate to the company’s Azure Active Directory.
Northwind Public Website
The customer website must use a WebJob to process profile images into thumbnails
The customer website must be developed with lowest cost and difficulty in mind.
The customer website must automatically scale to minimize response times for customers.
Other Requirements
Data Storage:
The data storage must interface with an on-premises Microsoft SQL backend database.
A disaster recovery system needs to be in place for large amounts of data that will backup to Azure.
Backups must be fully automated and managed the Azure Management Portal.
The recovery system for company data must use a hybrid solution to back up both the on-premises
Microsoft SQL backend and any Azure storage.
Predictive Routing:
An Azure solution must be used for prediction systems.
Predictive analytics must be published as a web service and accessible by using the REST API.
Security:
The NorthRide app must use an additional level of authentication other than the employee’s password.
Access must be secured in NorthRide without opening a firewall port.
Company policy prohibits inbound connections from internet callers to the on-premises network.
Customer usernames in NorthRideFinder cannot exceed 10 characters.
Customer data in NorthRideFinder can be received only by the user ID that is associated with the data.
###EndCaseStudy###
You need to recommend a solution that meets the requirements for data storage for the NorthRide app.
What should you include in the recommendation?
Which three actions should you perform in sequence?
###BeginCaseStudy###
Testlet 1
Background
Overview
Northwind Electric Cars is the premier provider of private, low-cost transportation in Denver. Northwind drivers
are company employees who work together as a team. The founding partners believe that by hiring their drivers
as employees, their drivers focus on providing a great customer experience. Northwind Electric Cars has a
reputation for offering fast, reliable, and friendly service, due largely to their extensive network of drivers and
their proprietary dispatching software named NorthRide.
Northwind Electric Cars drivers depend on frequent, automatic updates for the NorthRide mobile app. The
Northwind management team is concerned about unplanned system downtime and slow connection speeds
caused by high usage. Additionally, Northwind’s in-house data storage solution is unsustainable because of the
new influx of customer data that is retained. Data backups are made periodically on DVDs and stored onpremises at corporate headquarters.
Apps
NorthRide App
Northwind drivers use the NorthRide app to meet customer pickup requests. The app uses a GPS transponder
in each Northwind vehicle and Bing Maps APIs to monitor the location of each vehicle in the fleet in real time.
NorthRide allows Northwind dispatchers to optimize their driver coverage throughout the city.
When new customers call, the dispatcher enters their pickup locations into NorthRide. NorthRide identifies the
closest available driver. The dispatcher then contacts the driver with the pick-up details. This process usually
results in a pick-up time that is far faster than the industry average.
Drivers use NorthRide to track the number of miles they drive and the number of customers they transport.
Drivers also track their progress towards their established goals, which are measured by using key
performance indicators (KPIs).
NorthRide App 2.0
Northwind Electric Cars is growing quickly. New callers often wait for their calls to be answered because the
dispatchers are contacting their drivers to arrange pickups for other customers.
To support the growth of the business, Northwind’s development team completes an overhaul of the NorthRide
system that it has named NorthRide 2.0. When a dispatcher enters a customer’s pickup location, the address
and driving directions are automatically sent to the driver who is closest to the customer’s pickup location.
Drivers indicate their availability on the NorthRide mobile app and can view progress towards their KPI’s in real
time. Drivers can also record customer ratings and feedback for each pickup.
Business Requirements
Apps
NorthRideFinder App
Northwind Electric Cars needs a customer-facing website and mobile app that allows customers to schedule
pickups. Customers should also be able to create profiles that will help ensure the customer gets a ride faster
by storing customer information.
Predictor App
Northwind Electric Cars needs a new solution named Predictor. Predictor is an employee-facing mobile app.
The app predicts periods of high usage and popular pickup locations and provides various ways to view this
predictive data. Northwind uses this information to better distribute its drivers. Northwind wants to use the latest
Azure technology to create this solution.
Other Requirements
On-premises data must be constantly backed up.
Mobile data must be protected from loss, even if connectivity with the backend is lost.Dispatch offices need to have seamless access to both their primary data center and the applications and
services that are hosted in the Azure cloud.
Connectivity needs to be redundant to on-premises and cloud services, while providing a way for each
dispatch office to continue to operate even if one or all of the connection options fail.
The management team requires that operational data is accessible 24/7 from any office location.
Technical Requirements
Apps and Website
NorthRide / NorthRideFinder Apps:
The solution must support on-premises and Azure data storage.
The solution must scale as necessary based on the current number of concurrent users.
Customer pickup requests from NorthRideFinder must be asynchronous.
The customer pickup request system will be high in volume, and each request will have a short life span.
Data for NorthRideFinder must be protected during a loss of connectivity.
NorthRide users must authenticate to the company’s Azure Active Directory.
Northwind Public Website
The customer website must use a WebJob to process profile images into thumbnails
The customer website must be developed with lowest cost and difficulty in mind.
The customer website must automatically scale to minimize response times for customers.
Other Requirements
Data Storage:
The data storage must interface with an on-premises Microsoft SQL backend database.
A disaster recovery system needs to be in place for large amounts of data that will backup to Azure.
Backups must be fully automated and managed the Azure Management Portal.
The recovery system for company data must use a hybrid solution to back up both the on-premises
Microsoft SQL backend and any Azure storage.
Predictive Routing:
An Azure solution must be used for prediction systems.
Predictive analytics must be published as a web service and accessible by using the REST API.
Security:
The NorthRide app must use an additional level of authentication other than the employee’s password.
Access must be secured in NorthRide without opening a firewall port.
Company policy prohibits inbound connections from internet callers to the on-premises network.
Customer usernames in NorthRideFinder cannot exceed 10 characters.
Customer data in NorthRideFinder can be received only by the user ID that is associated with the data.
###EndCaseStudy###
DRAG DROP
You need to design the notification service for the customer-facing mobile app.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of
actions to the answer area and arrange them in the correct order.
Select and Place:
