Background:
You are a developer for ProseWare Inc., a software-as-a-service (SaaS) company that provides a comment
system that websites use to allow for end users to post comments associated with a webpage or topic on a
customer’s website.
Business requirements
Moderation:
The moderation of comments is a feature of the software, and usually involves the editing of a comment.
Only users who have accounts in a group in Azure Active Directory (Azure AD) have the ability moderate.
External users can also become moderators, but only by explicit invitation.
Any moderation action must include the name of the moderator.
Comment navigation:
Each comment is identified by a unique string consisting of a random string of characters.Within the body of a comment, internal links to other comment threads can be specified using the link format: “/
<parent comment id> / <child comment id>”
Comment search:
Comments can be searched using Azure Search. Searches must do the following:
Searching for email addresses must match email addresses in comments.
Searching must work for the client’s language.
Internal links to other comments using the link format should be searched.
Content screening:
Comment content is screened for inappropriate language, length, and topic using content analysis. Content
must be screened, but can appear prior to be screened.
Mobile App:
The moderation functionality can be accessed using a Universal Windows Platform (UWP) app named
ProsewareApp. The app includes functionality that notifies moderators when changes are made to a comment
they modified.
Export:
Customers can perform an export of all comments to a customer supplied Microsoft OneDrive folder on
demand. The export functionality is implemented as an Azure Logic App, and it must be able to be triggered by
the customer from their local network.
Interaction agents:
Interaction agents are parts of the system that interact with comment threads. The main purpose is to modify a
comment’s body based on the contents of the comment. For example, one of the agents is WikiAgent, which
adds links to Wikipedia articles when it sees text in the comment body that exactly matches a Wikipedia article
title. Interaction Agents are implemented in Service Fabric.
Interaction agents must meet the following requirements:
Only successfully process each comment once
Any errors encountered during the processing of a comment should be retried
Must run on systems that allow for custom applications to be installed
Must run in a VNet or private network space
Must be run on a system that can scale up and down based on demand
A single user’s usage of Interaction Agents must not impact other users’ usage of Interaction Agents
Technical requirements
Authentication:
ProseWare Inc. allows for user authentication through Azure AD and Twitter.
Storage:
The application runs as a Web App on Azure. Comments are stored in an Azure DocumentDB database
named “Proseware”.
Performance:
The product includes a service level agreement (SLA) for individual method performance. All data retrieval
methods must return within 100ms 99% of the time.
API:
The ProseWare Inc. API is made available to public callers using an Azure API App. Azure AD and Twitter are
the Authentication Providers.
Application structure
CommentController.cs:

cleaner.csx:

ICommentAgent.cs:

WikiAgent.cs:

Comment.cs:

DataStore.cs:

MainPage.xaml.cs:

Note: This question is part of a series of questions that present the same scenario. Each question in the series
contains a unique solution that might meet the stated goals. Some question sets might have more than one
correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will
not appear in the review screen.
You need to implement the infrastructure for the Interaction Agents.
Solution: Create a Service Fabric cluster with Bronze durability and reliability tiers.
Does the solution meet the goal?

Background:
You are a developer for ProseWare Inc., a software-as-a-service (SaaS) company that provides a comment
system that websites use to allow for end users to post comments associated with a webpage or topic on a
customer’s website.
Business requirements
Moderation:
The moderation of comments is a feature of the software, and usually involves the editing of a comment.
Only users who have accounts in a group in Azure Active Directory (Azure AD) have the ability moderate.
External users can also become moderators, but only by explicit invitation.
Any moderation action must include the name of the moderator.
Comment navigation:Each comment is identified by a unique string consisting of a random string of characters.
Within the body of a comment, internal links to other comment threads can be specified using the link format: “/
<parent comment id> / <child comment id>”
Comment search:
Comments can be searched using Azure Search. Searches must do the following:
Searching for email addresses must match email addresses in comments.
Searching must work for the client’s language.
Internal links to other comments using the link format should be searched.
Content screening:
Comment content is screened for inappropriate language, length, and topic using content analysis. Content
must be screened, but can appear prior to be screened.
Mobile App:
The moderation functionality can be accessed using a Universal Windows Platform (UWP) app named
ProsewareApp. The app includes functionality that notifies moderators when changes are made to a comment
they modified.
Export:
Customers can perform an export of all comments to a customer supplied Microsoft OneDrive folder on
demand. The export functionality is implemented as an Azure Logic App, and it must be able to be triggered by
the customer from their local network.
Interaction agents:
Interaction agents are parts of the system that interact with comment threads. The main purpose is to modify a
comment’s body based on the contents of the comment. For example, one of the agents is WikiAgent, which
adds links to Wikipedia articles when it sees text in the comment body that exactly matches a Wikipedia article
title. Interaction Agents are implemented in Service Fabric.
Interaction agents must meet the following requirements:
Only successfully process each comment once
Any errors encountered during the processing of a comment should be retried
Must run on systems that allow for custom applications to be installed
Must run in a VNet or private network space
Must be run on a system that can scale up and down based on demand
A single user’s usage of Interaction Agents must not impact other users’ usage of Interaction Agents
Technical requirements
Authentication:
ProseWare Inc. allows for user authentication through Azure AD and Twitter.
Storage:
The application runs as a Web App on Azure. Comments are stored in an Azure DocumentDB database
named “Proseware”.
Performance:
The product includes a service level agreement (SLA) for individual method performance. All data retrieval
methods must return within 100ms 99% of the time.
API:
The ProseWare Inc. API is made available to public callers using an Azure API App. Azure AD and Twitter are
the Authentication Providers.
Application structure
CommentController.cs:

cleaner.csx:

ICommentAgent.cs:

WikiAgent.cs:

Comment.cs:

DataStore.cs:

MainPage.xaml.cs:

Note: This question is part of a series of questions that present the same scenario. Each question in the series
contains a unique solution that might meet the stated goals. Some question sets might have more than one
correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will
not appear in the review screen.
You need to implement the infrastructure for the Interaction Agents.
Solution: Create an Azure virtual machine (VM) scale set and use Azure Desired State Configuration (DSC)
extension handler to install Service Fabric runtime.
Does the solution meet the goal?

Background:
You are a developer for ProseWare Inc., a software-as-a-service (SaaS) company that provides a comment
system that websites use to allow for end users to post comments associated with a webpage or topic on a
customer’s website.
Business requirements
Moderation:
The moderation of comments is a feature of the software, and usually involves the editing of a comment.
Only users who have accounts in a group in Azure Active Directory (Azure AD) have the ability moderate.
External users can also become moderators, but only by explicit invitation.
Any moderation action must include the name of the moderator.
Comment navigation:
Each comment is identified by a unique string consisting of a random string of characters.Within the body of a comment, internal links to other comment threads can be specified using the link format: “/
<parent comment id> / <child comment id>”
Comment search:
Comments can be searched using Azure Search. Searches must do the following:
Searching for email addresses must match email addresses in comments.
Searching must work for the client’s language.
Internal links to other comments using the link format should be searched.
Content screening:
Comment content is screened for inappropriate language, length, and topic using content analysis. Content
must be screened, but can appear prior to be screened.
Mobile App:
The moderation functionality can be accessed using a Universal Windows Platform (UWP) app named
ProsewareApp. The app includes functionality that notifies moderators when changes are made to a comment
they modified.
Export:
Customers can perform an export of all comments to a customer supplied Microsoft OneDrive folder on
demand. The export functionality is implemented as an Azure Logic App, and it must be able to be triggered by
the customer from their local network.
Interaction agents:
Interaction agents are parts of the system that interact with comment threads. The main purpose is to modify a
comment’s body based on the contents of the comment. For example, one of the agents is WikiAgent, which
adds links to Wikipedia articles when it sees text in the comment body that exactly matches a Wikipedia article
title. Interaction Agents are implemented in Service Fabric.
Interaction agents must meet the following requirements:
Only successfully process each comment once
Any errors encountered during the processing of a comment should be retried
Must run on systems that allow for custom applications to be installed
Must run in a VNet or private network space
Must be run on a system that can scale up and down based on demand
A single user’s usage of Interaction Agents must not impact other users’ usage of Interaction Agents
Technical requirements
Authentication:
ProseWare Inc. allows for user authentication through Azure AD and Twitter.
Storage:
The application runs as a Web App on Azure. Comments are stored in an Azure DocumentDB database
named “Proseware”.
Performance:
The product includes a service level agreement (SLA) for individual method performance. All data retrieval
methods must return within 100ms 99% of the time.
API:
The ProseWare Inc. API is made available to public callers using an Azure API App. Azure AD and Twitter are
the Authentication Providers.
Application structure
CommentController.cs:

cleaner.csx:

ICommentAgent.cs:

WikiAgent.cs:

Comment.cs:

DataStore.cs:

MainPage.xaml.cs:

Note: This question is part of a series of questions that present the same scenario. Each question in the series
contains a unique solution that might meet the stated goals. Some question sets might have more than one
correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will
not appear in the review screen.
You need to implement the infrastructure for the Interaction Agents.
Solution: Create a set of Azure virtual machines (VMs) using Azure Resource Manager (ARM) templates, and
use Chef to install the Service Fabric runtime.
Does the solution meet the goal?

Background:
You are a developer for ProseWare Inc., a software-as-a-service (SaaS) company that provides a comment
system that websites use to allow for end users to post comments associated with a webpage or topic on a
customer’s website.
Business requirements
Moderation:
The moderation of comments is a feature of the software, and usually involves the editing of a comment.
Only users who have accounts in a group in Azure Active Directory (Azure AD) have the ability moderate.
External users can also become moderators, but only by explicit invitation.
Any moderation action must include the name of the moderator.
Comment navigation:
Each comment is identified by a unique string consisting of a random string of characters.
Within the body of a comment, internal links to other comment threads can be specified using the link format: “/
<parent comment id> / <child comment id>”
Comment search:
Comments can be searched using Azure Search. Searches must do the following:
Searching for email addresses must match email addresses in comments.
Searching must work for the client’s language.
Internal links to other comments using the link format should be searched.Content screening:
Comment content is screened for inappropriate language, length, and topic using content analysis. Content
must be screened, but can appear prior to be screened.
Mobile App:
The moderation functionality can be accessed using a Universal Windows Platform (UWP) app named
ProsewareApp. The app includes functionality that notifies moderators when changes are made to a comment
they modified.
Export:
Customers can perform an export of all comments to a customer supplied Microsoft OneDrive folder on
demand. The export functionality is implemented as an Azure Logic App, and it must be able to be triggered by
the customer from their local network.
Interaction agents:
Interaction agents are parts of the system that interact with comment threads. The main purpose is to modify a
comment’s body based on the contents of the comment. For example, one of the agents is WikiAgent, which
adds links to Wikipedia articles when it sees text in the comment body that exactly matches a Wikipedia article
title. Interaction Agents are implemented in Service Fabric.
Interaction agents must meet the following requirements:
Only successfully process each comment once
Any errors encountered during the processing of a comment should be retried
Must run on systems that allow for custom applications to be installed
Must run in a VNet or private network space
Must be run on a system that can scale up and down based on demand
A single user’s usage of Interaction Agents must not impact other users’ usage of Interaction Agents
Technical requirements
Authentication:
ProseWare Inc. allows for user authentication through Azure AD and Twitter.
Storage:
The application runs as a Web App on Azure. Comments are stored in an Azure DocumentDB database
named “Proseware”.
Performance:
The product includes a service level agreement (SLA) for individual method performance. All data retrieval
methods must return within 100ms 99% of the time.
API:
The ProseWare Inc. API is made available to public callers using an Azure API App. Azure AD and Twitter are
the Authentication Providers.
Application structure
CommentController.cs:

cleaner.csx:

ICommentAgent.cs:

WikiAgent.cs:

Comment.cs:

DataStore.cs:

MainPage.xaml.cs:

Note: This question is part of a series of questions that present the same scenario. Each question in the series
contains a unique solution that might meet the stated goals. Some question sets might have more than one
correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will
not appear in the review screen.
You need to implement the infrastructure for the Interaction Agents.
Solution: Create an Azure Container Service cluster and create a container for running Service Fabric.
Does the solution meet the goal?

Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like
to complete each case. However, there may be additional case studies and sections on this exam. You must
manage your time to ensure that you are able to complete all questions included on this exam in the time
provided.
To answer the questions included in a case study, you will need to reference information that is provided in the
case study. Case studies might contain exhibits and other resources that provide more information about the
scenario that is described in the case study. Each question is independent of the other question on this case
study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to
make changes before you move to the next sections of the exam. After you begin a new section, you cannot
return to this section.
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore
the content of the case study before you answer the questions. Clicking these buttons displays information such
as business requirements, existing environment, and problem statements. If the case study has an All
Information tab, note that the information displayed is identical to the information displayed on the subsequent
tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
You are a developer for LitWare, Inc., a game development company. You are developing a backend service
for an online social gaming platform named GamerData. The game is built around point generators, which are
associated with physical landmarks. Players claim point generators which give them a set amount of points per
day.
Business Requirements
Mobile App
The game itself runs on various mobile devices and is developed by TailSpin Toys, a company that specializes
in mobile game development. The mobile app will periodically make calls to the GamerData service to find the
five closest point generators that are located less than the specified distance from the player’s current location.
If no point generators are found, the search distance increases until one is found.
The mobile app shows all the point generators owned by each player. The mobile app allows for each player to
search for claimed point generators by player name. This search does not require exact spelling of names. The
details for each claimed generator is shown in the app.
When a player claims a point generator, they should receive an email notification. An Azure Function named
EmailPlayer has been developed to email players with details about recently claimed point generators.
Sponsors
The platform allows business to sponsor point generators within a business location.
Reports
A report named Daily Sponsor Report must be generated each day at midnight. The report must contain a
section for each sponsor. Each sponsor section must contain two subsections.
The first subsection of the report contains the names of the point generators for that sponsor, ordered by the
last time the point generator was claimed. The second subsection contains the current owners for each of the
point generators for the sponsor. Generation of reports must not impact the GamerData service.
Technical RequirementsGamerData Service
All data for the GamerData service is stored in an Azure DocumentDB instance named GamerData. Business
and players interact with the service by using a REST API.
The REST API must:
Produce valid Swagger API specifications for non-obsolete actions.
Be optimized for loading specific point generators.
Follow REST best practices.
Include appropriate terms of service.
Costs for all Azure services must be minimized.
Build and Deployment
The GamerData service will be deployed to Azure in a private VNet.
Security
Sponsors have accounts in an Azure Active Directory (Azure AD) with business-to-consumer (B2C) enabled
named litwaregamerdata.onmicrosoft.com managed by Litware, Inc. for both GamerData and LitWare, Inc.
services.
Only Litware, Inc. developers and automated testing tools should be able to directly access the GamerData
service. All other use of the service must be through Azure API Management. A description of the security
practices used during development, available on Microsoft SharePoint, must be available to users of the API
under the terms of service.
Reporting
Azure Search will be used as the source for running reports. The properties of indexes in Azure Search must
match the names of the properties in DocumentDB.
Performance
The Azure DocumentDB must not be used for reporting purposes. All services must perform queries in the data
store when possible.
Application Structure
Startup.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointController.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointGenerator.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to decrease the amount of time it takes to query point generators by configuring API management
caching.
In the Azure portal, which value should you use for the Vary by Query string parameters setting?

