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

Question

Case Study 10 - Fourth Coffee Background Fourth Coffee is a global coffeehouse chain and coffee company recognized as one of the world's most influential coffee brands. The company is renowned for its specialty coffee beverages, including a wide range of espresso-based drinks, teas, and other beverages. Fourth Coffee operates thousands of stores worldwide. Current environment The company is developing cloud-native applications hosted in Azure. Corporate website to place orders as well as view and update inventory items. Inventory items In addition to its core coffee offerings, Fourth Coffee recently expanded its menu to include inventory items such as lunch items, snacks, and merchandise. Corporate team members constantly update inventory. Users can customize items. Corporate team members configure inventory items and associated images on the website. Orders Associates in the store serve customized beverages and items to customers. Orders are placed on the website for pickup. The application components process data as follows: 1. Azure Traffic Manager routes a user order request to the corporate website hosted in Azure App Service. 2. Azure Content Delivery Network serves static images and content to the user. 3. The user signs in to the application through a Microsoft Entra ID for customers tenant. 4. Users search for items and place an order on the website as item images are pulled from Azure Blob Storage. 5. Item customizations are placed in an Azure Service Bus queue message. 6. Azure Functions processes item customizations and saves the customized items to Azure Cosmos DB. 7. The website saves order details to Azure SQL Database. 8. SQL Database query results are cached in Azure Cache for Redis to improve performance. The application consists of the following Azure services: Requirements The application components must meet the following requirements: - Azure Cosmos DB development must use a native API that receives the latest updates and stores data in a document format. - Costs must be minimized for all Azure services. - Developers must test Azure Blob Storage integrations locally before deployment to Azure. Testing must support the latest versions of the Azure Storage APIs. Corporate website - User authentication and authorization must allow one-time passcode sign-in methods and social identity providers (Google or Facebook). - Static web content must be stored closest to end users to reduce network latency. Inventory items - Customized items read from Azure Cosmos DB must maximize throughput while ensuring data is accurate for the current user on the website. - Processing of inventory item updates must automatically scale and enable updates across an entire Azure Cosmos DB container. - Inventory items must be processed in the order they were placed in the queue. - Inventory item images must be stored as JPEG files in their native format to include exchangeable image file format (data) stored with the blob data upon upload of the image file. - The Inventory Items API must securely access the Azure Cosmos DB data. Orders - Orders must receive inventory item changes automatically after inventory items are updated or saved. Issues - Developers are storing the Azure Cosmos DB credentials in an insecure clear text manner within the Inventory Items API code. - Production Azure Cache for Redis maintenance has negatively affected application performance. You need to mitigate the Azure Cache for Redis issue. What are two possible ways to achieve this goal? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

Options

• ATest application code by rebooting all nodes in the test environment.
• BConfigure client connections to retry commands with exponential backoff.
• CModify the maxmemory policy to evict the least frequently used keys out of all keys.
• DIncrease the maxmemory-reserved and maxfragmentationmemory-reserved values.
• ETest application code by purging the cache in the test environment.

Explanation

If your Azure Cache for Redis underwent a failover, all client connections from the node that went down are transferred to the node that is still running. The server load could spike because of the increased connections. You can try rebooting your client applications so that all the client connections get recreated and redistributed among the two nodes. https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-troubleshoot-server

No community discussion yet for this question.