Azure Developer Associate exam questions fully solved & updated 2024

Microsoft Graph Events(trigger): Starts a function in response to an incoming webhook from the Microsoft Graph. Each instance of this trigger can react to one Microsoft Graph resource type. 4 levels of organizing structure in Azure(top to bottom): 1) Management groups 2) Subscriptions 3) Resource groups 4) Resources Resources: Resources are instances of services that you create, like virtual machines, storage, or SQL databases. Resource groups: Resources are combined into resource groups, which act as a logical container into which Azure resources like web apps, databases, and storage accounts are deployed and managed. Subscriptions: A subscription groups together user accounts and the resources that have been created by those user accounts. For each subscription, there are limits or quotas on the amount of resources that you can create and use. Organizations can use subscriptions to manage costs and the resources that are created by users, teams, or projects. Management groups: These groups help you manage access, policy, and compliance for multiple subscriptions. All subscriptions in a management group automatically inherit the conditions applied to the management group. The two types of subscription boundaries are: 1) Billing boundary 2) Access control boundary Billing boundary: This subscription type determines how an Azure account is billed for using Azure. You can create multiple subscriptions for different types of billing requirements. Azure generates separate billing reports and invoices for each subscription so that you can organize and manage costs. Access control boundary: Azure applies access-management policies at the subscription level, and you can create separate subscriptions to reflect different organizational structures. An example is that within a business, you have different departments to which you apply distinct Azure subscription policies. This billing model allows you to manage and control access to the resources that users provision with specific subscriptions. you might choose to create additional subscriptions to separate: 1) Environments (for coding, testing, dev etc) 2) Organizational structures 3) Billing role-based access control (RBAC) Availability zones: physically separate datacenters within an Azure region. isolation boundary: If one zone(datacenter) goes down, the other continues working Zonal services: You pin the resource to a specific zone (for example, VMs, managed disks, IP addresses). Zone-redundant services: The platform replicates automatically across zones (for example, zone-redundant storage, SQL Database). region pair: Each Azure region is always paired with another region within the same geography, This approach allows for the replication of resources Which of the following statements is a valid statement about an Azure subscription? -Using Azure doesn't require a subscription. -An Azure subscription is a logical unit of Azure services. -You can't have more than one subscription. An Azure subscription is a logical unit of Azure services. Which of the following features doesn't apply to resource groups? -Resources can be in only one resource group. -Role-based access control can be applied to the resource group. -Resource groups can be nested. Resource groups can be nested. Which of the following is a logical unit of Azure services that links to an Azure account? Azure subscription Management group Resource group Azure subscription 1. Which of the following can be used to manage governance across multiple Azure subscriptions? Azure initiatives Management groups Resource groups Management groups Serverless compute: Like FaaS or function as a service Stateless logic: state of variables does not exceed the scope of a function drawback of a serverless compute solution: 1) Execution time: By default, functions have a timeout of 5 minutes. This timeout is configurable to a maximum of 10 minutes. 2) Execution frequency: if your function is executed a lot it might be cheaper to host your service on a VM. Consumption service plan: automatic scaling and bills you when your functions are running. Azure App Service plan: allows you to avoid timeout periods by having your function run continuously on a VM that you define. Blob storage(trigger): Starts a function when a new or updated blob is detected. Azure Cosmos DB(trigger): Start a function when inserts and updates are detected. Event Grid(trigger): Starts a function when an event is received from Event Grid. HTTP(trigger): Starts a function with an HTTP request. Queue storage(trigger): Starts a function when a new item is received on a queue. The queue message is provided as input to the function. Service Bus(trigger): Starts a function in response to messages from a Service Bus queue. Timer(trigger): Starts a function on a schedule. Bindings: a declarative way to connect data and services to your function. Function app: A function app is a way to organize and collectively manage your functions. A function app is comprised of one or more individual functions that are managed together by Azure App Service. All the functions in a function app share the same pricing plan, continuous deployment, and runtime version. We secured our function against unknown HTTP callers by requiring a function-specific API key be passed with each call. Which of the following fields is the name header in the HTTP requests that needs to contain this key?: x-functions-key x-requested-with x-csrf-token x-functions-key two kinds of bindings: 1) input binding 2) output binding Input binding: An input binding is a connection to a data source. Our function can read data from these inputs.