Apigee-API-Engineer Google Cloud - Apigee Certified API Engineer Question and Answers

distributed, non-synchronous

non-distributed, synchronous

distnbuted, synchronous

non-distnbuted, non-synchronous

use a concurrent rate limiting policy

use a LoadBalancer entry in the HTTPTargelConnection session

use RouteRules with multiple TargetEndpoints

use an AssignMessage policy

Only the first matching flow from the top runs

Only the first matching flow from the bottom runs.

All matching flows run. in order from the top to the bottom.

A fault is raised and this should be handled in the FaultRules.

Create a new API proxy for new customers and invoke backend target system with required parameters.

Configure the API as a pass-through proxy and invoke backend target system with client request parameters.

Create a new proxy xml and base path with upgraded version and invoke backend target system with required parameters

Include a new customer requirement in an existing API proxy and invoke backend target system with required parameters.

PostClientFlow will only be executed if a payload is returned.

The response is blocked until! the PostClientFlow policies are executed.

PostClientFlow can only include MessageLogging policies.

PostClientFlow can include any supported policy.

response millis and connect.millis

target.timeout and proxy timeout

connect.timeout.millis and io.timeoutmillis

connect timeout and network timeout

the request content in the request flow

the response content in the response flow

the request content when in the request flow and the response content when in the response flow

neither the request content nor the response content

Modify the RouteRuies to be more specific.

Create a new proxy for this special condition.

Reorder the RouteRuies so that your condition is found

Add a new TargetServer to handle your specific condition

Storing of external access tokens

Setting custom attributes for generated access tokens

Credentials validation when password grant_type is used

Setting different expiration for refresh and access tokens

Regular Expression Protection policy

Basic Authentication policy

Access Control policy

Raise Fault policy

Authenticate users.

Authenticate applications

Log update events to StackDriver

Enforce quotas based on Product configurations

Alert when total API latency exceeds 500 milliseconds

You should deploy an Apigee microgateway

Management APIs need a separate API product for security reasons.

Each management API you plan to use should be turned into an Apigee Proxy.

Management APIs should be called directly from the tool to the Apigee gateway

Enforce a naming convention using a static code analysis tool.

Ask developers to do more code reviews, and focus on the names of fields.

Create a basic data dictionary that covers common use cases and rules for naming

Create a unified data model that attempts to model all use cases for each object type

An out-of-the-box variable populated by Edge when a policy fails

Custom variable that you populate before you Raise Fault

System errors that are only populated in script callouts

Backend error names that are populated along with error code

None of the above

Use Apigee service callouts

Create route rules for each target endpoint

Create multiple target proxy xmls for each endpoint

Use the Node JS async module to invoke target systems