Edge Microgateway-aware proxies are standard Apigee proxies that serve as a configuration source for a Microgateway instance. A key feature of Apigee proxies is the ability to use conditional flows to apply logic and policies to specific request paths, verbs, or other conditions. This feature is fully supported for microgateway-aware proxies. It allows developers to define granular enforcement rules, such as applying a stricter quota policy to a write operation (POST /resource) and a more lenient one to a read operation (GET /resource) within the same proxy, which Microgateway will then download and enforce locally.

A. Edge Microgateway-aware proxies must point to a Node js ScnptTarget

This is incorrect. Microgateway-aware proxies often have no target at all (a "no target" proxy) because their primary purpose is to bundle policies for Microgateway, not to route traffic.

B. Edge Microgateway-aware proxies should at least contain a quota or OAuth2 policy

This is not a requirement. A microgateway-aware proxy could validly contain only a Spike Arrest policy or just be used for API key validation without other specific policies.

D. Edge Microgateway-aware proxies must use HTTPTargetConnection in the TargetEndpoint

This is incorrect. As these proxies are not primarily for routing traffic to a backend, they typically do not use an HTTPTargetConnection. A "no target" configuration is common.

---

1. Google Cloud

Apigee Documentation

"Operations and flows": This document explicitly states

"You can attach policies to flows in the microgateway-aware proxy

giving you the ability to apply fine-grained policy enforcement on a per-resource basis." It provides a clear XML example of a conditional flow () being used in a microgateway-aware proxy. This directly supports option C.

2. Google Cloud

Apigee Documentation

"Set up and configure Edge Microgateway"

Step 3: Create a microgateway-aware proxy: This tutorial section notes

"The proxy can be a simple 'no target' proxy... The proxy's TargetEndpoint must be configured with a element

but it does not have to resolve to a real target..." This confirms that a specific

functional HTTPTargetConnection or ScriptTarget is not required

invalidating options A and D.

3. Google Cloud

Apigee Documentation

"What is Edge Microgateway?": Under the section "What policies are enforced by Edge Microgateway?"

the documentation lists Spike Arrest

Quota

OAuth v2

and Verify API Key. It does not state that a proxy must contain a Quota or OAuth2 policy

invalidating the strict requirement implied in option B.