Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Cloud - Apigee Certified API Engineer Exam - Topic 11 Question 7 Discussion

You are generating tokens depending on a partner's service level at runtime You need to control access token expiration What should you do?
D) Store and fetch expiration value from Key Value Maps at runtime to use for access token creation.
A) Pass access token expiration values as a request query parameter
B) Add expiration times in product custom attributes for retrieval at run time
C) Store and fetch access token expiration times from a configuration file to use at run time

Google Cloud - Apigee Certified API Engineer Exam - Topic 11 Question 7 Discussion

Actual exam question for Google's Google Cloud - Apigee Certified API Engineer exam
Question #: 7
Topic #: 11
[All Google Cloud - Apigee Certified API Engineer Questions]

You are generating tokens depending on a partner's service level at runtime You need to control access token expiration What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Niesha at Jun 10, 2025, 02:51 AM

Limited Time Offer

25%

Off

Get Premium Google Cloud - Apigee Certified API Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Paola
8 months ago
Wait, can you really store expiration in custom attributes? Sounds odd.
upvoted 0 times
...
Felton
9 months ago
A is a bit risky, right? Query parameters can be manipulated.
upvoted 0 times
...
Virgie
9 months ago
I think D is a solid choice too, especially for dynamic environments.
upvoted 0 times
...
Ling
9 months ago
B could work, but it might complicate things unnecessarily.
upvoted 0 times
...
Felicidad
9 months ago
Option C seems the most straightforward for managing expiration.
upvoted 0 times
...
Rikki
9 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.
upvoted 0 times
...
Shawnna
10 months ago
I practiced a similar question where we used Key Value Maps. It feels like a good option for managing expiration times.
upvoted 0 times
...
Colette
10 months ago
I think passing expiration values as query parameters could work, but it seems less secure.
upvoted 0 times
...
Gene
10 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.
upvoted 0 times
...
Patria
10 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.
upvoted 0 times
...
Fanny
11 months 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.
upvoted 0 times
...
Ethan
11 months 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.
upvoted 0 times
...
Lavonne
11 months 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.
upvoted 0 times
...
Aracelis
11 months 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.
upvoted 0 times
...

Save Cancel