Google Apigee-API-Engineer Google Cloud - Apigee Certified API Engineer Exam Practice Test

response millis and connect.millis

target.timeout and proxy timeout

connect.timeout.millis and io.timeoutmillis

connect timeout and network timeout

Cassandra nodes

Routers

Message Processors

Management Servers

Create an Oauth 2 0 Service Account API proxy

Create an Oauth 2.0 Password Grant Type API proxy

Create an Oauth 2.0 Client Credential Flow Grant Type API proxy

Create a new API proxy for a GET /v1/customers/{customerid}

Create a new API proxy for a PUT/v1/customers/{customerid}

Create a new API proxy for a POST /v1/customers/{customerid}

Create a new API proxy for a DELETE/v1/customers/{customerid}

Notify operations of the release

Run an automated smoke test suite.

Monitor the logs looking for unusual error patterns

Ensure all sources are checked into source control

Add Caching Policies

Add a Spike Arrest Policy

Add an Assign Message Policy

Add a Statistics Collector Policy

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

GET/customers/{customer-id)/orders

GET/orders7customer-id={customer-id}

GET /getOrdersForCustomer?customer-id={customer-id}

POST /orders with a post-body of customer-id={customer-id}

Step

TargetConfiguration

RouteRule

Connection

Path

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.

generate an authorization code

generate an access token

verify the device ID

validate the client API key

obtain the end user's consent for the application to request the user's protected resources

validate the developer name

Review the Epics and meet the cross functional team

Review and update the user stories and tasks in detail.

Review the high level design document and ask questions

Update support tickets that have been sitting for x number of days

Adhere to Pragmatic REST

Model the API to the consumption use case

Require API Key authentication

Implement CORS.

Validate inputs.

Return a 200 OK

Return a 302 Found

Return a 201 Created

Return a 202 Accepted

Return a 303 See Other

Return a 400 Bad Request

Verify the signature of the JWT using a shared secret.

Parse the JWT to extract the exp: nbf and iat properties to determine if the token is still valid

Pass the JWT to a preconfigured 3rd party for verification of the signature, exp, nbf and iat properties

Use the OpenID Connect URL to locate a trusted 3rd party for verification the signature, exp, nbf and iat properties

Using the JKWS URL in the OpenID Connect configuration, fetch the signing key to verify the JWT signature and parameters

Use the InvalidateToken operation with cascade=true

Use the InvalidateToken operation with cascade=false

Store a list of revoked tokens in Firebase. On each access, check the list and only allow unrevoked tokens through

Store a list of revoked tokens in Key-Value Maps. On each access, check the list and only allow unrevoked tokens through

return-1,

return false,

context setVanablefWeather Fault", "true"),

throw "Bad Data";

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