Q99 — AWS DVA-C02 Ch.3

Question 99 of 100 | ← Chapter 3

A company is using an Amazon API Gateway REST API endpoint as a webhook to publish commits from its on-premises source code management (SCM) system to Amazon EventBridge. The company has configured an EventBridge rule in a central AWS account to listen for application deployments from the SCM system. The company needs to deliver commits to multiple receiving AWS accounts. How can developers meet these requirements without changing the SCM system configuration?

• A. Deploy the API Gateway REST API to all required AWS accounts. Use the same custom domain name for all gateway endpoints so that a single SCM webhook can be used for events from all accounts.
• B. Deploy the API Gateway REST API to all receiving AWS accounts. Create as many SCM webhooks as there are AWS accounts.
• C. Grant the central AWS account's EventBridge permission to access the receiving AWS accounts. Add EventBridge event buses in the receiving AWS accounts as targets to the existing EventBridge rule. ✓
• D. Convert the API Gateway type from REST API to HTTP API.

Correct Answer: C. Grant the central AWS account's EventBridge permission to access the receiving AWS accounts. Add EventBridge event buses in the receiving AWS accounts as targets to the existing EventBridge rule.

Explanation

In this scenario, events must be delivered from the SCM system to EventBridge and then routed across multiple receiving AWS accounts without modifying the SCM configuration. Option A deploys API Gateway to all accounts and uses a shared custom domain, but it does not address cross-account event delivery without SCM changes. Option B requires creating multiple SCM webhooks, violating the 'no SCM configuration change' requirement. Option C enables the central account’s EventBridge rule to forward events to event buses in other accounts via cross-account permissions—meeting the requirement without altering SCM. Option D is irrelevant to the requirement. Therefore, the correct answer is C.