MENU
You are generating tokens depending on a partner's service level at runtime You need to control access token expiration What should you do?
Suggested Answer: D
Get Premium Google Cloud - Apigee Certified API Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
14 comments · newest first
PA
Paola
10 months ago
Wait, can you really store expiration in custom attributes? Sounds odd.
FE
Felton
10 months ago
A is a bit risky, right? Query parameters can be manipulated.
VI
Virgie
10 months ago
I think D is a solid choice too, especially for dynamic environments.
LI
Ling
11 months ago
B could work, but it might complicate things unnecessarily.
FE
Felicidad
11 months ago
Option C seems the most straightforward for managing expiration.
RI
Rikki
11 months ago
Adding expiration times in custom attributes sounds familiar, but I can't recall if it's the most efficient method for runtime access.
SH
Shawnna
11 months ago
I practiced a similar question where we used Key Value Maps. It feels like a good option for managing expiration times.
CO
Colette
11 months ago
I think passing expiration values as query parameters could work, but it seems less secure.
GE
Gene
12 months ago
I remember something about storing values in a configuration file, but I'm not sure if that's the best approach for access tokens.
PA
Patria
12 months ago
I'm a bit confused by this question. I'm not sure if I fully understand the context and requirements. I think I'll need to re-read the question and the options a few times to make sure I'm choosing the best approach.
FA
Fanny
1 year ago
Okay, let me think this through. I'm pretty confident that option D is the way to go here. Storing and fetching the expiration value from Key Value Maps seems like the most robust and scalable solution.
ET
Ethan
1 year ago
Ah, this is a good one. I think I'll go with option C - storing and fetching the access token expiration times from a configuration file. That way, I can easily update the expiration times without having to modify the code.
LA
Lavonne
1 year ago
Hmm, I'm a bit unsure about this one. I'm trying to decide between options B and D. I'm leaning towards D since it seems more dynamic and flexible, but I'll need to think it through a bit more.
AR
Aracelis
1 year ago
This seems like a straightforward question about controlling access token expiration. I think I'll go with option D - storing and fetching the expiration value from Key Value Maps at runtime. That seems like the most flexible and dynamic approach.