###BeginCaseStudy###
Case Study: 4
Lucerne Publishing
Background
Overview
Lucerne Publishing creates, stores, and delivers online media for advertising companies. This
media is streamed to computers by using the web, and to mobile devices around the world by
using native applications. The company currently supports the iOS, Android, and Windows
Phone 8.1 platform.
Lucerne Publishing uses proprietary software to manage its media workflow. This software
has reached the end of its lifecycle. The company plans to move its media workflows to the
cloud. Lucerne Publishing provides access to its customers, who are third-party companies,
so that they can download, upload, search, and index media that is stored on Lucerne
Publishing servers.
Apps and Applications
Lucerne Publishing develops the applications that customers use to deliver media. The
company currently provides the following media delivery applications:
• Lucerne Media W – a web application that delivers media by using any browser
• Lucerne Media M – a mobile app that delivers media by using Windows Phone 8.1
• Lucerne Media A – a mobile app that delivers media by using an iOS device
• Lucerne Media N – a mobile app that delivers media by using an Android device
• Lucerne Media D – a desktop client application that customer’s install on their local
computer
Business Requirements
Lucerne Publishing’s customers and their consumers have the following requirements:
• Access to media must be time-constricted once media is delivered to a consumer.
• The time required to download media to mobile devices must be minimized.• Customers must have 24-hour access to media downloads regardless of their location
or time zone.
• Lucerne Publishing must be able to monitor the performance and usage of its
customer-facing app.
Lucerne Publishing wants to make its asset catalog searchable without requiring a database
redesign.
• Customers must be able to access all data by using a web application. They must also
be able to access data by using a mobile app that is provided by Lucerne Publishing.
• Customers must be able to search for media assets by key words and media type.
• Lucerne Publishing wants to move the asset catalog database to the cloud without
formatting the source data.
Other Requirements
Development
Code and current development documents must be backed up at all times. All solutions must
be automatically built and deployed to Azure when code is checked in to source control.
Network Optimization
Lucerne Publishing has a .NET web application that runs on Azure. The web application
analyzes storage and the distribution of its media assets. It needs to monitor the utilization of
the web application. Ultimately, Lucerne Publishing hopes to cut its costs by reducing data
replication without sacrificing its quality of service to its customers. The solution has the
following requirements:
• Optimize the storage location and amount of duplication of media.
• Vary several parameters including the number of data nodes and the distance from
node to customers.
• Minimize network bandwidth.
• Lucerne Publishing wants be notified of exceptions in the web application.
Technical Requirements
Data Mining
Lucerne Publishing constantly mines its data to identify customer patterns. The company
plans to replace the existing on-premises cluster with a cloud-based solution. Lucerne
Publishing has the following requirements:
Virtual machines:
• The data mining solution must support the use of hundreds to thousands of processing
cores.
• Minimize the number of virtual machines by using more powerful virtual machines.
Each virtual machine must always have eight or more processor cores available.
• Allow the number of processor cores dedicated to an analysis to grow and shrink
automatically based on the demand of the analysis.
• Virtual machines must use remote memory direct access to improve performance.
Task scheduling:
The solution must automatically schedule jobs. The scheduler must distribute the jobs based
on the demand and available resources.
Data analysis results:
The solution must provide a web service that allows applications to access the results of
analyses.
Other RequirementsFeature Support
• Ad copy data must be searchable in full text.
• Ad copy data must indexed to optimize search speed.
• Media metadata must be stored in Azure Table storage.
• Media files must be stored in Azure BLOB storage.
• The customer-facing website must have access to all ad copy and media.
• The customer-facing website must automatically scale and replicate to locations
around the world.
• Media and data must be replicated around the world to decrease the latency of data
transfers.
• Media uploads must have fast data transfer rates (low latency) without the need to
upload the data offline.
Security
• Customer access must be managed by using Active Directory.
• Media files must be encrypted by using the PlayReady encryption method.
• Customers must be able to upload media quickly and securely over a private
connection with no opportunity for internet snooping.

###EndCaseStudy###

HOTSPOT
You need to recommend strategies for storing data.
Which services should you recommend? To answer, select the appropriate storage technology for
each data type in the answer area.

