APIGEE-API-ENGINEER practice question 21 of 25

When using a Shared Flow from a Flow Hook, which proxies will call the Shared Flow?

Full set: 126 questions
Answer options
A: All proxies in the environment where the Flow Hook is configured Correct answer
B: Only proxies that contain a Flow Callout policy
C: All proxies within an Organization
D: Only proxies with the Flow Hook checkbox checked
Correct Answer:
A. All proxies in the environment where the Flow Hook is configured
Explanation

A Flow Hook is a mechanism in Apigee for attaching a Shared Flow to a specific point in the request/response lifecycle (e.g., Pre-proxy, Post-target) for an entire environment. When a Shared Flow is attached to a Flow Hook, the Apigee runtime automatically executes that Shared Flow for every API proxy deployed within that specific environment. This ensures that a consistent set of logic, such as for security or logging, is applied uniformly across all APIs in the environment without needing to modify each proxy's individual code.

Why Incorrect

B. This is incorrect. A Flow Callout policy is an alternative method to invoke a Shared Flow from within a specific proxy's logic. Flow Hooks operate at the environment level and do not require a Flow Callout policy in the proxy.
C. This is incorrect. Flow Hooks are configured on a per-environment basis (e.g., dev, test, prod), not for an entire organization. A Shared Flow attached in one environment will not affect proxies in another.
D. This is incorrect. There is no "Flow Hook checkbox" on individual API proxies. The association is made at the environment level, and it applies to all proxies deployed to that environment automatically.

References

1. Google Cloud Apigee Documentation

"Attaching a shared flow with a flow hook":

"A flow hook lets you attach a shared flow... When you do this

the attached shared flow executes for every API proxy deployed in the environment associated with the flow hook." This statement directly supports answer A.

"This gives you a separately implemented and deployed sequence of logic that is not part of a proxy's implementation code." This clarifies that a Flow Callout policy (part of the proxy's code) is not involved

refuting option B.

2. Google Cloud Apigee Documentation

"Shared flows":

Under the section "Using a shared flow

" the documentation explicitly lists two distinct methods: "Attached to a flow hook" and "Called from an API proxy with a FlowCallout policy." This separation confirms that one method does not depend on the other

making option B incorrect.

Scroll to Top