AZ-204 · Question #218
Case Study 6 - Contoso, Ltd Background Overview You are a developer for Contoso, Ltd. The company has a social networking website that is developed as a Single Page Application (SPA). The main web app
The correct answer is ImagePushed; repository; topic. Explanation: ACR Event Grid YAML Markup This question is about configuring an Azure Event Grid subscription in YAML for Azure Container Registry (ACR) events. Despite the question framing mentioning "Storage access keys," the YAML at line CS17 is for wiring up ACR event notificat
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- ImagePushed
- repository
- topic
Explanation
Explanation: ACR Event Grid YAML Markup
This question is about configuring an Azure Event Grid subscription in YAML for Azure Container Registry (ACR) events. Despite the question framing mentioning "Storage access keys," the YAML at line CS17 is for wiring up ACR event notifications - a common exam mismatch between the stated goal and the actual configuration artifact shown.
The YAML configures what events to listen for when images are pushed to the contosoimages private ACR registry.
Why This Arrangement
Position 1: ImagePushed
What it is: The ACR event type name for when a container image is successfully pushed to the registry.
Why it goes here: Azure Container Registry emits Event Grid events with specific type names. ImagePushed is the canonical event type (Microsoft.ContainerRegistry.ImagePushed) that signals a new image is available. This is the trigger that allows downstream services (like ContentAnalysisService deployment) to react.
Common mistake: Choosing ImageDeployed - this sounds logical but does not exist as an ACR event type. ACR emits ImagePushed and ImageDeleted, not ImageDeployed. RepositoryUpdated is similarly not a real ACR event type.
Position 2: repository
What it is: The Event Grid subject filter scope - scoping event subscriptions to a specific repository path within the registry.
Why it goes here: ACR event subjects follow the pattern /repository/{repositoryName}. The filter must use repository as the subject prefix to correctly scope which events are forwarded. Using image or imageCollection would not match the ACR subject path structure.
Common mistake: Choosing image - while images live inside repositories, the subject path starts with /repository/, so image would not match correctly.
Position 3: topic
What it is: The Event Grid destination/delivery target type.
Why it goes here: Event Grid subscriptions define where events are delivered. A topic is a custom Event Grid topic endpoint used to route events to subscribers (like an Azure Function or webhook). This is the correct sink type for this architecture.
Common mistake: Choosing service or aci - these are not valid Event Grid topic/destination types. aci (Azure Container Instances) is the compute runtime, not an event routing concept.
Summary Table
| Position | Correct Item | Why |
|---|---|---|
| 1 | ImagePushed | Real ACR event type for image push events |
| 2 | repository | Matches ACR subject path format /repository/... |
| 3 | topic | Event Grid delivery destination type |
The core concept tested is knowledge of ACR + Event Grid integration: specifically, the valid event types ACR emits and how Event Grid subscriptions are structured in YAML.
Topics
Community Discussion
No community discussion yet for this question.
