You are migrating an existing solution to Azure…..

You are migrating an existing solution to Azure. The solution includes a user interface tier and a database tier.The user interface tier runs on multiple virtual machines (VMs). The user interface tier has a website that usesNode.js. The user interface tier has a background process that uses Python.
This background process runs as a scheduled job. The user interface tier is updated frequently. The database tier uses a self-hosted MySQLdatabase. The user interface tier requires up to 25 CPU cores. You must be able to revert the user interface tier to a previous version if updates to the website cause technical problems. The database requires up to 50 GB of memory. The database must run in a single VM. You need to deploy the solution to Azure.
What should you do first?
A. Deploy the entire solution to an Azure Web App. Use a web job that runs continuously to host the database.
B. Configure Microsoft Visual Team Services to continuously deploy the user interface tier to the Azure Web App service. Deploy the production builds and the staging builds of the user interface tier to separate slots.
C. Deploy the entire solution to an Azure Web App. Use a web job that runs continuously to host the user interface tier.
D. Deploy the user interface tier to a VM. Use multiple availability sets to continuously deploy updates from Microsoft Visual Studio Online.
Continue reading “You are migrating an existing solution to Azure…..”

You are using Microsoft Visual Studio to develop an App Service Web App….

– You are using Microsoft Visual Studio to develop an App Service Web App named WebApp.
– The app must collect the statistics and details on the application dependencies.
– You need to set up, configure, and validate monitoring using Application Insights.
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.

Continue reading “You are using Microsoft Visual Studio to develop an App Service Web App….”

You administer an Azure environment that contains multiple virtual machines (VMs).You need to view and retrieve diagnostic logs for all VMs.
Which storage type should you use for each data source? To answer, select the appropriate options in theanswer area.

Continue reading

Case Study: This is a case study. Case studies are not timed separately……

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. SecuritySponsors 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 StructureStartup.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 forreference 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 managementcaching.
In the Azure portal, which value should you use for the Vary by Query string parameters setting?
A. Name
B. longitude; latitude; minDistance
C. longitude; latitude; dateLastClaimed
D. Id
Continue reading “Case Study: This is a case study. Case studies are not timed separately……”

You are developer for Fabrikam, a company that specializes in payment processing….

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 fromthe 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 becomesavailable to read from the queue. After examining the queue, you determine that no queue messages have aDequeueCount 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 retryshould pause for at least two seconds and for one second longer than the previous attempt. If the updatefails, 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 named StorageConnectionString, 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 settingnamedDiagnosticsStorageConnectionString, 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 namedFabrikamFundingPaymentProcessor.
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?
A. Update the QueueManager to use the Put Message operation of the Queue Service REST API. Use HTTP compression for all calls made to the REST API.
B. Encode the notesfield content by using UTF-32 encoding.
C. UpdateSendMessageAsyncmethod of the QueueManager class to store the notes field in BLOB storage. Update the EventPaymentclass to store the BLOB uniform resource identifier (URI). Extract the notes BLOB information by using the BLOB URI in the ProcessMessagesAsyncmethod of the QueueManager class.
D. Update the notesfield to a byte array. Binary encode and decode the notescontent when sending or receiving an EventPaymentclass.
Continue reading “You are developer for Fabrikam, a company that specializes in payment processing….”

You are developing a web-based solution that students and teachers……

Background: You are developing a web-based solution that students and teachers can use to collaborate on written assignments. Teachers can also use the solution to detect potential plagiarism, and they can manage assignments and data by using locally accessible network shares.

Business Requirements: The solution consists of three parts: a website where students work on assignments and where teachers view and grade assignments, the plagiarism detection service, and a connector service to manage data by using a network share.
The system availability agreement states that operating hours are weekdays between midnight on Sunday and midnight on Friday.

Plagiarism Service: The plagiarism detection portion of the solution compares a new work against a repository of existing works.
The initial dataset contains a large database of existing works. Teachers upload additional works. In addition, the service itself searches for other works and adds those works to the repository.

Technical Requirements Website: The website for the solution must run on an Azure web role.

Plagiarism Service: The plagiarism detection service runs on an Azure worker role. The computation uses a random number generator. Certain values can result in an infinite loop, so if a particular work item takes longer than one hour to process, other instances of the service must be able to process the work item. Computation results are cached in local storage resources to reduce computation time.

Repository of Existing Works: The plagiarism detection service works by comparing student submissions against a repository of existing works by using a custom matching algorithm. The master copies of the works are stored in Azure blob storage.

