You need to recommend a solution to deploy containers that run an application. The application has two tiers. Each tier is implemented as a separate Docker Linux-based image. The solution must meet the following requirements: * The front-end tier must be accessible by using a public IP address on port 80. * The backend tier must be accessible by using port 8080 from the front-end tier only. * Both containers must be able to access the same Azure file share. * If a container fails, the application must restart automatically. * Costs must be minimized. What should you recommend using to host the application?
Correct Answer: C
Azure Container Instances enables a layered approach to orchestration, providing all of the scheduling and management capabilities required to run a single container, while allowing orchestrator platforms to manage multi-container tasks on top of it. Because the underlying infrastructure for container instances is managed by Azure, an orchestrator platform does not need to concern itself with finding an appropriate host machine on which to run a single container. Azure Container Instances can schedule both Windows and Linux containers with the same API. Orchestration of container instances exclusively Because they start quickly and bill by the second, an environment based exclusively on Azure Container Instances offers the fastest way to get started and to deal with highly variable workloads. Reference: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-overview https://docs.microsoft.com/en-us/azure/container-instances/container-instances-orchestrator-relationship
Question 147
You have an Azure virtual machine named VM1 that runs Windows Server 2019 and contains 500 GB of data files. You are designing a solution that will use Azure Data Factory to transform the data files, and then load the files to Azure Data Lake Storage. What should you deploy on VM1 to support the design?
Correct Answer: D
The integration runtime (IR) is the compute infrastructure that Azure Data Factory uses to provide data- integration capabilities across different network environments. For details about IR, see Integration runtime overview. A self-hosted integration runtime can run copy activities between a cloud data store and a data store in a private network. It also can dispatch transform activities against compute resources in an on-premises network or an Azure virtual network. The installation of a self-hosted integration runtime needs an on-premises machine or a virtual machine inside a private network. Reference: https://docs.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime Design Data Storage Testlet 2 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 questions in 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 section 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 in 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. Overview Contoso, Ltd, is a US-based financial services company that has a main office in New York and a branch office in San Francisco. Existing Environment. Payment Processing System Contoso hosts a business-critical payment processing system in its New York data center. The system has three tiers: a front-end web app, a middle-tier web API, and a back-end data store implemented as a Microsoft SQL Server 2014 database. All servers run Windows Server 2012 R2. The front-end and middle-tier components are hosted by using Microsoft Internet Information Services (IIS). The application code is written in C# and ASP.NET. The middle-tier API uses the Entity Framework to communicate to the SQL Server database. Maintenance of the database is performed by using SQL Server Agent jobs. The database is currently 2 TB and is not expected to grow beyond 3 TB. The payment processing system has the following compliance-related requirements: * Encrypt data in transit and at rest. Only the front-end and middle-tier components must be able to access the encryption keys that protect the data store. * Keep backups of the data in two separate physical locations that are at least 200 miles apart and can be restored for up to seven years. * Support blocking inbound and outbound traffic based on the source IP address, the destination IP address, and the port number. * Collect Windows security logs from all the middle-tier servers and retain the logs for a period of seven years. * Inspect inbound and outbound traffic from the front-end tier by using highly available network appliances. * Only allow all access to all the tiers from the internal network of Contoso. Tape backups are configured by using an on-premises deployment of Microsoft System Center Data Protection Manager (DPM), and then shipped offsite for long term storage. Existing Environment. Historical Transaction Query System Contoso recently migrated a business-critical workload to Azure. The workload contains a .NET web service for querying the historical transaction data residing in Azure Table Storage. The .NET web service is accessible from a client app that was developed in-house and runs on the client computers in the New York office. The data in the table storage is 50 GB and is not expected to increase. Existing Environment. Current Issues The Contoso IT team discovers poor performance of the historical transaction query system, as the queries frequently cause table scans. Requirements. Planned Changes Contoso plans to implement the following changes: * Migrate the payment processing system to Azure. * Migrate the historical transaction data to Azure Cosmos DB to address the performance issues. Requirements. Migration Requirements Contoso identifies the following general migration requirements: * Infrastructure services must remain available if a region or a data center fails. Failover must occur without any administrative intervention. * Whenever possible, Azure managed services must be used to minimize management overhead. * Whenever possible, costs must be minimized. Contoso identifies the following requirements for the payment processing system: * If a data center fails, ensure that the payment processing system remains available without any administrative intervention. The middle-tier and the web front end must continue to operate without any additional configurations. * Ensure that the number of compute nodes of the front-end and the middle tiers of the payment processing system can increase or decrease automatically based on CPU utilization. * Ensure that each tier of the payment processing system is subject to a Service Level Agreement (SLA) of 99.99 percent availability. * Minimize the effort required to modify the middle-tier API and the back-end tier of the payment processing system. * Payment processing system must be able to use grouping and joining tables on encrypted columns. * Generate alerts when unauthorized login attempts occur on the middle-tier virtual machines. * Ensure that the payment processing system preserves its current compliance status. * Host the middle tier of the payment processing system on a virtual machine Contoso identifies the following requirements for the historical transaction query system: * Minimize the use of on-premises infrastructure services. * Minimize the effort required to modify the .NET web service querying Azure Cosmos DB. * Minimize the frequency of table scans. * If a region fails, ensure that the historical transaction query system remains available without any administrative intervention. Requirements. Information Security Requirements The IT security team wants to ensure that identity management is performed by using Active Directory. Password hashes must be stored on-premises only. Access to all business-critical systems must rely on Active Directory credentials. Any suspicious authentication attempts must trigger a multi-factor authentication prompt automatically.
Question 148
You manage a network that includes an on-premises Active Directory Domain Services domain and an Azure Active Directory (Azure AD). Employees are requires to use different accounts when using on-premises or cloud resources. You must recommend a solution that lets employees sign in to all company resources by using a single account. The solution must implement an identity provider. You need provide guidance on the different identity providers. How should you describe each identity provider? To answer, select the appropriate description from each list in the answer area. NOTE: Each correct selection is worth one point.
You plan to store data in Azure Blob storage for many years. The stored data will be accessed rarely. You need to ensure that the data in Blob storage is always available for immediate access. The solution must minimize storage costs. Which storage tier should you use?
Correct Answer: A
Data in the cool access tier can tolerate slightly lower availability, but still requires high durability, retrieval latency, and throughput characteristics similar to hot data. For cool data, a slightly lower availability service- level agreement (SLA) and higher access costs compared to hot data are acceptable trade-offs for lower storage costs. Incorrect Answers: B: Archive storage stores data offline and offers the lowest storage costs but also the highest data rehydrate and access costs. Archive - Optimized for storing data that is rarely accessed and stored for at least 180 days with flexible latency requirements (on the order of hours). Reference: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-storage-tiers
Question 150
A company has an existing web application that runs on virtual machines (VMs) in Azure. You need to ensure that the application is protected from SQL injection attempts and uses a layer-7 load balancer. The solution must minimize disruption to the code for the existing web application. What should you recommend? To answer, drag the appropriate values to the correct items. Each value 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 one point.
Correct Answer:
Explanation Box 1: Azure Application Gateway Azure Application Gateway provides an application delivery controller (ADC) as a service. It offers various layer 7 load-balancing capabilities for your applications. Box 2: Web Application Firwewall (WAF) Application Gateway web application firewall (WAF) protects web applications from common vulnerabilities and exploits. This is done through rules that are defined based on the OWASP core rule sets 3.0 or 2.2.9. There are rules that detects SQL injection attacks. References: https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-faq https://docs.microsoft.com/en-us/azure/application-gateway/waf-overview
