nerdexam
Amazon

DVA-C02 · Question #104

A company is using an Amazon API Gateway REST API endpoint as a webhook to publish events from an on-premises source control management (SCM) system to Amazon EventBridge. The company has configured a

The correct answer is C. Grant permission to the central AWS account for EventBridge to access the receiver AWS. EventBridge supports cross-account event delivery by granting the central account permission to put events onto receiver account event buses, allowing a single API Gateway webhook to fan out events without any SCM reconfiguration.

Submitted by khalil_dz· Mar 5, 2026Development with AWS Services

Question

A company is using an Amazon API Gateway REST API endpoint as a webhook to publish events from an on-premises source control management (SCM) system to Amazon EventBridge. The company has configured an EventBridge rule to listen for the events and to control application deployment in a central AWS account. The company needs to receive the same events across multiple receiver AWS accounts. How can a developer meet these requirements without changing the configuration of the SCM system?

Options

  • ADeploy the API Gateway REST API to all the required AWS accounts. Use the same custom
  • BDeploy the API Gateway REST API to all the receiver AWS accounts. Create as many SCM
  • CGrant permission to the central AWS account for EventBridge to access the receiver AWS
  • DConvert the API Gateway type from REST API to HTTP API.

How the community answered

(45 responses)
  • A
    4% (2)
  • B
    4% (2)
  • C
    82% (37)
  • D
    9% (4)

Why each option

EventBridge supports cross-account event delivery by granting the central account permission to put events onto receiver account event buses, allowing a single API Gateway webhook to fan out events without any SCM reconfiguration.

ADeploy the API Gateway REST API to all the required AWS accounts. Use the same custom

Deploying API Gateway to all required accounts would require the SCM system to send webhooks to multiple endpoints, directly violating the no-SCM-config-change requirement.

BDeploy the API Gateway REST API to all the receiver AWS accounts. Create as many SCM

Creating multiple SCM webhooks also changes the SCM system configuration, which is explicitly prohibited by the requirements.

CGrant permission to the central AWS account for EventBridge to access the receiver AWSCorrect

By adding a resource-based policy on each receiver account's EventBridge event bus that grants the central account permission to call events:PutEvents, the central account's EventBridge rule can forward incoming SCM events to multiple receiver accounts. This requires no changes to the SCM webhook configuration and leverages native EventBridge cross-account routing.

DConvert the API Gateway type from REST API to HTTP API.

Converting from REST API to HTTP API changes the endpoint URL, which would require SCM reconfiguration and does not solve the multi-account delivery problem.

Concept tested: EventBridge cross-account event bus permissions

Source: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-cross-account.html

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DVA-C02 Practice