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

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

C.Use a Spike Arrest policy setting the UseEffectiveCount parameter

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

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

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

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

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

E.Verify the signature of the JWT using a shared secret.

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

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

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

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

A.Create a unified data model that attempts to model all use cases for each object type

B.Enforce a naming convention using a static code analysis tool.

C.Ask developers to do more code reviews, and focus on the names of fields.

D.Create a basic data dictionary that covers common use cases and rules for naming

A.Break the proxy into smaller components using proxy chaining

B.Use the period "." to namespace variables.

C.Create a data dictionary describing all the variables

D.Use camelCase variable names instead of snake_case