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

Use a Java Callout to the target, calling the hot datacenter first and the warm datacenter in case of failure

Use the not datacenter as the TargetEndpoint and configure a FaultRule to call the warm datacenter in case of failure

Create two service callouts to the target, calling the hot datacenter first and the warm datacenter in the event of failure on the first call

Create Target Servers for each datacenter and configuring the TargetEndpoint with a LoadBalancer, setting the Is Fallback property on the warm datacenter

specify using the secuntyDefinrtions name property

specify using the secuntySchemas name property

specify using the security Variables name properly

specify using the securityParams name property

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

return-1,

return false,

context setVanablefWeather Fault", "true"),

throw "Bad Data";

Use the Spike Arrest policy, to smooth out traffic spikes.

Use a Quota policy, to ensure that no client exceeds a defined quantity of traffic.

Work with operations to ensure autoscaling is set up to respond to traffic events

Use the Concurrent Rate Limit policy, to ensure back-end services are not overwhelmed

Creation of a message logging policy in Apigee.

Creating user stories to fulfill the business requirements.

Creating support tickets that cover each of the business requirements.

Creating a cross functional team of API engineers, business analysts, and backend software developers.

Info

host

paths

license

swagger

basePath

produces

The internet latency

The network latency

The backend latency

The Apigee proxy latency

The backend database latency

Step

TargetConfiguration

RouteRule

Connection

Path

use a concurrent rate limiting policy

use a LoadBalancer entry in the HTTPTargelConnection session

use RouteRules with multiple TargetEndpoints

use an AssignMessage policy

distributed, non-synchronous

non-distributed, synchronous

distnbuted, synchronous

non-distnbuted, non-synchronous

TLS Store

Virtual Hosts

Certificate Manager

Keystores and Truststores

add headers

remove the payload

assign a value to a variable

all of the above

Use service callouts configuration for each target, and use a condition to decide which to invoke.

Use a Key-Value Map configuration to access SSL and URL information to invoke target systems

Use an AssignMessage policy to override default target URL and define 2-way SSL configuration at runtime

Create another target endpoint with SSL configured and define route rule to pick that depends on available variables.

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.