Microsoft 70-534 Free Practice Questions

Answer:

Answer: C

Explanation: For Cloud Services in Azure applications need both web and worker roles to

scale well.

Reference: Application Patterns and Development Strategies for SQL Server in Azure Virtual Machines

https://msdn.microsoft.com/en-us/library/azure/dn574746.aspx

Topic 7, Woodgrove Bank

Overview

Woodgrove Bank has 20 regional offices and operates 1,500 branch office locations. Each regional office hosts the servers, infrastructure, and applications that support that region. Woodgrove Bank plans to move all of Their on-premises resources to Azure, including virtual machine (VM)-based, line-of-business workloads, and SQL databases. You are the owner of the Azure subscription that Woodgrove Bank is using. Your team is using Git repositories hosted on GitHub for source control.

Security

Currently, Woodgrove Bank's Computer Security Incident Response Team (CSIRT) has a problem investigating security issues due to the lack of security intelligence integrated with their current incident response tools. This lack of integration introduces a problem during the detection (too many false positives), assessment, and diagnose stages. You decide to use Azure Security Center to help address this problem.

Woodgrove Bank has several apps with regulated data such as Personally Identifiable Information (PU) that require a higher level of security. All apps are currently secured by using an on-premises Active Directory Domain Services (AD DS). The company depends on following mission-critical apps: WGBLoanMaster, WGBLeaseLeader, and WGBCreditCruncher apps. You plan to move each of these apps to Azure as part of an app migration project.

Apps

The WGBLoanMaster app has been audited for transaction loss. Many transactions have been lost in processing and monetary write-offs have cost the bank. The app runs on two VMs that include several public end points.

The WGBteaseLeader app has been audited for several data breaches. The app includes a SQL Server database and a web-based portal. The portal uses an ASP.NET Web API function to generate a monthly aggregate report from the database.

The WGBCreditCruncher app runs on a VM and is load balanced at the network level. The app includes several stateless components and must accommodate scaling of increased credit processing. The app runs on a nightly basis to process credit transactions that are batched during the day. The app includes a web-based portal where customers can check their credit information. A mobile version of the app allows users to upload check images.

Business Requirements: WGBLoanMasterApp

The app audit revealed a need for zero transaction loss. The business is losing money due to the app losing and not processing loan information. In addition, transactions fail to process after running for a long time. The business has requested the aggregation processing to be scheduled for 01:00 to prevent system slowdown.

WGBLeaseLeader App

The app should be secured to stop data breaches. It the data is breached, it must not be readable. The app is continuing to see increased volume and the business does not want the issues presented in the WGBLoanMaster app. Transaction loss is unacceptable, and although the lease monetary amounts are smaller than loans, they are still an important profit center for Woodgrove Bank. The business would also like the monthly report to be automatically generated on the first of the month. Currently, a user must log in to the portal and click a button to generate the report.

WGBCreditCruncher app

The web-based portal area of the app must allow users to sign in with their Facebook credentials. The bank would like to allow this feature to enable more users to check their credit within the app.

Woodgrove Bank needs to develop a new financial risk modeling feature that they can include in the WGBCreditCruncher app. The financial risk modeling feature has not been developed due to costs associated with processing, transforming, and analyzing the large volumes of data that are collected. You need to find a way to implement parallel processing to ensure that the features runs efficiently, reliably, and quickly. The feature must scale based on computing demand to process the large volumes of data and output several financial risk models.

Technical Requirements: WGBLoanMaster App

The app uses several compute-intensive tasks that create long-running requests to the system. The app is critical to the business and must be scalable to increased loan processing demands. The VMs that run the app include a Windows Task Scheduler task that aggregates loan information from the app to send to a third party. This task runs a console app on the VM.

The app requires a messaging system to handle transaction processing. The messaging system must meet the following requirements:

*Allow messages to reside in the queue for up to a month

*Be able to publish and consume batches of messages

*Allow full integration with the Windows Communication Foundation (WCF) communication stack