A daily process synchronizes files between blob storage and a file share on a virtual machine (VM). As part of this synchronization, the Existing WorkRepository object adds the files to Azure Cache to improve the display performance of the website. If a student’s submission is overdue, the Late property is set to the number of days that the work is overdue. Work files can be downloaded by using the Work action of the Teacher Controller object.

Network Connector: Clients can interact with files that are stored on the VM by using a network share. The network permissions are configured in a startup task in the plagiarism detection service.

Service Monitoring: The CPU of the system on which the plagiarism detection service runs usually limits the plagiarism detection service. However, certain combinations of input can cause memory issues, which results in decreased performance. The average time for a given computation is 45 seconds. Unexpected results during computations might cause a memory dump. Memory dump files are stored in the Windows temporary folder on the VM that hosts the worker role.

Security: Only valid users of the solution must be able to view content that users submit. Privacy regulations require that all content that users submit must be retained only in Azure Storage. All documents that students upload must be signed by using a certificate named DocCert that is installed in both the worker role and the web role.

Solution Development: You use Microsoft Visual Studio 2013 and the Azure emulator to develop and test both the compute component and the storage component. New versions of the solution must undergo testing by using production data.
Scaling: During non-operating hours, the plagiarism detection service should not use more than 40 CPU cores. During operating hours, the plagiarism detection service should automatically scale when 500 work items are waiting to be processed. To facilitate maintenance of the system, no plagiarism detection work should occur during non-operating hours. All ASP.NET MVC actions must support files that are up to 2 GB in size.

Biographical Information: Biographical information about students and teachers is stored in a Microsoft Azure SQL database. All services run in the US West region. The plagiarism detection service runs on Extra Large instances. The Azure worker role must fully utilize all available CPU cores.

Solution Structure: Relevant portions of the solution files are shown in the following code segments. Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which the line belongs.







HOTSPOT
You need to implement the Work action on the TeacherController object.
How should you complete the relevant code? To answer, select the appropriate options in the answer area.
Hot Area:

Continue reading “You are developing a web-based solution that students and teachers……”

Contoso, Ltd. is developing a patient monitoring solution for a hospital…..

Background: Contoso, Ltd. is developing a patient monitoring solution for a hospital. The solution consists of an Azure website and a set of mobile applications that health care providers use to monitor patients remotely. Monitoring devices that run the embedded version of Windows will be attached to patients. The devices will collect information from patients and will transmit real-time continuous data to a service that runs on Azure. The service collects and distributes data. The data that the service provides must be accessible by the website and by the mobile applications.

Business Requirements Patients: All patient data must be stored securely on Azure. Data security must meet or exceed Health Insurance Portability and Accountability Act of 1996 (HIPAA) standards in the United States and must meet or exceed ISO/ICE 27002 data security standards in the rest of the world.

Contractors: Third-party contractors will develop the mobile applications. All contractors must develop the applications by using virtual machines (VMs) that are hosted on Azure. Only authorized contractors and authorized IP addresses are permitted to access the VMs. The contractors can use Near Field Communication (NFC) tags to launch Remote Desktop (RD) connections to the VMs from NFC-enabled devices. For testing purposes, contractors must be able to run multiple instances of mobile applications within the VMs.

Data Collection and Distribution Service: The service must monitor the patient data and send out alerts to health care providers when specific conditions are detected. The service must send the alerts to mobile applications and to the website in real time so that doctors, nurses, and caregivers can attend to the patient. Partner organizations and diagnostic laboratories must be able to securely access the data and the website from remote locations.

Current Issues: A partner that is testing a prototype of the website reports that after signing in to the website, the partner is redirected to the settings page instead of to the home page.
The data from the patient devices is slow to appear on the website and does not always appear. All patient devices online have active connections to the data collection service.

Technical Requirements Contractors: All contractors will use virtual machines that are initially configured as size A3. Contractors must sign in to the assigned VM by using IP addresses from a list of preapproved addresses.
Data Collection and Distribution Service: The service runs Node.js in a worker role. The service must use at least 2048-bit encryption and must use port 8888. All patient information must be encrypted and stored by using a NoSQL data store. Data must be stored and retrieved securely by using RESTful endpoints.
Data must NOT be stored within a virtual machine. All deployed services must send an alert email to watchguard@contoso.com when any of the following conditions is met: The CPU Percentage metric is at or above 85 percent for at least 10 minutes. The Network In metric is at or above 2 KB for at least 10 minutes. The Network Out metric is at or above 2 KB for at least 10 minutes. The Disk Write metric is at or above 1 KB/sec for at least 30 minutes. The Disk Read metric is at or above 1 KB/sec for at least 30 minutes.

Website and Mobile Devices: The website must be secure and must be accessible only within the hospital’s physical grounds. All mobile applications and websites must be responsive. All websites must produce error logs that can be viewed remotely.

Virtual Machines: All Azure instances must be deployed and tested on staging instances before they are deployed to production instances. All deployed instances must scale up to the next available CPU instance at a CPU usage threshold of 90 percent and scale down when the usage is below 10 percent.
Application Structure: Relevant portions of the application files are shown in the following code segments. 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.

HOTSPOT
You run the following Windows PowerShell script. Line numbers are included for reference only.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.
Hot Area:


Continue reading “Contoso, Ltd. is developing a patient monitoring solution for a hospital…..”

Developing Microsoft Azure Solution…

Background: You are Developing Microsoft Azure Solution that individuals and small businesses will use to prepare and file tax-related documents.
Business Requirements General: The solution must provide a way for customers to enter personal and demographic information. Customers must be able to upload income documents and related documents to the solution. The solution must provide reports and summary documents for customers in PDF format.
Scope and Device Accessibility: The solution must support two operational modes: On-Peak and Off-Peak. On-Peak is defined as the first quarter of a year. Off-Peak is defined as the other three quarters of a year. Customers must be able to access the solution by using desktop computers, laptop computers, mobile devices, and tablets.
High Availability and Business Continuity: The solution must be available at all times. When the solution transitions between Off-Peak mode and On-Peak mode, solution availability must not be affected. Disaster recovery must be established for the customers’ stored data.
Diagnostics: The solution must log relevant diagnostic data that can be used to troubleshoot the cloud service.
Scalability: The solution must scale out while transitioning from Off-Peak mode to On-Peak mode.
Cost: The solution must use cloud resources optimally to minimize operating costs.
Storage and Security: The solution must be secure to prevent any anonymous access (including read access) to the customers’ tax documents.
Cross-Premises Networking: The solution must extend the developers’ on-premises network into Azure.
Technical Requirements: The logical design for the solution is shown in the following exhibit.

Platform-as-a-Service (PaaS): The solution must have two roles: a web role and worker role. The web interface of the solution uses a web role to accept and send user input and any related documents. The worker role must access the stored data and prepare the tax documents in the background.
Compute: The solution must support a minimum of 10 role instances. When the solution is in On-Peak mode, each role instance must be allocated at least 6 GB of memory. The memory can be scaled down to 3 GB when the solution is in Off-Peak mode.
The solution must cache documents locally. The cache does not need to be refreshed during the lifecycle of the worker role.
Role instances that are running should not be affected by topology changes such as an increase in instance count.
Storage: The web role must store documents in blob storage. A SQL database is used to store customer information.
The worker role must use queues to process the final tax documents.
Performance and Scalability: When the solution is in Off-Peak mode, it must support at least 150 concurrent database sessions, and the maximum size of the database is 50 GB. When the solution is in On-Peak mode, it must support 750 concurrent database sessions, and the maximum size of the database is 300 GB. Geo-replication must be enabled and must be configurable by using the Azure management portal.
Software Prerequisites: The solution must install the software that is necessary to generate PDF documents on the server. The software will be provided as a Windows Installer package.
Debugging: Solution errors and warnings that occur in a web role must be logged. The worker role must log any crash dump files. Detailed information about errors and their context must be collected so that the environment in which errors occurred can be simulated locally.
Security: At the time that a customer’s tax information and documents are accepted, the solution must send an email to the customer. The email contains a secure hyperlink that the customer can use to upload any additional necessary documents. The customer is asked to upload these documents within 48 hours. If the customer does not upload the documents within 48 hours, the solution should not issue a new hyperlink. The solution must send an email to the customer to remind the customer to use the original hyperlink to upload any additional necessary documents.
Network Services: The solution must use a cross-premises secure network. The network must be configurable by using the Azure management portal.
Social Structure: Relevant portions of the solution files are shown in the following code segments. 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.


###EndCaseStudy###
You need to configure diagnostics for the Azure solution.
Which two types of diagnostic data should you collect? Each correct answer presents part of the solution.
A. application logs
B. IIS logs
C. crash dumps
D. trace logs
E. performance counters
F. infrastructure logs
Continue reading “Developing Microsoft Azure Solution…”