AZ-204 Question #435: Real Exam Question with Answer & Explanation

Question

Case Study 8 - VanArsdel, Ltd Background VanArsdel, Ltd. is a global office supply company. The company is based in Canada and has retail store locations across the world. The company is developing several cloud-based solutions to support their stores, distributors, suppliers, and delivery services. Current environment Corporate website consists of a React JavaScript user interface, HTML, CSS, image assets, and several APIs hosted in Azure Functions. Retail Store Locations The company supports thousands of store locations globally. Store locations send data every hour to an Azure Blob storage account to support inventory, purchasing and delivery services. Each record includes a location identifier and sales transaction information. Requirements The application components must meet the following requirements: Corporate website - Secure the website by using SSL. - Minimize costs for data storage and hosting. - Implement native GitHub workflows for continuous integration and continuous deployment (CI/CD). - Distribute the website content globally for local use. - Implement monitoring by using Application Insights and availability web tests including SSL certificate validity and custom header value verification. - The website must have 99.95 percent uptime. Retail store locations - Azure Functions must process data immediately when data is uploaded to Blob storage. Azure Functions must update Azure Cosmos DB by using native SQL language queries. - Audit store sale transaction information nightly to validate data, process sales financials, and reconcile inventory. Delivery services - Store service telemetry data in Azure Cosmos DB by using an Azure Function. Data must include an item id, the delivery vehicle license plate, vehicle package capacity, and current vehicle location coordinates. - Store delivery driver profile information in Azure Active Directory (Azure AD) by using an Azure Function called from the corporate website. Inventory services The company has contracted a third-party to develop an API for inventory processing that requires access to a specific blob within the retail store storage account for three months to include read-only access to the data. Security - All Azure Functions must centralize management and distribution of configuration data for different environments and geographies, encrypted by using a company-provided RSA-HSM key. - Authentication and authorization must use Azure AD and services must use managed identities where possible. Issues Retail Store Locations - You must perform a point-in-time restoration of the retail store location data due to an unexpected and accidental deletion of data. - Azure Cosmos DB queries from the Azure Function exhibit high Request Unit (RU) usage and contain multiple, complex queries that exhibit high point read latency for large items as the function app is scaling. Question You need to reduce read latency for the retail store solution. What are two possible ways to achieve the goal? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

Options

• ACreate a new composite index for the store location data queries in Azure Cosmos DB.
• BProvision an Azure Cosmos DB dedicated gateway.
• CConfigure Azure Cosmos DB consistency to session consistency.
• DProvision an Azure Cosmos DB dedicated gateway.
• EConfigure Azure Cosmos DB consistency to strong consistency.

Explanation

Azure Cosmos DB queries from the Azure Function exhibit high Request Unit (RU) usage and contain multiple, complex queries that exhibit high point read latency for large items as the function app is scaling. B: A dedicated gateway is server-side compute that is a front-end to your Azure Cosmos DB account. When you connect to the dedicated gateway, it both routes requests and caches data. You can provision a dedicated gateway to improve performance at scale. You must connect to Azure Cosmos DB using the dedicated gateway in order to use the integrated cache. The dedicated gateway has a different endpoint from the standard one provided with your Azure Cosmos DB account. When you connect to your dedicated gateway endpoint, your application sends a request to the dedicated gateway, which then routes the request to different backend nodes. If possible, the integrated cache will serve the result. C: Azure Cache for Redis perfectly complements Azure database services such as Cosmos DB. It provides a cost-effective solution to scale read and write throughput of your data tier. Store and share database query results, session states, static contents, and more using a common cache- https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/data-cache-with-redis- https://docs.microsoft.com/en-us/azure/cosmos-db/dedicated-gateway

No community discussion yet for this question.