APIGEE-API-ENGINEER practice question 14 of 25
Which of the following statements are the for Edge Microgateway-aware proxies?
Full set: 126 questionsEdge 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.
Keep practicing
Take the free APIGEE-API-ENGINEER practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other APIGEE-API-ENGINEER practice questions
- Question 1In your last release, there were unexpected errors uncovered by users within the first 24…
- Question 2Your company runs their internal services across two datacenters in a hot-warm configurat…
- Question 3Which features are supported in the OAulhV2 policy'? Select all that are correct. Choose …
- Question 4Which is a benefit of three-legged OAuth (authonzation_code grant)'?
- Question 5Which Apigee product feature can be used to host and version your API documentation'?
- Question 6As an API Engineer your team would like to make sure you are simulating a user experience…
