Salesforce MCE-Dev-201 Exam - Topic 5 Question 5 Discussion

Actual exam question for Salesforce's MCE-Dev-201 exam

Question #: 5
Topic #: 5

[All MCE-Dev-201 Questions]

How often should a developer request a new token when making multiple API calls in v1?

AWhen changing routes/objects

BBefore every new call

COnce an hour

DEvery 15 minutes

Show Suggested Answer

Suggested Answer: C

A developer should request a new token once an hour when making multiple API calls in v1. Salesforce Marketing Cloud access tokens are typically valid for one hour, and refreshing them every hour ensures that the API calls are authenticated.

Salesforce Marketing Cloud API Token Management

Salesforce Marketing Cloud Authentication

by Johnathon at Dec 18, 2025, 08:27 AM

Limited Time Offer

25%

Off

Get Premium MCE-Dev-201 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Jerry

5 days ago

I prefer B. Better safe than sorry, right?

upvoted 0 times

...

Nidia

10 days ago

Wait, are we really supposed to request a new token that often?

upvoted 0 times

...

Chu

15 days ago

D) Every 15 minutes seems excessive!

upvoted 0 times

...

Lezlie

20 days ago

I thought it was C) Once an hour?

upvoted 0 times

...

Silvana

25 days ago

I disagree, it should be B) Before every new call.

upvoted 0 times

...

Mitsue

1 month ago

A) When changing routes/objects is the way to go.

upvoted 0 times

...

Gladys

1 month ago

I recall something about tokens being valid for a period, but I can't remember if it's an hour or 15 minutes.

upvoted 0 times

...

Quentin

2 months ago

I practiced a similar question, and I think the answer was related to timing, maybe C or D?

upvoted 0 times

...

Winfred

2 months ago

I'm not really sure, but I feel like it might be B since you want to ensure security with each call.

upvoted 0 times

...

Carolynn

2 months ago

Option C is the way to go. Gotta keep that token fresh, but no need to overdo it.

upvoted 0 times

...

Yoko

2 months ago

Haha, I just use the same token until it stops working. Then I get a new one and start the cycle again.

upvoted 0 times

...

Toshia

3 months ago

D is the way to go. 15 minutes is the sweet spot - not too often, but keeps things secure.

upvoted 0 times

...

Odette

3 months ago

I always just use the same token and hope for the best. Who has time to get a new one every call?

upvoted 0 times

...

Queenie

3 months ago

Option B is the correct answer. Getting a new token before every call ensures your API access is always valid.

upvoted 0 times

...

Adria

3 months ago

I'm a bit confused by this question. Do we need to request a new token for every single API call, or is there a more efficient way to handle it? I'll have to review the documentation again to make sure I understand the best approach.

upvoted 0 times

...

Chun

3 months ago

I'm leaning towards option D. Getting a new token every 15 minutes might be a bit overkill, but it's better to be safe than sorry when it comes to API security.

upvoted 0 times

...

Jess

4 months ago

Option C seems like the most reasonable choice to me. Requesting a new token once an hour should be frequent enough to keep our API calls secure without being overly burdensome.

upvoted 0 times

...

Lonny

4 months ago

Hmm, I'm a bit unsure about this one. I know we need to get new tokens, but I can't remember if it's before every call or just at certain intervals. I'll have to think this through carefully.

upvoted 0 times

...

Bong

4 months ago

I think it's A, but I remember something about needing a new token for different routes.

upvoted 0 times

...

Raina

4 months ago

I think I'll go with option B. It's better to be safe and get a new token before each call to avoid any authentication issues.

upvoted 0 times

...

Wayne

4 months ago

I think A is the best choice. Tokens should change with routes.

upvoted 0 times

...