Microsoft Azure Architect Design (AZ-304) Practice Test

Disable ads (and more) with a membership for a one time $2.99 payment

Study for the Microsoft Azure Architect Design AZ-304 Test with comprehensive quizzes and multiple-choice questions. Each question comes with detailed explanations to help you grasp key concepts. Prepare effectively and boost your chances of success!

Practice this question and more.


For a message application that requires daily queue creation and deletion with scheduled uploads every five minutes, which should be used?

  1. Azure CLI

  2. AzCopy

  3. Azure Data Factory

  4. .NET Core

The correct answer is: .NET Core

Using .NET Core for the described scenario is a suitable choice due to its versatility and capabilities in managing queue operations programmatically. The message application requires creating and deleting queues on a daily basis, which can be efficiently handled through a .NET Core application that utilizes the Azure SDKs. The SDK provides robust libraries for interacting with Azure services, allowing the application to automate queue creation, management, and scheduled uploads seamlessly. Additionally, .NET Core can leverage timers and background services to handle the frequent uploads every five minutes, making it a strong candidate for a solution that requires custom logic, error handling, and comprehensive control over the entire message processing workflow. Other options do have their specific uses; for instance, Azure CLI is more suited for interactive command-line operations rather than ongoing automated tasks. AzCopy is designed specifically for high-performance data transfer, not for queue management or automated processing. Azure Data Factory is primarily a data integration and orchestration tool, which, while powerful for moving data between systems, may not be the best fit for a rapid, message-oriented task that involves frequent queue management and scheduled operations. Thus, .NET Core emerges as the most appropriate choice for this messaging application scenario.