What should you recommend to meet the monitoring requirements for App2?
A. VM insights
B. Azure Application Insights
C. Microsoft Sentinel
D. Container insights
Scenario: You need to monitor App2 to analyze how long it takes to perform different transactions within the application. The solution must not require changes to the application code. Unified cross-component transaction diagnostics. The unified diagnostics experience automatically correlates server-side telemetry from across all your Application Insights monitored components into a single view. It doesn't matter if you have multiple resources. Application Insights detects the underlying relationship and allows you to easily diagnose the application component, dependency, or exception that caused a transaction slowdown or failure. Note: Components are independently deployable parts of your distributed/microservices application. Developers and operations teams have code-level visibility or access to telemetry generated by these application components. Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/app/transaction-diagnostics
Question 262
You need to recommend a data storage strategy for WebApp1. What should you include in the recommendation?
A. an Azure virtual machine that runs SQL Server
B. a fixed-size DTU Azure SQL database
C. an Azure SQL Database elastic pool
D. a vCore-based Azure SQL database
The use of WebApp1 is unpredictable. At peak times, users often report delays. At other times, many resources for WebApp1 are underutilized. Database metrics for the production instance of WebApp1 must be available for analysis so that database administrators can optimize the performance settings. Note: A virtual core (vCore) represents a logical CPU and offers you the option to choose between generations of hardware and the physical characteristics of the hardware (for example, the number of cores, the memory, and the storage size). The vCore-based purchasing model gives you flexibility, control, transparency of individual resource consumption, and a straightforward way to translate on-premises workload requirements to the cloud. This model optimizes price, and allows you to choose compute, memory, and storage resources based on your workload needs. Incorrect: Not C: Azure SQL Database elastic pools are a simple, cost-effective solution for managing and scaling multiple databases, not for a single database. Reference: https://docs.microsoft.com/en-us/azure/azure-sql/database/service-tiers-sql-database-vcore
Question 263
HOTSPOT - You plan to migrate App1 to Azure. You need to recommend a storage solution for App1 that meets the security and compliance requirements. Which type of storage should you recommend, and how should you recommend configuring the storage? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:
Box 1: Standard general-purpose v2 Standard general-purpose v2 supports Blob Storage. Azure Storage provides data protection for Blob Storage and Azure Data Lake Storage Gen2. Scenario: Litware identifies the following security and compliance requirements: - Once App1 is migrated to Azure, you must ensure that new data can be written to the app, and the modification of new and existing data is prevented for a period of three years. - On-premises users and services must be able to access the Azure Storage account that will host the data in App1. - Access to the public endpoint of the Azure Storage account that will host the App1 data must be prevented. - All Azure SQL databases in the production environment must have Transparent Data Encryption (TDE) enabled. App1 must NOT share physical hardware with other workloads. Box 2: NFSv3 - Scenario: Plan: Migrate App1 to Azure virtual machines. Blob storage now supports the Network File System (NFS) 3.0 protocol. This support provides Linux file system compatibility at object storage scale and prices and enables Linux clients to mount a container in Blob storage from an Azure Virtual Machine (VM) or a computer on-premises. Reference: https://docs.microsoft.com/en-us/azure/storage/blobs/data-protection-overview
Question 264
HOTSPOT - You plan to migrate DB1 and DB2 to Azure. You need to ensure that the Azure database and the service tier meet the resiliency and business requirements. What should you configure? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:
Box 1: An Azure SQL Database elastic pool Scenario: * Resiliency Requirements. Once migrated to Azure, DB1 and DB2 must meet the following requirements: Maintain availability if two availability zones in the local Azure region fail. Fail over automatically. Minimize I/O latency. * Litware identifies the following business requirements: Minimize administrative effort. Minimize costs. Box 2: Business Critical
Question 265
DRAG DROP - You need to recommend a solution that meets the file storage requirements for App2. What should you deploy to the Azure subscription and the on-premises network? To answer, drag the appropriate services to the correct locations. Each service 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. Select and Place:
Box 1: Azure Files - Scenario: App2 has the following file storage requirements: - Save files to an Azure Storage account. - Replicate files to an on-premises location. - Ensure that on-premises clients can read the files over the LAN by using the SMB protocol. Box 2: Azure File Sync - Use Azure File Sync to centralize your organization's file shares in Azure Files, while keeping the flexibility, performance, and compatibility of an on-premises file server. Azure File Sync transforms Windows Server into a quick cache of your Azure file share. You can use any protocol that's available on Windows Server to access your data locally, including SMB, NFS, and FTPS. You can have as many caches as you need across the world. Reference: https://docs.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide
Question 266
HOTSPOT - You are evaluating whether to use Azure Traffic Manager and Azure Application Gateway to meet the connection requirements for App1. What is the minimum numbers of instances required for each service? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:
Box 1: 1 - App1 will only be accessible from the internet. App1 has the following connection requirements: * Connections to App1 must be active-active load balanced between instances. * All connections to App1 from North America must be directed to the East US region. All other connections must be directed to the West Europe region. App1 will have six instances: three in the East US Azure region and three in the West Europe Azure region. Note: Azure Traffic Manager is a DNS-based traffic load balancer. This service allows you to distribute traffic to your public facing applications across the global Azure regions. Box 2: 2 - For production workloads, run at least two gateway instances. A single Application Gateway deployment can run multiple instances of the gateway. Use one Application Gateway in East US Region, and one in the West Europe region. Reference: https://docs.microsoft.com/en-us/azure/architecture/high-availability/reference-architecture-traffic-manager-application-gateway
Question 267
HOTSPOT - How should the migrated databases DB1 and DB2 be implemented in Azure? Hot Area:
Box 1: SQL Managed Instance - Scenario: Once migrated to Azure, DB1 and DB2 must meet the following requirements: - Maintain availability if two availability zones in the local Azure region fail. - Fail over automatically. - Minimize I/O latency. The auto-failover groups feature allows you to manage the replication and failover of a group of databases on a server or all databases in a managed instance to another region. It is a declarative abstraction on top of the existing active geo-replication feature, designed to simplify deployment and management of geo- replicated databases at scale. You can initiate a geo-failover manually or you can delegate it to the Azure service based on a user-defined policy. The latter option allows you to automatically recover multiple related databases in a secondary region after a catastrophic failure or other unplanned event that results in full or partial loss of the SQL Database or SQL Managed Instance availability in the primary region. Box 2: Business critical - SQL Managed Instance is available in two service tiers: General purpose: Designed for applications with typical performance and I/O latency requirements. Business critical: Designed for applications with low I/O latency requirements and minimal impact of underlying maintenance operations on the workload. Reference: https://docs.microsoft.com/en-us/azure/azure-sql/database/auto-failover-group-overview https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview
Question 268
HOTSPOT - You design a solution for the web tier of WebApp1 as shown in the exhibit. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. Hot Area:
Box 1: Yes - Any new deployments to Azure must be redundant in case an Azure region fails. Traffic Manager is resilient to failure, including the failure of an entire Azure region. Box 2: No - Traffic Manager provides load balancing, but not auto-scaling. Box 3: No - Automatic failover using Azure Traffic Manager: when you have complex architectures and multiple sets of resources capable of performing the same function, you can configure Azure Traffic Manager (based on DNS) to check the health of your resources and route the traffic from the non-healthy resource to the healthy resource. Reference: https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview https://docs.microsoft.com/en-us/azure/networking/disaster-recovery-dns-traffic-manager