###BeginCaseStudy###
Case Study: 4
Lucerne Publishing
Background
Overview
Lucerne Publishing creates, stores, and delivers online media for advertising companies. This
media is streamed to computers by using the web, and to mobile devices around the world by
using native applications. The company currently supports the iOS, Android, and Windows
Phone 8.1 platform.
Lucerne Publishing uses proprietary software to manage its media workflow. This software
has reached the end of its lifecycle. The company plans to move its media workflows to the
cloud. Lucerne Publishing provides access to its customers, who are third-party companies,
so that they can download, upload, search, and index media that is stored on Lucerne
Publishing servers.
Apps and Applications
Lucerne Publishing develops the applications that customers use to deliver media. The
company currently provides the following media delivery applications:
• Lucerne Media W – a web application that delivers media by using any browser
• Lucerne Media M – a mobile app that delivers media by using Windows Phone 8.1
• Lucerne Media A – a mobile app that delivers media by using an iOS device
• Lucerne Media N – a mobile app that delivers media by using an Android device
• Lucerne Media D – a desktop client application that customer’s install on their local
computer
Business Requirements
Lucerne Publishing’s customers and their consumers have the following requirements:
• Access to media must be time-constricted once media is delivered to a consumer.
• The time required to download media to mobile devices must be minimized.• Customers must have 24-hour access to media downloads regardless of their location
or time zone.
• Lucerne Publishing must be able to monitor the performance and usage of its
customer-facing app.
Lucerne Publishing wants to make its asset catalog searchable without requiring a database
redesign.
• Customers must be able to access all data by using a web application. They must also
be able to access data by using a mobile app that is provided by Lucerne Publishing.
• Customers must be able to search for media assets by key words and media type.
• Lucerne Publishing wants to move the asset catalog database to the cloud without
formatting the source data.
Other Requirements
Development
Code and current development documents must be backed up at all times. All solutions must
be automatically built and deployed to Azure when code is checked in to source control.
Network Optimization
Lucerne Publishing has a .NET web application that runs on Azure. The web application
analyzes storage and the distribution of its media assets. It needs to monitor the utilization of
the web application. Ultimately, Lucerne Publishing hopes to cut its costs by reducing data
replication without sacrificing its quality of service to its customers. The solution has the
following requirements:
• Optimize the storage location and amount of duplication of media.
• Vary several parameters including the number of data nodes and the distance from
node to customers.
• Minimize network bandwidth.
• Lucerne Publishing wants be notified of exceptions in the web application.
Technical Requirements
Data Mining
Lucerne Publishing constantly mines its data to identify customer patterns. The company
plans to replace the existing on-premises cluster with a cloud-based solution. Lucerne
Publishing has the following requirements:
Virtual machines:
• The data mining solution must support the use of hundreds to thousands of processing
cores.
• Minimize the number of virtual machines by using more powerful virtual machines.
Each virtual machine must always have eight or more processor cores available.
• Allow the number of processor cores dedicated to an analysis to grow and shrink
automatically based on the demand of the analysis.
• Virtual machines must use remote memory direct access to improve performance.
Task scheduling:
The solution must automatically schedule jobs. The scheduler must distribute the jobs based
on the demand and available resources.
Data analysis results:
The solution must provide a web service that allows applications to access the results of
analyses.
Other RequirementsFeature Support
• Ad copy data must be searchable in full text.
• Ad copy data must indexed to optimize search speed.
• Media metadata must be stored in Azure Table storage.
• Media files must be stored in Azure BLOB storage.
• The customer-facing website must have access to all ad copy and media.
• The customer-facing website must automatically scale and replicate to locations
around the world.
• Media and data must be replicated around the world to decrease the latency of data
transfers.
• Media uploads must have fast data transfer rates (low latency) without the need to
upload the data offline.
Security
• Customer access must be managed by using Active Directory.
• Media files must be encrypted by using the PlayReady encryption method.
• Customers must be able to upload media quickly and securely over a private
connection with no opportunity for internet snooping.

###EndCaseStudy###

You need to configure the deployment of the storage analysis application.
What should you do?

###BeginCaseStudy###
Case Study: 4
Lucerne Publishing
Background
Overview
Lucerne Publishing creates, stores, and delivers online media for advertising companies. This
media is streamed to computers by using the web, and to mobile devices around the world by
using native applications. The company currently supports the iOS, Android, and Windows
Phone 8.1 platform.
Lucerne Publishing uses proprietary software to manage its media workflow. This software
has reached the end of its lifecycle. The company plans to move its media workflows to the
cloud. Lucerne Publishing provides access to its customers, who are third-party companies,
so that they can download, upload, search, and index media that is stored on Lucerne
Publishing servers.
Apps and Applications
Lucerne Publishing develops the applications that customers use to deliver media. The
company currently provides the following media delivery applications:
• Lucerne Media W – a web application that delivers media by using any browser
• Lucerne Media M – a mobile app that delivers media by using Windows Phone 8.1
• Lucerne Media A – a mobile app that delivers media by using an iOS device
• Lucerne Media N – a mobile app that delivers media by using an Android device
• Lucerne Media D – a desktop client application that customer’s install on their local
computer
Business Requirements
Lucerne Publishing’s customers and their consumers have the following requirements:
• Access to media must be time-constricted once media is delivered to a consumer.
• The time required to download media to mobile devices must be minimized.• Customers must have 24-hour access to media downloads regardless of their location
or time zone.
• Lucerne Publishing must be able to monitor the performance and usage of its
customer-facing app.
Lucerne Publishing wants to make its asset catalog searchable without requiring a database
redesign.
• Customers must be able to access all data by using a web application. They must also
be able to access data by using a mobile app that is provided by Lucerne Publishing.
• Customers must be able to search for media assets by key words and media type.
• Lucerne Publishing wants to move the asset catalog database to the cloud without
formatting the source data.
Other Requirements
Development
Code and current development documents must be backed up at all times. All solutions must
be automatically built and deployed to Azure when code is checked in to source control.
Network Optimization
Lucerne Publishing has a .NET web application that runs on Azure. The web application
analyzes storage and the distribution of its media assets. It needs to monitor the utilization of
the web application. Ultimately, Lucerne Publishing hopes to cut its costs by reducing data
replication without sacrificing its quality of service to its customers. The solution has the
following requirements:
• Optimize the storage location and amount of duplication of media.
• Vary several parameters including the number of data nodes and the distance from
node to customers.
• Minimize network bandwidth.
• Lucerne Publishing wants be notified of exceptions in the web application.
Technical Requirements
Data Mining
Lucerne Publishing constantly mines its data to identify customer patterns. The company
plans to replace the existing on-premises cluster with a cloud-based solution. Lucerne
Publishing has the following requirements:
Virtual machines:
• The data mining solution must support the use of hundreds to thousands of processing
cores.
• Minimize the number of virtual machines by using more powerful virtual machines.
Each virtual machine must always have eight or more processor cores available.
• Allow the number of processor cores dedicated to an analysis to grow and shrink
automatically based on the demand of the analysis.
• Virtual machines must use remote memory direct access to improve performance.
Task scheduling:
The solution must automatically schedule jobs. The scheduler must distribute the jobs based
on the demand and available resources.
Data analysis results:
The solution must provide a web service that allows applications to access the results of
analyses.
Other RequirementsFeature Support
• Ad copy data must be searchable in full text.
• Ad copy data must indexed to optimize search speed.
• Media metadata must be stored in Azure Table storage.
• Media files must be stored in Azure BLOB storage.
• The customer-facing website must have access to all ad copy and media.
• The customer-facing website must automatically scale and replicate to locations
around the world.
• Media and data must be replicated around the world to decrease the latency of data
transfers.
• Media uploads must have fast data transfer rates (low latency) without the need to
upload the data offline.
Security
• Customer access must be managed by using Active Directory.
• Media files must be encrypted by using the PlayReady encryption method.
• Customers must be able to upload media quickly and securely over a private
connection with no opportunity for internet snooping.

###EndCaseStudy###

You need to recommend an appropriate solution for the data mining requirements.
Which solution should you recommend?

###BeginCaseStudy###
Case Study: 4
Lucerne Publishing
Background
Overview
Lucerne Publishing creates, stores, and delivers online media for advertising companies. This
media is streamed to computers by using the web, and to mobile devices around the world by
using native applications. The company currently supports the iOS, Android, and Windows
Phone 8.1 platform.
Lucerne Publishing uses proprietary software to manage its media workflow. This software
has reached the end of its lifecycle. The company plans to move its media workflows to the
cloud. Lucerne Publishing provides access to its customers, who are third-party companies,
so that they can download, upload, search, and index media that is stored on Lucerne
Publishing servers.
Apps and Applications
Lucerne Publishing develops the applications that customers use to deliver media. The
company currently provides the following media delivery applications:
• Lucerne Media W – a web application that delivers media by using any browser
• Lucerne Media M – a mobile app that delivers media by using Windows Phone 8.1
• Lucerne Media A – a mobile app that delivers media by using an iOS device
• Lucerne Media N – a mobile app that delivers media by using an Android device
• Lucerne Media D – a desktop client application that customer’s install on their local
computer
Business Requirements
Lucerne Publishing’s customers and their consumers have the following requirements:
• Access to media must be time-constricted once media is delivered to a consumer.
• The time required to download media to mobile devices must be minimized.• Customers must have 24-hour access to media downloads regardless of their location
or time zone.
• Lucerne Publishing must be able to monitor the performance and usage of its
customer-facing app.
Lucerne Publishing wants to make its asset catalog searchable without requiring a database
redesign.
• Customers must be able to access all data by using a web application. They must also
be able to access data by using a mobile app that is provided by Lucerne Publishing.
• Customers must be able to search for media assets by key words and media type.
• Lucerne Publishing wants to move the asset catalog database to the cloud without
formatting the source data.
Other Requirements
Development
Code and current development documents must be backed up at all times. All solutions must
be automatically built and deployed to Azure when code is checked in to source control.
Network Optimization
Lucerne Publishing has a .NET web application that runs on Azure. The web application
analyzes storage and the distribution of its media assets. It needs to monitor the utilization of
the web application. Ultimately, Lucerne Publishing hopes to cut its costs by reducing data
replication without sacrificing its quality of service to its customers. The solution has the
following requirements:
• Optimize the storage location and amount of duplication of media.
• Vary several parameters including the number of data nodes and the distance from
node to customers.
• Minimize network bandwidth.
• Lucerne Publishing wants be notified of exceptions in the web application.
Technical Requirements
Data Mining
Lucerne Publishing constantly mines its data to identify customer patterns. The company
plans to replace the existing on-premises cluster with a cloud-based solution. Lucerne
Publishing has the following requirements:
Virtual machines:
• The data mining solution must support the use of hundreds to thousands of processing
cores.
• Minimize the number of virtual machines by using more powerful virtual machines.
Each virtual machine must always have eight or more processor cores available.
• Allow the number of processor cores dedicated to an analysis to grow and shrink
automatically based on the demand of the analysis.
• Virtual machines must use remote memory direct access to improve performance.
Task scheduling:
The solution must automatically schedule jobs. The scheduler must distribute the jobs based
on the demand and available resources.
Data analysis results:
The solution must provide a web service that allows applications to access the results of
analyses.
Other RequirementsFeature Support
• Ad copy data must be searchable in full text.
• Ad copy data must indexed to optimize search speed.
• Media metadata must be stored in Azure Table storage.
• Media files must be stored in Azure BLOB storage.
• The customer-facing website must have access to all ad copy and media.
• The customer-facing website must automatically scale and replicate to locations
around the world.
• Media and data must be replicated around the world to decrease the latency of data
transfers.
• Media uploads must have fast data transfer rates (low latency) without the need to
upload the data offline.
Security
• Customer access must be managed by using Active Directory.
• Media files must be encrypted by using the PlayReady encryption method.
• Customers must be able to upload media quickly and securely over a private
connection with no opportunity for internet snooping.

###EndCaseStudy###

You need to ensure that the website scales.
What should you do?

###BeginCaseStudy###
Case Study: 5
Northwind traders
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 inhouse 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 on-premises 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.0Northwind 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 employeefacing 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 onpremises 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 design the authentication solution for the NorthRide app. Which solution should you
use?

###BeginCaseStudy###
Case Study: 5
Northwind traders
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 inhouse 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 on-premises 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.0Northwind 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 employeefacing 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 onpremises 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 provide a data access solution for the NorthRide app.
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.

###BeginCaseStudy###
Case Study: 5
Northwind traders
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 inhouse 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 on-premises 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.0Northwind 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 employeefacing 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 onpremises 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 the appropriate technology to provide the predictive analytics for
passenger pickup.
What should you do?

###BeginCaseStudy###
Case Study: 5
Northwind traders
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 inhouse 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 on-premises 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.0Northwind 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 employeefacing 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 onpremises 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.

###BeginCaseStudy###
Case Study: 5
Northwind traders
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 inhouse 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 on-premises 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.0Northwind 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 employeefacing 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 onpremises 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 technology for processing customer pickup requests.
Which technology should you recommend?

###BeginCaseStudy###
Case Study: 5
Northwind traders
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 inhouse 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 on-premises 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.0Northwind 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 employeefacing 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 onpremises 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?