HOTSPOT
Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like
to complete each case. However, there may be additional case studies and sections on this exam. You must
manage your time to ensure that you are able to complete all questions included on this exam in the time
provided.
To answer the questions included in a case study, you will need to reference information that is provided in the
case study. Case studies might contain exhibits and other resources that provide more information about the
scenario that is described in the case study. Each question is independent of the other question on this case
study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to
make changes before you move to the next sections of the exam. After you begin a new section, you cannot
return to this section.
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore
the content of the case study before you answer the questions. Clicking these buttons displays information such
as business requirements, existing environment, and problem statements. If the case study has an All
Information tab, note that the information displayed is identical to the information displayed on the subsequent
tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
You are a developer for LitWare, Inc., a game development company. You are developing a backend service
for an online social gaming platform named GamerData. The game is built around point generators, which are
associated with physical landmarks. Players claim point generators which give them a set amount of points per
day.Business Requirements
Mobile App
The game itself runs on various mobile devices and is developed by TailSpin Toys, a company that specializes
in mobile game development. The mobile app will periodically make calls to the GamerData service to find the
five closest point generators that are located less than the specified distance from the player’s current location.
If no point generators are found, the search distance increases until one is found.
The mobile app shows all the point generators owned by each player. The mobile app allows for each player to
search for claimed point generators by player name. This search does not require exact spelling of names. The
details for each claimed generator is shown in the app.
When a player claims a point generator, they should receive an email notification. An Azure Function named
EmailPlayer has been developed to email players with details about recently claimed point generators.
Sponsors
The platform allows business to sponsor point generators within a business location.
Reports
A report named Daily Sponsor Report must be generated each day at midnight. The report must contain a
section for each sponsor. Each sponsor section must contain two subsections.
The first subsection of the report contains the names of the point generators for that sponsor, ordered by the
last time the point generator was claimed. The second subsection contains the current owners for each of the
point generators for the sponsor. Generation of reports must not impact the GamerData service.
Technical Requirements
GamerData Service
All data for the GamerData service is stored in an Azure DocumentDB instance named GamerData. Business
and players interact with the service by using a REST API.
The REST API must:
Produce valid Swagger API specifications for non-obsolete actions.
Be optimized for loading specific point generators.
Follow REST best practices.
Include appropriate terms of service.
Costs for all Azure services must be minimized.
Build and Deployment
The GamerData service will be deployed to Azure in a private VNet.
Security
Sponsors have accounts in an Azure Active Directory (Azure AD) with business-to-consumer (B2C) enabled
named litwaregamerdata.onmicrosoft.com managed by Litware, Inc. for both GamerData and LitWare, Inc.
services.
Only Litware, Inc. developers and automated testing tools should be able to directly access the GamerData
service. All other use of the service must be through Azure API Management. A description of the security
practices used during development, available on Microsoft SharePoint, must be available to users of the API
under the terms of service.Reporting
Azure Search will be used as the source for running reports. The properties of indexes in Azure Search must
match the names of the properties in DocumentDB.
Performance
The Azure DocumentDB must not be used for reporting purposes. All services must perform queries in the data
store when possible.
Application Structure
Startup.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointController.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointGenerator.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to build a Swagger specification for creating the GamerData managed API.
What should you do? To answer, select the appropriate options in the answer area.
Hot Area:

Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like
to complete each case. However, there may be additional case studies and sections on this exam. You must
manage your time to ensure that you are able to complete all questions included on this exam in the time
provided.
To answer the questions included in a case study, you will need to reference information that is provided in the
case study. Case studies might contain exhibits and other resources that provide more information about the
scenario that is described in the case study. Each question is independent of the other question on this case
study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to
make changes before you move to the next sections of the exam. After you begin a new section, you cannot
return to this section.
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore
the content of the case study before you answer the questions. Clicking these buttons displays information such
as business requirements, existing environment, and problem statements. If the case study has an All
Information tab, note that the information displayed is identical to the information displayed on the subsequent
tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
You are a developer for LitWare, Inc., a game development company. You are developing a backend service
for an online social gaming platform named GamerData. The game is built around point generators, which are
associated with physical landmarks. Players claim point generators which give them a set amount of points per
day.Business Requirements
Mobile App
The game itself runs on various mobile devices and is developed by TailSpin Toys, a company that specializes
in mobile game development. The mobile app will periodically make calls to the GamerData service to find the
five closest point generators that are located less than the specified distance from the player’s current location.
If no point generators are found, the search distance increases until one is found.
The mobile app shows all the point generators owned by each player. The mobile app allows for each player to
search for claimed point generators by player name. This search does not require exact spelling of names. The
details for each claimed generator is shown in the app.
When a player claims a point generator, they should receive an email notification. An Azure Function named
EmailPlayer has been developed to email players with details about recently claimed point generators.
Sponsors
The platform allows business to sponsor point generators within a business location.
Reports
A report named Daily Sponsor Report must be generated each day at midnight. The report must contain a
section for each sponsor. Each sponsor section must contain two subsections.
The first subsection of the report contains the names of the point generators for that sponsor, ordered by the
last time the point generator was claimed. The second subsection contains the current owners for each of the
point generators for the sponsor. Generation of reports must not impact the GamerData service.
Technical Requirements
GamerData Service
All data for the GamerData service is stored in an Azure DocumentDB instance named GamerData. Business
and players interact with the service by using a REST API.
The REST API must:
Produce valid Swagger API specifications for non-obsolete actions.
Be optimized for loading specific point generators.
Follow REST best practices.
Include appropriate terms of service.
Costs for all Azure services must be minimized.
Build and Deployment
The GamerData service will be deployed to Azure in a private VNet.
Security
Sponsors have accounts in an Azure Active Directory (Azure AD) with business-to-consumer (B2C) enabled
named litwaregamerdata.onmicrosoft.com managed by Litware, Inc. for both GamerData and LitWare, Inc.
services.
Only Litware, Inc. developers and automated testing tools should be able to directly access the GamerData
service. All other use of the service must be through Azure API Management. A description of the security
practices used during development, available on Microsoft SharePoint, must be available to users of the API
under the terms of service.Reporting
Azure Search will be used as the source for running reports. The properties of indexes in Azure Search must
match the names of the properties in DocumentDB.
Performance
The Azure DocumentDB must not be used for reporting purposes. All services must perform queries in the data
store when possible.
Application Structure
Startup.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointController.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointGenerator.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to trigger the EmailPlayer Azure Function when a point generator is claimed.
What are two possible ways to achieve this goal? Each correct answer presents a complete solution.

DRAG DROP
Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like
to complete each case. However, there may be additional case studies and sections on this exam. You must
manage your time to ensure that you are able to complete all questions included on this exam in the time
provided.
To answer the questions included in a case study, you will need to reference information that is provided in the
case study. Case studies might contain exhibits and other resources that provide more information about the
scenario that is described in the case study. Each question is independent of the other question on this case
study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to
make changes before you move to the next sections of the exam. After you begin a new section, you cannot
return to this section.
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore
the content of the case study before you answer the questions. Clicking these buttons displays information such
as business requirements, existing environment, and problem statements. If the case study has an All
Information tab, note that the information displayed is identical to the information displayed on the subsequent
tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
You are a developer for LitWare, Inc., a game development company. You are developing a backend service
for an online social gaming platform named GamerData. The game is built around point generators, which are
associated with physical landmarks. Players claim point generators which give them a set amount of points per
day.Business Requirements
Mobile App
The game itself runs on various mobile devices and is developed by TailSpin Toys, a company that specializes
in mobile game development. The mobile app will periodically make calls to the GamerData service to find the
five closest point generators that are located less than the specified distance from the player’s current location.
If no point generators are found, the search distance increases until one is found.
The mobile app shows all the point generators owned by each player. The mobile app allows for each player to
search for claimed point generators by player name. This search does not require exact spelling of names. The
details for each claimed generator is shown in the app.
When a player claims a point generator, they should receive an email notification. An Azure Function named
EmailPlayer has been developed to email players with details about recently claimed point generators.
Sponsors
The platform allows business to sponsor point generators within a business location.
Reports
A report named Daily Sponsor Report must be generated each day at midnight. The report must contain a
section for each sponsor. Each sponsor section must contain two subsections.
The first subsection of the report contains the names of the point generators for that sponsor, ordered by the
last time the point generator was claimed. The second subsection contains the current owners for each of the
point generators for the sponsor. Generation of reports must not impact the GamerData service.
Technical Requirements
GamerData Service
All data for the GamerData service is stored in an Azure DocumentDB instance named GamerData. Business
and players interact with the service by using a REST API.
The REST API must:
Produce valid Swagger API specifications for non-obsolete actions.
Be optimized for loading specific point generators.
Follow REST best practices.
Include appropriate terms of service.
Costs for all Azure services must be minimized.
Build and Deployment
The GamerData service will be deployed to Azure in a private VNet.
Security
Sponsors have accounts in an Azure Active Directory (Azure AD) with business-to-consumer (B2C) enabled
named litwaregamerdata.onmicrosoft.com managed by Litware, Inc. for both GamerData and LitWare, Inc.
services.
Only Litware, Inc. developers and automated testing tools should be able to directly access the GamerData
service. All other use of the service must be through Azure API Management. A description of the security
practices used during development, available on Microsoft SharePoint, must be available to users of the API
under the terms of service.Reporting
Azure Search will be used as the source for running reports. The properties of indexes in Azure Search must
match the names of the properties in DocumentDB.
Performance
The Azure DocumentDB must not be used for reporting purposes. All services must perform queries in the data
store when possible.
Application Structure
Startup.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointController.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointGenerator.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to ensure that sponsors can interact with the GamerData service by using the same credentials as
they use for other LitWare, Inc. services.
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:

Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like
to complete each case. However, there may be additional case studies and sections on this exam. You must
manage your time to ensure that you are able to complete all questions included on this exam in the time
provided.
To answer the questions included in a case study, you will need to reference information that is provided in the
case study. Case studies might contain exhibits and other resources that provide more information about the
scenario that is described in the case study. Each question is independent of the other question on this case
study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to
make changes before you move to the next sections of the exam. After you begin a new section, you cannot
return to this section.
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explorethe content of the case study before you answer the questions. Clicking these buttons displays information such
as business requirements, existing environment, and problem statements. If the case study has an All
Information tab, note that the information displayed is identical to the information displayed on the subsequent
tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
You are a developer for LitWare, Inc., a game development company. You are developing a backend service
for an online social gaming platform named GamerData. The game is built around point generators, which are
associated with physical landmarks. Players claim point generators which give them a set amount of points per
day.
Business Requirements
Mobile App
The game itself runs on various mobile devices and is developed by TailSpin Toys, a company that specializes
in mobile game development. The mobile app will periodically make calls to the GamerData service to find the
five closest point generators that are located less than the specified distance from the player’s current location.
If no point generators are found, the search distance increases until one is found.
The mobile app shows all the point generators owned by each player. The mobile app allows for each player to
search for claimed point generators by player name. This search does not require exact spelling of names. The
details for each claimed generator is shown in the app.
When a player claims a point generator, they should receive an email notification. An Azure Function named
EmailPlayer has been developed to email players with details about recently claimed point generators.
Sponsors
The platform allows business to sponsor point generators within a business location.
Reports
A report named Daily Sponsor Report must be generated each day at midnight. The report must contain a
section for each sponsor. Each sponsor section must contain two subsections.
The first subsection of the report contains the names of the point generators for that sponsor, ordered by the
last time the point generator was claimed. The second subsection contains the current owners for each of the
point generators for the sponsor. Generation of reports must not impact the GamerData service.
Technical Requirements
GamerData Service
All data for the GamerData service is stored in an Azure DocumentDB instance named GamerData. Business
and players interact with the service by using a REST API.
The REST API must:
Produce valid Swagger API specifications for non-obsolete actions.
Be optimized for loading specific point generators.
Follow REST best practices.
Include appropriate terms of service.
Costs for all Azure services must be minimized.
Build and Deployment
The GamerData service will be deployed to Azure in a private VNet.Security
Sponsors have accounts in an Azure Active Directory (Azure AD) with business-to-consumer (B2C) enabled
named litwaregamerdata.onmicrosoft.com managed by Litware, Inc. for both GamerData and LitWare, Inc.
services.
Only Litware, Inc. developers and automated testing tools should be able to directly access the GamerData
service. All other use of the service must be through Azure API Management. A description of the security
practices used during development, available on Microsoft SharePoint, must be available to users of the API
under the terms of service.
Reporting
Azure Search will be used as the source for running reports. The properties of indexes in Azure Search must
match the names of the properties in DocumentDB.
Performance
The Azure DocumentDB must not be used for reporting purposes. All services must perform queries in the data
store when possible.
Application Structure
Startup.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointController.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointGenerator.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to write an Azure Search Query to return data for the first subsection of the Daily Sponsor Report.
Which query string should you use?

DRAG DROPCase Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like
to complete each case. However, there may be additional case studies and sections on this exam. You must
manage your time to ensure that you are able to complete all questions included on this exam in the time
provided.
To answer the questions included in a case study, you will need to reference information that is provided in the
case study. Case studies might contain exhibits and other resources that provide more information about the
scenario that is described in the case study. Each question is independent of the other question on this case
study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to
make changes before you move to the next sections of the exam. After you begin a new section, you cannot
return to this section.
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore
the content of the case study before you answer the questions. Clicking these buttons displays information such
as business requirements, existing environment, and problem statements. If the case study has an All
Information tab, note that the information displayed is identical to the information displayed on the subsequent
tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
You are a developer for LitWare, Inc., a game development company. You are developing a backend service
for an online social gaming platform named GamerData. The game is built around point generators, which are
associated with physical landmarks. Players claim point generators which give them a set amount of points per
day.
Business Requirements
Mobile App
The game itself runs on various mobile devices and is developed by TailSpin Toys, a company that specializes
in mobile game development. The mobile app will periodically make calls to the GamerData service to find the
five closest point generators that are located less than the specified distance from the player’s current location.
If no point generators are found, the search distance increases until one is found.
The mobile app shows all the point generators owned by each player. The mobile app allows for each player to
search for claimed point generators by player name. This search does not require exact spelling of names. The
details for each claimed generator is shown in the app.
When a player claims a point generator, they should receive an email notification. An Azure Function named
EmailPlayer has been developed to email players with details about recently claimed point generators.
Sponsors
The platform allows business to sponsor point generators within a business location.
Reports
A report named Daily Sponsor Report must be generated each day at midnight. The report must contain a
section for each sponsor. Each sponsor section must contain two subsections.
The first subsection of the report contains the names of the point generators for that sponsor, ordered by the
last time the point generator was claimed. The second subsection contains the current owners for each of the
point generators for the sponsor. Generation of reports must not impact the GamerData service.
Technical Requirements
GamerData Service
All data for the GamerData service is stored in an Azure DocumentDB instance named GamerData. Businessand players interact with the service by using a REST API.
The REST API must:
Produce valid Swagger API specifications for non-obsolete actions.
Be optimized for loading specific point generators.
Follow REST best practices.
Include appropriate terms of service.
Costs for all Azure services must be minimized.
Build and Deployment
The GamerData service will be deployed to Azure in a private VNet.
Security
Sponsors have accounts in an Azure Active Directory (Azure AD) with business-to-consumer (B2C) enabled
named litwaregamerdata.onmicrosoft.com managed by Litware, Inc. for both GamerData and LitWare, Inc.
services.
Only Litware, Inc. developers and automated testing tools should be able to directly access the GamerData
service. All other use of the service must be through Azure API Management. A description of the security
practices used during development, available on Microsoft SharePoint, must be available to users of the API
under the terms of service.
Reporting
Azure Search will be used as the source for running reports. The properties of indexes in Azure Search must
match the names of the properties in DocumentDB.
Performance
The Azure DocumentDB must not be used for reporting purposes. All services must perform queries in the data
store when possible.
Application Structure
Startup.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointController.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

PointGenerator.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for
reference only and include a two-character prefix that denotes the specific file to which they belong.)

You need to write a method to return the email address for a given sponsor.
What should you do? To answer, drag the appropriate code segment to the correct location. Each code
segment may be used once, more than once, or not at all. You may need to drag the split bar between panes or
scroll to view content.
Select and Place: