Apigee-API-Engineer Sample Questions Answers

Use a JavaScript callout

Use a MessageLog policy in (he DefaultFaulIRule.

Use a conditional MessageLog policy in the PostClientFlow

Use a conditional MessageLog policy as the last item in the Response flow

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

GET /customers/{customend}/v1

GET /customers/v1/{customerid}

GET /v1/customers/{customerid}

GET /customers?customend={customerid}&version=v1

The rate of 5 per second indicates that 5 requests can be made at any time during a second: but the 6th and later requests dunng the same second would be rejected

Spike arrest is calculated separately on each message processor, so you could end up with significantly more than 5 calls in a second

It is possible to make fewer than 5 requests in a second and still cause a spike arrest

The continueOnError setting means that normal flow processing will resume even if the traffic exceeds the spike arrest rate

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

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.

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

Concurrent Rate Limit > Spike Arrest > Quota

Quota > Concurrent Rate Limit > Spike Arrest

Spike Arrest > Quota > Concurrent Rate Limit

Quota > Spike Arrest > Concurrent Rate Limit

GET/getOrdersBetweenDates/2016-01-01/2016-02-01

GET/orders'?from-date=2016-01-01&to-date=2016-02-01

GET /customers/{customer-id}/orders'?from-date=2016-01-01&to-date^2016-02-01

POST /searchorders with a post-body of from-date-2016-01-01&to-date=2016-02-01

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.

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

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

GET

HEAD

POST

PUT

OPTIONS

no order, random

alphabetical by name

bottom to top as configured in the ProxyEndpoint

bottom to top as configured in the TargetEndpoint

top to bottom as configured in the ProxyEndpoint

Use XSLT to transform the XML payload and then use a XML to JSON policy

Use XML to JSON policy first to convert to JSON and then ExtractVariables with a JSONPath to extract the body from the converted SOAP envelope

Use ExtractVariables with an XPath first to extract the SOAP body and then use XML to JSON policy

Use an AssignMessage policy to convert the SOAP response to a JSON response, using XPath expressions to retrieve the data

govern the level of access for client applications

select API products for the request

implement SAML security assertions

issue OAuth 2 0 refresh tokens

add headers

remove the payload

assign a value to a variable

all of the above

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}

ServiceCallout

AssignMessage

RequestMessage

Message Validation

The object will expire from both locations after the TimeToLive has passed.

The object will be stored in Cassandra twice

When object is retrieved from KVM, the object with the same key will be returned from the cache instead to improve performance

One of the inserts (either to cache or to KVM) will fail as you cant insert the same key twice

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

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

AccessEntity,XSL,ExtractVariable

ServiceCallout, ExtractVanable, AssignMessage

XMLToJSON, ExtractVanables, APIKeyValidation

MessageValidation, ServiceCallout, AccessControl

provides simple mechanism to authenticate developers

provides simple mechanism to identify developer apps

authenticates the developer

authenticates the client application

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

Quotas are only enforced when client authentication is enabled

Quota plugin requires quota-memory plugin to be installed and enabled

Quota plugin requires OAuth Plugin to be installed and enabled

Quota plugin must execute after the quota-memory Plugin execution

Quota plugin must execute after the OAuth Plugin execution

Use the payload.

Use a header version: vl.

UsetheURI/products/productjd/vl

UsetheURI/v1/products/product id

GET

POST

OPTIONS

PUT

Use a default Spike Arrest policy setting the limit to 100 TPS

Use a Quota enforcement policy set to limit throughput to 100 TPS

Use a Spike Arrest policy setting the UseEffectiveCount parameter

Keep a count of accesses in the back-end, rejecting queries when they exceed 100 TPS

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

You should recommend an Apigee Edge Access Control policy

You should recommend that the backend API's use TLS v12 to secure their APIs.

You should recommend the use of custom secure headers with time stamp verification

You should recommend a design change that uses a Apigee microgateway in front of the backend APIs.

Add Caching Policies

Add a Spike Arrest Policy

Add an Assign Message Policy

Add a Statistics Collector Policy

analytics

oauth

quota

spike arrest

Specify in PopulateCache policy

Specify number of Max Elements In Memory on the Cache Resource definition

Specify max size in KB in Cache Resource definition

It cannot be configured as Apigee manages it internally.