Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An organization is deploying an event-driven serverless solution in Azure to process invoices. The development team needs the application code to execute automatically whenever a new document is uploaded to Azure Blob Storage, without provisioning or maintaining persistent virtual servers.
Which Azure Functions feature should the team configure to initiate code execution in response to this cloud event?
An Azure Functions trigger is an architectural construct that defines how a serverless function is invoked. Triggers monitor specific cloud event sources—such as HTTP webhooks, scheduled timers, message queues, or storage events—and pass relevant payload data to the function code upon execution.
In a serverless environment, applications do not run continuously waiting for input. Instead, the Blob Storage trigger (or an Event Grid event subscription on the container) listens for newly uploaded files. As soon as a document arrives, the platform allocates compute resources dynamically, runs the function, and releases those resources immediately afterward.
A function trigger is the native, purpose-built mechanism in Azure serverless computing for running on-demand code without dedicated server infrastructure.
An Azure Resource Manager (ARM) lock is a governance and security feature applied to Azure subscriptions, resource groups, or individual resources to prevent accidental deletion or unwanted configuration changes.
Resource locks operate purely at the management plane for governance purposes (CanNotDelete or ReadOnly). They have no operational role in application logic, code invocation, or reacting to data changes within storage containers.
The organization needed to protect the Azure Storage account or Function App from being accidentally deleted by administrative users.
An Azure Virtual Machine Scale Set (VMSS) is an Infrastructure as a Service (IaaS) resource management offering that allows administrators to deploy, configure, and automatically scale a pool of identical, load-balanced virtual machines.
Using a Virtual Machine Scale Set represents traditional IaaS cloud computing rather than serverless computing. A VMSS requires managing underlying operating systems, runtime dependencies, patches, and base infrastructure capacity, which directly conflicts with the serverless requirement of running code on-demand without managing servers.
The requirement asked to horizontally scale dedicated IaaS virtual machines based on average CPU utilization or memory metrics.
A deployment slot is an application lifecycle management feature available in hosting environments like Azure App Service and certain Azure Functions plans. Deployment slots allow teams to run different versions of an application (such as staging and production) under distinct hostnames.
Deployment slots do not listen for external cloud events or invoke code execution when files are uploaded. Their role is strictly related to release management, continuous delivery (CI/CD), and validating new application versions prior to swapping them into production.
The organization needed to deploy and test a new version of their serverless function code in a staging environment before swapping it into production without downtime.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated