CASE STUDY
Background:
You are developer for Fabrikam, a company that specializes in payment processing. Fabrikam is developing a solution to process payments for various events, such as music concerts. You develop an ASP.NET MVC website that is hosted in Azure to support an upcoming music concert. The music concert is expected to generate a large volume of ticket sales in a short amount of time.
The website uploads information to an Azure storage queue. A worker role in Azure retrieves information from the queue and generates the concert tickets in a PDF file format after the financial transaction is approved.You observe a delay between the time the website adds a message to a queue and the time it becomes available to read from the queue. After examining the queue, you determine that no queue messages have a
DequeueCount value greater than zero. The website does not throw any errors.
Business Requirements
Payments:
The music concert website must be able to submit event payment information for processing. The website must remain responsive while submitting payment information. Customers must be able to add notes about their orders to a free-form control on the website. These notes must be submitted with the payment when the customer submits an order.
Customers often enter notes that exceed 7 KB in size.
Technical Requirements
Payment Submission and Processing:
Event payment information must be sent from the website to a Windows Communication Foundation (WCF) service worker role. The worker role must submit the information to the payment processor in JSON format.
Payment Processing
You have the following payment processing requirements:
If the number of messages in a queue goes above or below a specified threshold, worker role instances must be created or deleted as needed. This process must be completed by using the least amount of effort.
It must be easy to reconfigure role instance thresholds.
Payments must be retrieved from the queue in the maximum batch sizes that are allowed by the queue and pulled from the queue for 5 minutes.
The payment queue must not be re-created when processing payments.
During single Payment processing, the number of tickets available for an event must be updated. The update operation must be retried for 30 seconds or 5 retry attempts, whichever occurs first. Each retry should pause for at least two seconds and for one second longer than the previous attempt. If the update fails, the payment should be placed in the poison queue.
Storage:
You have the following storage requirements:
Payment information must be stored by using Azure Queue storage. Connection to the Azure storage account has been established in a configured setting namedStorageConnectionString, which is configured for the web and worker roles.
A payment processing queue and a poison payment queue must be used when processing payments.
Azure Queue message content must be XML-safe and UTF-8 encoded.
An Azure storage account must be established for diagnostic information in a configured setting namedDiagnosticsStorageConnectionString, which is configured for both the web and worker roles.
Security and Monitoring
Security
The web role must be secured by using HTTPS.
Monitoring
You must collect diagnostic data for both the web and worker roles by using the Diagnostics module.
Diagnostics configuration changes must not require the code of the roles to be rebuilt. The diagnostic data is used for debugging and troubleshooting, measuring performance, monitoring resource usage, traffic analysis and capacity planning, and auditing.
Performance testing must evaluate the roles under normal and stress conditions without incurring changes for running Azure. Memory allocation, function time, and multithreading concurrency issues must be evaluated.
Deployment:
You purchase a custom domain name fabrikamfunding.com to host the website, web role, and worker roles.
You must deploy an HTTPS certificate with the web role, and you must update associated configuration files accordingly.
Web role and worker role instance sizes must be specified as Medium. You must deploy one web role instancenamed FabrikamFundingPaymentGenerator, and worker role instances named
FabrikamFundingPaymentProcessor.
Application Structure:
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to while they belong.

The SendMessageAsync method of the QueueManager class occasionally throws errors.
You need to correct the errors.
What should you do?

DRAG DROP
You need to add code to CommentController.cs to enable moderation of comments.
How should you complete the code? To answer, drag the appropriate code segments to the correct locations.
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.
NOTE: Each correct selection is worth point.
Select and Place:

CASE STUDY
Background:
You are developer for Fabrikam, a company that specializes in payment processing. Fabrikam is developing asolution to process payments for various events, such as music concerts. You develop an ASP.NET MVC website that is hosted in Azure to support an upcoming music concert. The music concert is expected to generate a large volume of ticket sales in a short amount of time.
The website uploads information to an Azure storage queue. A worker role in Azure retrieves information from the queue and generates the concert tickets in a PDF file format after the financial transaction is approved.
You observe a delay between the time the website adds a message to a queue and the time it becomes available to read from the queue. After examining the queue, you determine that no queue messages have a
DequeueCount value greater than zero. The website does not throw any errors.
Business Requirements
Payments:
The music concert website must be able to submit event payment information for processing. The website must remain responsive while submitting payment information. Customers must be able to add notes about their orders to a free-form control on the website. These notes must be submitted with the payment when the customer submits an order.
Customers often enter notes that exceed 7 KB in size.
Technical Requirements
Payment Submission and Processing:
Event payment information must be sent from the website to a Windows Communication Foundation (WCF) service worker role. The worker role must submit the information to the payment processor in JSON format.
Payment Processing
You have the following payment processing requirements:
If the number of messages in a queue goes above or below a specified threshold, worker role instances must be created or deleted as needed. This process must be completed by using the least amount of effort.
It must be easy to reconfigure role instance thresholds.
Payments must be retrieved from the queue in the maximum batch sizes that are allowed by the queue and pulled from the queue for 5 minutes.
The payment queue must not be re-created when processing payments.
During single Payment processing, the number of tickets available for an event must be updated. The update operation must be retried for 30 seconds or 5 retry attempts, whichever occurs first. Each retry should pause for at least two seconds and for one second longer than the previous attempt. If the update fails, the payment should be placed in the poison queue.
Storage:
You have the following storage requirements:
Payment information must be stored by using Azure Queue storage. Connection to the Azure storage account has been established in a configured setting namedStorageConnectionString, which is configured for the web and worker roles.
A payment processing queue and a poison payment queue must be used when processing payments.
Azure Queue message content must be XML-safe and UTF-8 encoded.
An Azure storage account must be established for diagnostic information in a configured setting namedDiagnosticsStorageConnectionString, which is configured for both the web and worker roles.
Security and Monitoring
Security
The web role must be secured by using HTTPS.
Monitoring
You must collect diagnostic data for both the web and worker roles by using the Diagnostics module.
Diagnostics configuration changes must not require the code of the roles to be rebuilt. The diagnostic data is used for debugging and troubleshooting, measuring performance, monitoring resource usage, traffic analysis and capacity planning, and auditing.
Performance testing must evaluate the roles under normal and stress conditions without incurring changes for running Azure. Memory allocation, function time, and multithreading concurrency issues must be evaluated.Deployment:
You purchase a custom domain name fabrikamfunding.com to host the website, web role, and worker roles.
You must deploy an HTTPS certificate with the web role, and you must update associated configuration files accordingly.
Web role and worker role instance sizes must be specified as Medium. You must deploy one web role instance named FabrikamFundingPaymentGenerator, and worker role instances named
FabrikamFundingPaymentProcessor.
Application Structure:
Relevant portions of the app files are shown below. Line numbers are included for reference only and include a two-character prefix that denotes the specific file to while they belong.

You need to diagnose the source of the performance issues when preparing concert tickets.
Which two actions should you perform? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point. https://docs.microsoft.com/en-us/azure/storage/storage-monitoring-diagnosing-troubleshooting#you-areexperiencing-unexpected-delays-in-message-delivery

DRAG DROP
You need to implement the StartNotify method in MainPage.xaml.cs to enable the receiving of notifications.
How should you complete the code? To answer, drag the appropriate code segments to the correct locations.
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.
NOTE: Each correct selection is worth point.
Select and Place:

DRAG DROP
You need to add code at line CC63 to ensure that the Interaction Agent is invoked.
How should you complete the code? To answer, drag the appropriate code segments to the correct locations.
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.NOTE: Each correct selection is worth point.
Select and Place:

HOTSPOT
You need to implement exception handling for the ModifyCommentText method in the WikiAgent class.How should you complete the code? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth point.
Hot Area:

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:

*************
You need to ensure that moderators can be added to the system.
Which authentication approach should you use?

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:

*************
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:

*******************8
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:

***********
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?