Apigee-API-Engineer Practice Exam Questions with Answers Google Cloud - Apigee Certified API Engineer Certification

govern the level of access for client applications

select API products for the request

implement SAML security assertions

issue OAuth 2 0 refresh tokens

ProxyEndpoint

HTTPProxyConnection

VirtualHost

TargetEndpoint

GET

PUT

POST

DELETE

OPTIONS

Object caching

Analytics Storage

XML and JSON conversions

Edge flow variable access

FTP

HTTP

SCP

TCP

UDP

restrict access to a set of APIs

configure the quota limits for APIs

restrict access to APIs in different environments

all of the above

DefaultFaultRule can be used lo handle an error that is not explicitly handled by a FaultRule.

DefaultFaultRules are a fixed set of fault rules defined in the product

You cannot use both FaultRule and DefaultFaultRules in the same API proxy

DefaultFaultRule is used when the fault happens during communication with the target

Virtual host

API product

Developer app

RBAC (Role-based Access Control)

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.

Java/JavaScript/Python callout

TargetEndpoint configuration

RouteRules

TargetServer

Check that the Accept header is set to text/json

Check that the Accept header is set to application/json.

Check that the Content-Type header is set to text/json

Check that the Content-Type header is set to application/json

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

Authenticate users.

Authenticate applications

Log update events to StackDriver

Enforce quotas based on Product configurations

Alert when total API latency exceeds 500 milliseconds

Use a Node.JS target to implement a nonblocking call.

Attach a Message Logging policy to the Post Client Flow

Implement a Java Extension Callout with a worker thread

Use an asynchronous Service Callout policy in your proxy (low as soon as you have enough data to log

can be used to generate or renew access tokens

is always issued with every access token

can be used to reset crederfflals

may be reused multiple times to create new access tokens

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

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

GET

HEAD

POST

PUT

OPTIONS

To extend the amount of time an existing access token can be used by resetting the token's expiration time

To request that Apigee re-issue a new access token to replace an expired access token.

To reset an application to its default configuration.

To notify the application that a new access token is required.

return-1,

return false,

context setVanablefWeather Fault", "true"),

throw "Bad Data";

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}

Visualize API proxy error metrics

Visualize API traffic metrics

Visualize Developer Engagement metrics

Visualize API Deployment metrics

Visualize Management API traffic metrics

analytics

oauth

quota

spike arrest

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 a concurrent rate limiting policy

use a LoadBalancer entry in the HTTPTargelConnection session

use RouteRules with multiple TargetEndpoints

use an AssignMessage policy

The internet latency

The network latency

The backend latency

The Apigee proxy latency

The backend database latency

add headers

remove the payload

assign a value to a variable

all of the above

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}

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

TLS Store

Virtual Hosts

Certificate Manager

Keystores and Truststores

Use a data masking configuration to hide sensitive data from logs

Use conditions to skip logging for data that might contain confidential information.

Work with the administrators of the log aggregators to mask confidential data contents.

Sanitize all data on entry using regular expressions that search for confidential data formats.

The Quota specified will automatically be enforced for any Developer App Keys assigned to the API product.

After validating an API key or access token, flow variables are automatically populated with the Quota configuration for later use in a Quota policy

Rate limiting will be enforced precise to the seconds level, even if you configure a per-minute or higher interval

The Quota configuration specified on the API product enforces a global rate limit across all API proxies