Free Google Apigee-API-Engineer Actual Exam Questions - Question 14 Discussion

C. Conditional flows are definitely supported because Edge Microgateway proxies need flexibility in routing. The other options mention must-haves that don’t seem like strict requirements.

It’s C for me as well. The key thing is that Edge Microgateway-aware proxies handle conditional flows, which is a core feature. Looking at A and D, neither Node.js targets nor HTTPTargetConnection are hard requirements—they can work with other backends or target types. As for B, quota and OAuth2 policies are useful but definitely not mandatory for every proxy. So C stands out as the only statement that’s always true.

Good point about the mandatory angle—thinking about it, A doesn’t seem right because Edge Microgateway proxies aren’t limited to Node.js targets; they can work with other backend types too. B also feels off since quota or OAuth2 policies aren’t a hard requirement for these proxies. That pretty much leaves C as the only solid choice since conditional flows are definitely supported and key for managing traffic logic in Edge Microgateway proxies.

I’m not sure B makes sense since quota or OAuth2 policies aren’t strictly required for all Edge Microgateway proxies. They can run with other policy types too. Wouldn’t that rule it out?

Guessing A here. Since Microgateway is designed to run policies locally, it probably needs proxies to point to Node.js script targets to execute those policies effectively. That fits better than the others.

Maybe C makes sense since conditional flows add flexibility in routing and processing, which fits with Microgateway’s lightweight nature. D could be too strict; I think other target types might be used sometimes.

It’s D. Edge Microgateway-aware proxies typically require HTTPTargetConnection because they often connect directly to backend HTTP services rather than specialized targets like Node.js scripts. A doesn’t hold since Node.js script target isn’t a must, and B sounds optional rather than mandatory. C is true in general, but I think D is more of a hard requirement for these proxies to function properly.

Option A feels off since Microgateway proxies don’t have to point to Node.js script targets.

B/C? I’m getting mixed signals here. Microgateway-aware proxies are known for some policy support like OAuth2 or quota, so B seems plausible. But I also recall something about conditional flows being supported, which points to C. A and D sound more strict than what I remember-Node js script target and HTTP target connections as musts? Not sure about that. Anyone cracked this one for sure?