[{"_1":2,"_159":-5,"_160":-5},"loaderData",{"_3":4},"routes/topics.$name",[5,24,33,40,50,56,67,77,87,97,108,115,125,131,140,152],{"_6":7,"_8":9,"_10":11,"_12":13,"_17":18,"_20":21,"_22":23},"id","16611a35556548f29f206f155348e08bf5c4193137c9afe8eba16736e0341668","question","Which of the following event schema properties requires a value?","answer","The subject property specifies the publisher-defined path to the event subject and is required. \nEvent Grid will provide Topic. \nA value isn't required for Data","options",[14,15,16],"Topic","Data","Subject","answerIndexes",[19],2,"hasCode",false,"topic","Event Grid",{"_6":25,"_8":26,"_10":27,"_12":28,"_17":31,"_20":21,"_22":23},"6ae5429f60acdd4cbc5b411b0ef29ed9f370f3833fd8b5d730996de412a7f202","Does Event Grid allow Azure Functions to respond to Azure Blob storage events, such as generating thumbnails for newly uploaded images?","It's a valid use case.",[29,30],"Yes","No",[32],0,{"_6":34,"_8":35,"_10":36,"_12":37,"_17":38,"_20":39,"_22":23},"2094ec4d66cafdacf65a5037f57030e7350805f50eefba556f34b752fa2effcc","Fill in \"XXX\" and \"YYY\" for this Event Grid filter:\n\n```jsonc\n{\n \"XXX\": [\n {\n \"operatorType\": \"StringContains\",\n \"key\": \"Subject\",\n \"YYY\": [\"container1\", \"container2\"]\n }\n ]\n}\n```","\n\n```jsonc\n{\n \"advancedFilters\": [\n {\n \"operatorType\": \"StringContains\",\n \"key\": \"Subject\",\n \"values\": [\"container1\", \"container2\"]\n }\n ]\n}\n```",[],[],true,{"_6":41,"_8":42,"_10":43,"_12":44,"_17":49,"_20":21,"_22":23},"b29d783554902563245a494cd139beabddb59b7875b9fc3e5ef9a84298badfe1","You are tasked with creating and deploying an Azure Function App that will handle events from a custom Azure Event Grid topic. To allow subscribers to effectively filter and route these events, which event schema property should you leverage?","Explanation: The `subject` property is used by subscribers to filter and route events when dealing with custom topics in Azure Event Grid. You can include the path where the event occurred in the `subject` property, enabling subscribers to filter events based on segments of that path. This flexibility allows subscribers to filter events either narrowly or broadly.",[45,46,47,48],"`eventTime`","`eventType`","`subject`","`data`",[19],{"_6":51,"_8":52,"_10":53,"_12":54,"_17":55,"_20":39,"_22":23},"9a41b26de9044d5850b7ff7df22fe081907d901b986ddf466e38c8e35eef3002","Configure Azure Event Grid service to send events to an Azure Event Hub instance.\n\n```ps\ntopicName=\"\"\nlocation=\"\"\nresourceGroupName=\"\"\nnamespaceName=\"\"\neventHubName=\"\"\n\n# Code here\n```","\n\n```ps\ntopicName=\"\"\nlocation=\"\"\nresourceGroupName=\"\"\nnamespaceName=\"\"\neventHubName=\"\"\n\naz eventgrid topic create --name $topicName --location $location --resource-group $resourceGroupName\n\n# az eventgrid topic show --name $topicName --resource-group $resourceGroupName --query \"{endpoint:endpoint, primaryKey:primaryKey}\" --output json\n\n# Create a namespace\naz eventhubs namespace create --name $namespaceName --location $location --resource-group $resourceGroupName\n\n# Create an event hub\naz eventhubs eventhub create --name $eventHubName --namespace-name $namespaceName --resource-group $resourceGroupName\n\ntopicId=$(az eventgrid topic show --name $topicName --resource-group $resourceGroupName --query \"id\" --output tsv)\nhubId=$(az eventhubs eventhub show --name $eventHubName --namespace-name $namespaceName --resource-group $resourceGroupName --query \"id\" --output tsv)\n\n# Link the Event Grid Topic to the Event Hub\naz eventgrid event-subscription create \\\n --name \"\" \\\n --source-resource-id $topicId \\\n --endpoint-type eventhub \\\n --endpoint $hubId\n```",[],[],{"_6":57,"_8":58,"_10":59,"_12":60,"_17":65,"_20":21,"_22":23},"22fb1130088bc8e3ff0ccf454f9be066fbfea0c62ce1cb2dea2acd910c81a3de","Which event format can be used to represent events in a standardized way across different cloud providers and platforms?","CloudEvent is a standardized specification designed to provide interoperability across services, platforms, and systems. It can be used across different cloud providers and platforms, unlike EventGridEvent, which is specific to Azure.",[61,62,63,64],"EventGridEvent","CloudEvent","AzureBlobEvent","CustomEvent",[66],1,{"_6":68,"_8":69,"_10":70,"_12":71,"_17":76,"_20":21,"_22":23},"c24c46ee3eeca2a97686df1137336f130400cc34855d5b109d671c5512638d10","You are managing an Azure Blob Storage account that contains multiple containers. One of these containers is critical and stores time-sensitive data. You need to set up an alerting mechanism to receive messages whenever objects are added to this specific container. To receive messages specifically when objects are added to a particular container in Azure Blob Storage, which Event Grid option should you configure?","By using \"Subject begins with or ends with,\" you can precisely target events related to the specific container in Azure Blob Storage, ensuring that you receive messages only when objects are added to that container. This allows for targeted alerting and monitoring.",[72,73,74,75],"Subject begins with or ends with","Advanced fields and operators","ResourceType","EventType",[32],{"_6":78,"_8":79,"_10":80,"_12":81,"_17":86,"_20":21,"_22":23},"354b603c5632dc47ee6f4a933b9683e2d8122c4d24a2b3a4118c66f91480d03d","What command you need to run to enable your Azure subscription to send events to Event Grid?","It will take some minutes. You need to run this only once per subscription.",[82,83,84,85],"`az provider register --namespace Microsoft.EventGrid`","`az group create --name Microsoft.EventGrid`","`az eventgrid topic create --name \"ServiceBus, BlobStorage\"`","`az subscription --enable Microsoft.EventGrid`",[32],{"_6":88,"_8":89,"_10":90,"_12":91,"_17":96,"_20":21,"_22":23},"52bd99e99d1ac5c5a5d828d680c86d928f3960c83649ea382a35eddad849700d","What is the minimum number of subscribers a publisher in Event Grid must have?","Publishers emit events, but have no expectation about how the events are handled.",[92,93,94,95],"0","1","3","5",[32],{"_6":98,"_8":99,"_10":100,"_12":101,"_17":107,"_20":21,"_22":23},"b4f375e05a9abd5318b7c5095c9bea56359b15873eef21487a8d9ed0539eccce","What best describes the optimistic batching behavior in Azure Event Grid?","Optimistic batching results in smaller batch sizes at low event rates. \nEvent Grid works on _All-or-None_ policy, no partial delivery allowed when batching. \nIt's not necessary to specify both the settings (Maximum events per batch and Approximate batch size in kilobytes).",[102,103,104,105,106],"Optimistic batching ensures that the batch size is always equal to the requested maximum events per batch.","Optimistic batching respects policy settings on a best-effort basis, often leading to smaller batch sizes at low event rates.","Optimistic batching operates with flexible semantics, allowing partial success of a batch delivery.","Optimistic batching is responsible for handling events that cannot be delivered to the endpoint.","Optimistic batching requires both the Maximum events per batch and Approximate batch size in kilobytes to be specified.",[66],{"_6":109,"_8":110,"_10":111,"_12":112,"_17":113,"_20":21,"_22":23},"2aaa98c0a63cff6323a40d5ade43fe4b7189df7a3c265f1e7c524206b3f5dab0","You are responsible for monitoring various Azure resources in your organization. You want to set up an Azure Event Grid subscription to specifically receive only failure messages for any type of resource. Which of the following options should you configure in your Event Grid subscription to achieve this?","In Azure Event Grid, you can configure your subscription to filter events based on `EventType`. This allows you to specifically receive failure messages for any type of Azure resource. By setting up your Event Grid subscription to only pass along events of a certain type, such as failure messages, you can effectively monitor the health of various resources in your organization.",[72,73,74,75],[114],3,{"_6":116,"_8":117,"_10":118,"_12":119,"_17":124,"_20":21,"_22":23},"ca5e6266a5dad4029095f66bba19e01447e2b744df1a35cdb00797701ceba6b0","You need to enable a third-party SaaS application to send events directly to your Azure subscription for processing by your custom applications. What type of Event Grid topic should you configure to achieve this?","Partner Topics are designed specifically for enabling third-party services or SaaS applications to push events into your Azure subscription. These events can then be processed by Azure Functions, Logic Apps, or other subscribers to the topic. \nSystem Topic: This is for Azure services that natively emit events, like Blob Storage or Event Hubs. You use system topics when you’re dealing with Azure-native resources. \nCustom topics are for your own applications to send events into Event Grid—not for third-party SaaS. If the source isn’t a partner but something you built, this would be the choice. \nEvent Hub Topic: Event Hub isn’t even part of Event Grid’s topic system. It’s used for high-throughput streaming of telemetry or event data, not the discrete events Event Grid handles.",[120,121,122,123],"System Topic","Partner Topic","Custom Topic","Event Hub Topic",[66],{"_6":126,"_8":127,"_10":128,"_12":129,"_17":130,"_20":21,"_22":23},"80d1a2460079c5231f7dc6bad899df33a89a2d5ca81cdc5657edb906497aeabb","You manage Azure Virtual Machines, SQL Databases, and Blob Storage. Each resource type requires a unique action when an event occurs: VMs need restarting, SQL Databases need backups, and Blob Storage needs old log deletion. To route events to specific actions based on the Azure resource involved, which Event Grid option should you configure?","By using `ResourceTypes`, you can ensure that each type of resource triggers its corresponding action, allowing for targeted and efficient automated responses.",[72,73,74,75],[19],{"_6":132,"_8":133,"_10":134,"_12":135,"_17":139,"_20":21,"_22":23},"05a5a6bb3aab25977b6657599034cfcde3635d6d03594904c435e033c34fe7d9","Which of the following Event Grid built-in roles is appropriate for managing Event Grid resources?","The Event Grid Contributor role has permissions to manage resources. \nThe Event Grid Subscription Contributor role has permissions to manage subscription operations. \nThe Event Grid Data Sender role has permissions to send events to topics.",[136,137,138],"Event Grid Contributor","Event Grid Subscription Contributor","Event Grid Data Sender",[32],{"_6":141,"_8":142,"_10":143,"_12":144,"_17":150,"_20":21,"_22":23},"e7df6a2171af1babfe82a5d8b2a55986c6616e490619c77060291cde8ffbd747","You are trying to send a 130KB event from Event Hub to Event Grid. Which of the following statements are true:","Only events up to 64KB are covered by SLA. \n`lastTimeModified` is a property for Azure Storage. \n`413 Payload Too Large` happens only for events over 1MB. \nMath.roof(130 / 64) = 3",[145,146,147,148,149],"Event is covered by the Service Level Agreement (SLA)","Event contains `lastTimeModified` property","Event contains Capture file URL property","You'll receive `413 Payload Too Large` error","You be charged for 3 separate events",[19,151],4,{"_6":153,"_8":154,"_10":155,"_12":156,"_17":158,"_20":21,"_22":23},"f61f20cdb52d8834e4600f6ee7bec58b24d11020e8bfa0a65a3408b8de28b54e","If you are working specifically within the Azure ecosystem and want to take advantage of Azure-specific features, which event format would you likely use?","EventGridEvent is specific to Azure Event Grid and is designed to work seamlessly with Azure services. It includes additional features specific to Azure, like support for Event Domains, making it the suitable choice for Azure-specific implementations. CloudEvent, on the other hand, is a more generalized standard and doesn't include Azure-specific features.",[64,62,61,157],"AzureQueueEvent",[19],"actionData","errors"]

AZ-204 Quiz

← Back to Topics