Salesforce
ARC-300 · Question #1
The storefront integrates with a REST based Address verification service (AVS) that uses token based security. The sequence of calls in the API documentation for this AVS looks like the following…
The correct answer is A. Apply page caching to the client authentication controller that is used with AJAX. C. Obtain the token from a custom cache before making the client authentication call. D. Use HTTPService caching for the client authentication call. See the full explanation below for the reasoning.
Question
The storefront integrates with a REST based Address verification service (AVS) that uses token based security. The sequence of calls in the API documentation for this AVS looks like the following: 1. Client authentication call, which contains the merchantId and secret in a GET request and returns a token in the response. 2. Address verification call, which contains the token and the address to verify in a POST request. Once the token is obtained, it is valid for hours and it is not needed to request a new one for subsequent address verification calls, the AVS charges for every request made no matter if it is client authentication call or address verification call. Which three strategies could be applied to allow for efficient use of the service without compromising security? Choose 3 answers
Options
- AApply page caching to the client authentication controller that is used with AJAX.
- BObtain the token from local storage of the browser and update it once It expires.
- CObtain the token from a custom cache before making the client authentication call.
- DUse HTTPService caching for the client authentication call.
- EUse a job to store and update the token in a custom object that is used from the storefront code
How the community answered
(20 responses)- A75% (15)
- B10% (2)
- E15% (3)
Community Discussion
No community discussion yet for this question.