*Provide a role-based access model to the queues, including different permissions for senders and receivers

You develop an Azure Resource Manager (ARM) template to deploy the VMs used to support the app. The template must be deployed to a new resource group and you must validate your deployment settings before creating actual resources.

WGBLeaseLeader App

The app must use Azure SQL Databases as a replacement to the current Microsoft SQL Server environment. The monthly report must be automatically generated.

The app requires a messaging system to handle transaction processing. The messaging system must meet the following requirements:

*Require server-side logs of all of the transactions run against your queues

*Track progress of a message within the queue

*Process the messages within 7 days

*Provide a differing timeout value per message

WGBCreditCruncher app

The app must

*Secure inbound and outbound traffic

*Analyze inbound network traffic for vulnerabilities.

*Use an instance-level public IP and allow web traffic on port 443 only.

*Upgrade the portal to a Single Page Application (SPA) that uses JavaScript Azure Active Directory (Azure AD), and the OAuth 2.0 implicit authorization grant to secure the Web API back end.

*Cache authentication and host the Web API back end using the Open Web Interface for

.NET (OWIN) middleware.

*Immediately compress check images received from the mobile web app.

*Schedule processing of the batched credit transactions on a nightly basis.

*Provide parallel processing and scalable computing resources to output financial risk models.

*Use simultaneous compute nodes to enable high performance computing and updating of the financial risk models.

Key Security Areas

Answer: A,B

Explanation: Before you start using the Windows Azure cmdlets to automate deployments, you must configure connectivity between the provisioning computer and Windows Azure. You can do this automatically by downloading the PublishSettings file from Windows Azure and importing it.

To download and import publish settings and subscription information

✑ At the Windows PowerShell command prompt, type the following command, and then press Enter.

Get-AzurePublishSettingsFile

2. Sign in to the Windows Azure Management Portal, and then follow the instructions to download your Windows Azure publishing settings. Save the file as a .publishsettings type file to your computer.

3. In the Windows Azure PowerShell window, at the command prompt, type the following command, and then press Enter.

Import-AzurePublishSettingsFile <mysettings>.publishsettings

Reference: How to: Download and Import Publish Settings and Subscription Information https://msdn.microsoft.com/en-us/library/dn385850%28v=nav.70%29.aspx

Answer:

Explanation:

* You can run programs or scripts in WebJobs in your App Service web app in three ways: on demand, continuously, or on a schedule.

* For continuous WebJobs there is an important feature called "always on" which is only available for a Standard Website, this will make sure your Website and WebJob are always up.

Answer: B

Explanation: General purpose compute: Basic tier

An economical option for development workloads, test servers, and other applications that don't require load balancing, auto-scaling, or memory-intensive virtual machines.

CPU core range: 1-8 RAM range: 0.75 – 14 GB

Disk size: 20-240 GB

Reference: Virtual Machines Pricing. Launch Windows Server and Linux in minutes

http://azure.microsoft.com/en-us/pricing/details/virtual-machines/

Answer: C

Explanation: * Scenario:

/ Mobile Apps: Event-triggered alerts must be pushed to mobile apps by using a custom Node.js script.

/ The service level agreement (SLA) for the solution requires an uptime of 99.9%

* If you are already using Azure Storage Blobs or Tables and you start using queues, you are guaranteed 99.9% availability. If you use Blobs or Tables with Service Bus queues, you will have lower availability.

Note: Microsoft Azure supports two types of queue mechanisms: Azure Queues and Service Bus Queues.

/ Azure Queues, which are part of the Azure storage infrastructure, feature a simple REST- based Get/Put/Peek interface, providing reliable, persistent messaging within and between services.

/ Service Bus queues are part of a broader Azure messaging infrastructure that supports queuing as well as publish/subscribe, Web service remoting, and integration patterns.

Reference: Azure Queues and Service Bus Queues - Compared and Contrasted https://msdn.microsoft.com/en-us/library/azure/hh767287.aspx

Answer: C

Explanation: Cloud-based distribution Point, a Configuration Manager Site System Role in the Cloud

Much of the Configuration Manager topology is made up of distribution points, they are very helpful in many situations where bandwidth and geographical separation are the facts of life, but also hard to manage if you have hundreds or even thousands of them.

This feature started with the vision that it makes perfect sense to have big distribution points in the Windows Azure cloud where one should not worry about things like (but not limited to) size, performance, reliability, security, access from all around the world, hardware/software update issues etc.

Note: Content management in System Center 2012 Configuration Manager provides the tools for you to manage content files for applications, packages, software updates, and operating system deployment. Configuration Manager uses distribution points to store files that are required for software to run on client computers. These distribution points function as distribution centers for the content files and let users download and run the software. Clients must have access to at least one distribution point from which they can download the files.

Reference: New Distribution Points in Configuration Manager SP1 http://blogs.technet.com/b/configmgrteam/archive/2013/01/31/new-distribution-points-in-configuration-manager-sp1.aspx

Answer:

Answer: D

Answer:

Explanation:

workflow Use-WorkflowCheckpointSample

{

# An exception occurs if 'HasBeenSuspended' does not already exist.

# Exceptions that are not caught with a try/catch will cause the runbook to suspend.

Set-AutomationVariable -Name 'HasBeenSuspended' -Value $False

# This line occurs before the checkpoint. When the runbook is resumed after

# suspension, 'Before Checkpoint' will not be output a second time. Write-Output "Before Checkpoint"

# A checkpoint is created. Checkpoint-Workflow

# This line occurs after the checkpoint. The runbook will start here on resume. Write-Output "After Checkpoint"

$HasBeenSuspended = Get-AutomationVariable -Name 'HasBeenSuspended'

# If branch only executes if the runbook has not previously suspended. if (!$HasBeenSuspended) {

Set-AutomationVariable -Name 'HasBeenSuspended' -Value $True

# This will cause a runtime exception. Any runtime exception in a runbook

# will cause the runbook to suspend. 1 + "abc"

}

Write-Output "Runbook Complete"

}

Answer: D

Explanation: Single sign-on (SSO) is a property of access control of multiple related, but independent software systems. With this property a user logs in once and gains access to all systems without being prompted to log in again at each of them.

Reference: http://en.wikipedia.org/wiki/Single_sign-on

Answer:

Topic 3, Contoso, Ltd

Background

Overview

Contoso, Ltd., manufactures and sells golf clubs and golf balls. Contoso also sells golf accessories under the Contoso Golf and Odyssey brands worldwide.

Most of the company's IT infrastructure is located in the company's Carlsbad, California, headquarters. Contoso also has a sizable third-party colocation datacenter that costs the company USD $30,000 to $40,000 a month. Contoso has other servers scattered around the United States.

Contoso, Ltd., has the following goals:

✑ Move many consumer-facing websites, enterprise databases, and enterprise web services to Azure.

✑ Improve the performance for customers and resellers who are access company websites from around the world.

✑ Provide support for provisioning resources to meet bursts of demand.

✑ Consolidate and improve the utilization of website- and database-hosting resources.

✑ Avoid downtime, particularly that caused by web and database server updating.

✑ Leverage familiarity with Microsoft server management tools.

Infrastructure

Contoso's datacenters are filled with dozens of smaller web servers and databases that run on under-utilized hardware. This creates issues for data backup. Contoso currently backs up data to tape by using System Center Data Protection Manager. System Center Operations Manager is not deployed in the enterprise.

All of the servers are expensive to acquire and maintain, and scaling the infrastructure takes significant time. Contoso conducts weekly server maintenance, which causes

downtime for some of its global offices. Special events, such as high-profile golf tournaments, create a large increase in site traffic. Contoso has difficulty scaling the web- hosting environment fast enough to meet these surges in site traffic.

Contoso has resellers and consumers in Japan and China. These resellers must use applications that run in a datacenter that is located in the state of Texas, in the United States. Because of the physical distance, the resellers experience slow response times and downtime.

Business Requirements Management and Performance Management

✑ Web servers and databases must automatically apply updates to the operating

system and products.

✑ Automatically monitor the health of worldwide sites, databases, and virtual machines.

✑ Automatically back up the website and databases.

✑ Manage hosted resources by using on-premises tools.

Performance

✑ The management team would like to centralize data backups and eliminate the use of tapes.

✑ The website must automatically scale without code changes or redeployment.

✑ Support changes in service tier without reconfiguration or redeployment.

✑ Site-hosting must automatically scale to accommodate data bandwidth and number of connections.

✑ Scale databases without requiring migration to a larger server.

✑ Migrate business critical applications to Azure.

✑ Migrate databases to the cloud and centralize databases where possible.

Business Continuity and Support Business Continuity

✑ Minimize downtime in the event of regional disasters.

✑ Recover data if unintentional modifications or deletions are discovered.

✑ Run the website on multiple web server instances to minimize downtime and support a high service level agreement (SLA).

Connectivity

✑ Allow enterprise web services to access data and other services located on- premises.

✑ Provide and monitor lowest latency possible to website visitors.

✑ Automatically balance traffic among all web servers.

✑ Provide secure transactions for users of both legacy and modern browsers.

✑ Provide automated auditing and reporting of web servers and databases.

✑ Support single sign-on from multiple domains.

Development Environment

You identify the following requirements for the development environment:

✑ Support the current development team's knowledge of Microsoft web development and SQL Service tools.

✑ Support building experimental applications by using data from the Azure deployment and on-premises data sources.

✑ Mitigate the need to purchase additional tools for monitoring and debugging.

✑ System designers and architects must be able to create custom Web APIs without requiring any coding.

✑ Support automatic website deployment from source control.

✑ Support automated build verification and testing to mitigate bugs introduced during builds.

✑ Manage website versions across all deployments.

✑ Ensure that website versions are consistent across all deployments.

Technical Requirement Management and Performance Management

✑ Use build automation to deploy directly from Visual Studio.

✑ Use build-time versioning of assets and builds/releases.

✑ Automate common IT tasks such as VM creation by using Windows PowerShell workflows.

✑ Use advanced monitoring features and reports of workloads in Azure by using existing Microsoft tools.

Performance

✑ Websites must automatically load balance across multiple servers to adapt to varying traffic.

✑ In production, websites must run on multiple instances.

✑ First-time published websites must be published by using Visual Studio and scaled to a single instance to test publishing.

✑ Data storage must support automatic load balancing across multiple servers.

✑ Websites must adapt to wide increases in traffic during special events.

✑ Azure virtual machines (VMs) must be created in the same datacenter when applicable.

Business Continuity and Support Business Continuity

✑ Automatically co-locate data and applications in different geographic locations.

✑ Provide real-time reporting of changes to critical data and binaries.

✑ Provide real-time alerts of security exceptions.

✑ Unwanted deletions or modifications of data must be reversible for up to one month, especially in business critical applications and databases.

✑ Any cloud-hosted servers must be highly available.

Enterprise Support

✑ The solution must use stored procedures to access on-premises SQL Server data from Azure.

✑ A debugger must automatically attach to websites on a weekly basis. The scripts

that handle the configuration and setup of debugging cannot work if there is a delay in attaching the debugger.

Answer:

Answer: D

Topic 5, Northwind traders

Background Overview

Northwind Electric Cars is the premier provider of private, low-cost transportation in Denver. Northwind drivers are company employees who work together as a team. The founding partners believe that by hiring their drivers as employees, their drivers focus on providing a great customer experience. Northwind Electric Cars has a reputation for offering fast, reliable, and friendly service, due largely to their extensive network of drivers and their proprietary dispatching software named NorthRide.

Northwind Electric Cars drivers depend on frequent, automatic updates for the NorthRide mobile app. The Northwind management team is concerned about unplanned system downtime and slow connection speeds caused by high usage. Additionally, Northwind's in- house data storage solution is unsustainable because of the new influx of customer data

