Which Azure compute solution fits each of the three projects?
HOTSPOT
You have the following projects:
• Project1: The development of an app that processes scanned images stored in an Azure Blob Storage account
• Project2: The migration of an on-premises app that processes log files as they arrive in an SMB file share
• Project3: The migration of an on-premises app that processes PDF documents stored on a local file system
The projects have the requirements shown in the following table.
Project3 does NOT support the use of containers.
You need to recommend a compute solution for the projects.
What should you include in the recommendation for each project? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Community Insight
The item tests whether you can read workload shape (massively parallel HPC vs event-driven vs legacy lift-and-shift) and platform constraints before naming a service; the trap is defaulting every workload to Azure Functions or pushing the no-containers app onto AKS or Container Instances.
This hotspot asks you to map three workloads — scanned-image batch processing, log files arriving in an SMB share, and a legacy PDF app — to the right Azure compute service. The page establishes that Project1 takes Azure Batch, Project2 takes Azure Functions, and Project3 takes Azure Virtual Machines because it cannot be containerized.
The most common wrong approach is treating Azure Functions as a universal answer and assigning it to the image-processing project, or choosing Azure Kubernetes Service / Azure Container Instances for the on-premises PDF application that the question explicitly says does not support containers.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Project1 develops an app that processes scanned images already stored in Azure Blob Storage, and its requirement profile is large-scale, parallel, dynamically scaled computation — exactly the Azure Batch model, where a job spins up a pool of compute nodes that auto-scales with the number of tasks. Project2 migrates an on-premises app whose input arrives as files land in an SMB file share; that is a classic event-shaped, bursty, low-administration workload, which is what a serverless Azure Functions app is designed for. Project3 migrates a legacy application that works against a local file system and explicitly does not support containers, so only an IaaS Azure Virtual Machine preserves OS-level and file-system behaviour without repackaging the app. Together the three selections follow AZ-305 compute doctrine: HPC/parallel → Azure Batch, event-driven → Azure Functions, legacy non-containerizable → Azure Virtual Machines.
Why Other Candidate Answers Are Wrong
Azure Functions is the wrong shape for Project1: its consumption model targets short, event-triggered executions, not thousands of parallel, long-running image-processing tasks that need dedicated node pools and job scheduling. Azure Kubernetes Service, Azure Container Instances, and container-based App Service plans are all eliminated for Project3 by the explicit "Project3 does NOT support the use of containers" constraint, no matter how good their scaling story looks. Hosting Project2 on a virtual machine or a Batch pool would technically run, but it forces OS patching, capacity planning, and idle-cost management for a file-arrival workload, which contradicts the low-administration intent of a migration scenario. Conversely, picking a PaaS or serverless target for Project3 fails because the legacy app depends on local file system semantics and cannot be repackaged.
Community Comment Notes
As gpais explains for the first project, the decisive driver is "the requirement for High-Performance Computing (HPC) combined with dynamic scaling" and concludes that Azure Batch is "specifically built to run large-scale parallel and high-performance computing applications" — which matches the verdict given here. The same comment continues that Project2's requirements are addressed by Azure Functions, i.e. the file-arrival trigger rather than a VM-based host. No commenter proposed a container platform for Project3, consistent with the no-containers constraint stated in the question stem. Since only one comment is visible and it is truncated, treat it as supporting evidence rather than the source of the answer — the service mapping is derived from the workload requirements themselves.
Official Reference
Exam Strategy
Read the requirements table row by row and extract three signals per project: what triggers the work, how it must scale, and any platform restriction. Eliminate container-based options for the project that forbids containers first, then match the remaining projects to Azure Batch (parallel HPC) and Azure Functions (event-driven, minimal administration).
Frequently Asked Questions
Why is Azure Batch recommended for Project1 instead of Azure Functions?
The image workload needs massively parallel, dynamically scaled HPC processing, which is Azure Batch's core design; Functions targets short event-driven executions instead.
Why can't Project3's PDF application run on Azure Container Instances or AKS?
The question states Project3 does not support containers, so it must be lifted and shifted onto an Azure Virtual Machine that preserves OS and local file system behaviour.
Related Analysis
Practice All AZ-305 Questions
Access 95 questions with complete answers and detailed explanations.
View Full AZ-305 Practice Test →