nerdexam
Microsoft

AZ-204 · Question #519

You are developing several microservices to run on Azure Container Apps for a company. External TCP ingress traffic from the internet has been enabled for the microservices. The company requires that

The correct answer is A. metadata B. type. When configuring a custom scaling rule for Azure Container Apps using KEDA with an Azure Event Hub trigger, the type and metadata fields are essential to define the event source and its specific configuration.

Submitted by fernanda_arg· Mar 30, 2026Develop Azure compute solutions

Question

You are developing several microservices to run on Azure Container Apps for a company. External TCP ingress traffic from the internet has been enabled for the microservices. The company requires that the microservices must scale based on an Azure Event Hub trigger. You need to scale the microservices by using a custom scaling rule. Which two Kubernetes Event-driven Autoscaling (KEDA) trigger fields should you use? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

Options

  • Ametadata
  • Btype
  • CauthenticationRef
  • Dname
  • EmetricType

How the community answered

(23 responses)
  • A
    83% (19)
  • C
    4% (1)
  • D
    4% (1)
  • E
    9% (2)

Why each option

When configuring a custom scaling rule for Azure Container Apps using KEDA with an Azure Event Hub trigger, the `type` and `metadata` fields are essential to define the event source and its specific configuration.

AmetadataCorrect

The `metadata` field is a collection of key-value pairs that provides the specific configuration details for the chosen KEDA scaler, such as `connectionStringSetting`, `consumerGroup`, and `eventHubName` for an Azure Event Hub trigger.

BtypeCorrect

The `type` field specifies the event source for the KEDA scaler (e.g., 'azure-eventhub'), which tells KEDA which specific scaler to use to monitor and react to events.

CauthenticationRef

The `authenticationRef` field is used to refer to an external `TriggerAuthentication` object for authentication, but it is optional and not as fundamental as `type` and `metadata` for defining the core scaling logic.

Dname

The `name` field is an optional identifier for the trigger and does not affect its functionality for scaling based on the event source.

EmetricType

The `metricType` field is typically associated with Horizontal Pod Autoscaler (HPA) metrics or specific KEDA scalers for interpreting metric values, but it's not a general top-level field for defining the event source itself in KEDA triggers.

Concept tested: KEDA trigger configuration for Azure Event Hub

Source: https://keda.sh/docs/2.12/scalers/azure-event-hub/

Topics

#Container Apps scaling#KEDA#Event Hub trigger#custom scaling rules

Community Discussion

No community discussion yet for this question.

Full AZ-204 Practice