that is retained. Data backups are made periodically on DVDs and stored on-premises at corporate headquarters.

Apps NorthRide App

Northwind drivers use the NorthRide app to meet customer pickup requests. The app uses

a GPS transponder in each Northwind vehicle and Bing Maps APIs to monitor the location of each vehicle in the fleet in real time. NorthRide allows Northwind dispatchers to optimize their driver coverage throughout the city.

When new customers call, the dispatcher enters their pickup locations into NorthRide. NorthRide identifies the closest available driver. The dispatcher then contacts the driver with the pick-up details. This process usually results in a pick-up time that is far faster than the industry average.

Drivers use NorthRide to track the number of miles they drive and the number of customers they transport. Drivers also track their progress towards their established goals, which are measured by using key performance indicators (KPIs).

NorthRide App 2.0

Northwind Electric Cars is growing quickly. New callers often wait for their calls to be answered because the dispatchers are contacting their drivers to arrange pickups for other customers.

To support the growth of the business, Northwind's development team completes an overhaul of the NorthRide system that it has named NorthRide 2.0. When a dispatcher enters a customer's pickup location, the address and driving directions are automatically sent to the driver who is closest to the customer's pickup location.

Drivers indicate their availability on the NorthRide mobile app and can view progress towards their KPI's in real time. Drivers can also record customer ratings and feedback for each pickup.

Business Requirements Apps

NorthRideFinder App

Northwind Electric Cars needs a customer-facing website and mobile app that allows customers to schedule pickups. Customers should also be able to create profiles that will help ensure the customer gets a ride faster by storing customer information.

Predictor App

Northwind Electric Cars needs a new solution named Predictor. Predictor is an employee- facing mobile app. The app predicts periods of high usage and popular pickup locations and provides various ways to view this predictive data. Northwind uses this information to

better distribute its drivers. Northwind wants to use the latest Azure technology to create this solution.

Other Requirements

✑ On-premises data must be constantly backed up.

✑ Mobile data must be protected from loss, even if connectivity with the backend is lost.

✑ Dispatch offices need to have seamless access to both their primary data center and the applications and services that are hosted in the Azure cloud.

✑ Connectivity needs to be redundant to on-premises and cloud services, while providing a way for each dispatch office to continue to operate even if one or all of the connection options fail.

✑ The management team requires that operational data is accessible 24/7 from any office location.

Technical Requirements Apps and Website

NorthRide / NorthRideFinder Apps:

✑ The solution must support on-premises and Azure data storage.

✑ The solution must scale as necessary based on the current number of concurrent users.

✑ Customer pickup requests from NorthRideFinder must be asynchronous.

✑ The customer pickup request system will be high in volume, and each request will have a short life span.

✑ Data for NorthRideFinder must be protected during a loss of connectivity.

✑ NorthRide users must authenticate to the company's Azure Active Directory.

Northwind Public Website

✑ The customer website must use a WebJob to process profile images into thumbnails

✑ The customer website must be developed with lowest cost and difficulty in mind.

✑ The customer website must automatically scale to minimize response times for customers.

Other Requirements Data Storage:

✑ The data storage must interface with an on-premises Microsoft SQL backend database.

✑ A disaster recovery system needs to be in place for large amounts of data that will backup to Azure.

✑ Backups must be fully automated and managed the Azure Management Portal.

✑ The recovery system for company data must use a hybrid solution to back up both the on-premises Microsoft SQL backend and any Azure storage.

Predictive Routing:

✑ An Azure solution must be used for prediction systems.

✑ Predictive analytics must be published as a web service and accessible by using the REST API.

Security:

✑ The NorthRide app must use an additional level of authentication other than the employee's password.

✑ Access must be secured in NorthRide without opening a firewall port.

✑ Company policy prohibits inbound connections from internet callers to the on- premises network.

✑ Customer usernames in NorthRideFinder cannot exceed 10 characters.

✑ Customer data in NorthRideFinder can be received only by the user ID that is associated with the data.

Answer: