Question 690
At fictional Juniper Creek Transit, a software-security team is conducting a security incident follow-up assessment without placing confidential information in build artifacts. The case observation is: An event consumer running in a shared cluster can subscribe to every tenant's order topics because the broker uses a wildcard permission. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?
Explanation
Writer-proposed answer: B (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
Messaging infrastructure must enforce least-privilege event distribution at the broker boundary. A consumer for tenant A cannot read tenant B topics even when connecting from the same cluster.
Incorrect Answers
This response concerns idempotent payment api design. Here, an event consumer running in a shared cluster can subscribe to every tenant's order topics because the broker uses a wildcard permission. The confirming evidence is: A consumer for tenant A cannot read tenant B topics even when connecting from the same cluster.
Focusing on api gateway authentication mismatch would leave this problem unresolved: An event consumer running in a shared cluster can subscribe to every tenant's order topics because the broker uses a wildcard permission.
Cross-origin policy misconfiguration concerns another aspect of the problem. Messaging infrastructure must enforce least-privilege event distribution at the broker boundary.