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

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

Virtual host

API product

Developer app

RBAC (Role-based Access Control)

Unit tests

Smoke tests.

Integration tests.

Code quality analysis.

By prefixing x- before the name of the custom object

By prefixing c- before the name of the custom object

By prefixing ext- before the name of the custom object

Open API specification does not allow custom objects

distributed, non-synchronous

non-distributed, synchronous

distnbuted, synchronous

non-distnbuted, non-synchronous

GET/customers/{customer-id}/orders

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

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

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

Add your Apigee TLS certificate to the key store.

Add the backend servers PEM file to the key store.

Add the backend certificate chain to the trust store

Add the backend servers PEM file to the trust store.

Use the KVM to store the contents of the PEM file.

Use the Access Control Policy to reference the PEM file

Add custom attributes for counts for every product. Create custom quota policies for every product which references these custom attributes

Set custom attributes for weekday and weekend count at every product Reference these How variables in the count property of Quota policy at runtime

Add custom attributes at the API Product with counts to use for weekdays and weekends. Using flow variables, reference the custom counts in the Quota policy

Add custom attributes for count at Product level Use a JS Policy to determine which count to use in Quota policy at runtime Use this count attribute in the Quota Policy.

Write business and functional requirements documents.

Implement ad-hoc microservices using a managed container system.

Catalog the data model of the backing data store or API into a data dictionary

Work with the existing or targeted application consumers to build an Open API Specification model

Switch to daily quotas.

Disable quota evaluation for chained proxies.

Increase quota levels in API Product settings

Use Analytics reports to balance proxy queries

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

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

The design should include a new custom header X-Product-Name

The Apigee proxy should allow a query parameter for q=

The Apigee proxy should allow a query parameter for orderld=

Create a different URL for updates

Implement user rights checks in the underlying microservice

Use an OAuth2 scope to identify allowed applications and user granted rights

Retrieve user rights from a database by inspecting the user id bound to the OAuth2 token

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

1

2

5

Unlimited until it expires

Unlimited as long as requests come within specified time of authorization code creation

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