Adobe AD0-E559 Exam - Topic 5 Question 56 Discussion

Actual exam question for Adobe's AD0-E559 exam

Question #: 56
Topic #: 5

David wants to time-stamp a custom field called 'MQL DateTime Most Recent' every time a person reaches the MQL stage. He will use a smart campaign that triggers upon MQL and the flow will have no wait steps.

Which type of token would he use in the "Change Data Value' flow step required to achieve his goal?

ASystem

BPerson/Lead

CTrigger

Show Suggested Answer

Suggested Answer: A

To time-stamp a custom field with the current date and time, David would use a System token in the ''Change Data Value'' flow step. System tokens are tokens that reference system-level information, such as date, time, IP address, etc. The System token for date and time is {{system.dateTime}}.Person/Lead tokens and Trigger tokens are not suitable for this purpose, as they reference person-level information or trigger-specific information.

by Yong at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium AD0-E559 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Ben

6 days ago

A) System token? Really? That wouldn't make any sense for a lead-level custom field.

upvoted 0 times

...

Gerardo

11 days ago

C) Trigger is the way to go here. The flow is triggered by the MQL event, so we need to use a Trigger token to timestamp the custom field.

upvoted 0 times

...

Idella

16 days ago

B) Person/Lead is the correct answer. The custom field 'MQL DateTime Most Recent' is a field on the lead, so we need to use a Person/Lead token to update it.

upvoted 0 times

...

Johnson

21 days ago

I’m a bit confused; I thought Trigger tokens were for events rather than data changes. Is that correct?

upvoted 0 times

...

Jamal

26 days ago

I feel like I've seen a similar question before, and it was definitely about using a Person/Lead token for custom fields.

upvoted 0 times

...

Felix

1 month ago

I'm not entirely sure, but I remember something about system tokens being used for broader data changes. Could that apply here?

upvoted 0 times

...

Stephaine

1 month ago

I think the answer might be B) Person/Lead since we're dealing with a specific individual's data, right?

upvoted 0 times

...

Cristy

1 month ago

I'm a little unsure here. Is a Trigger token an option for updating a lead field? Or is that more for accessing information about the trigger itself? I think I'd go with a Person/Lead token to be safe, but I'd want to double-check the documentation to be sure.

upvoted 0 times

...

Fanny

2 months ago

This seems straightforward. Since the goal is to update a custom lead field, I'd use a Person/Lead token in the 'Change Data Value' step. The question mentions no wait steps, so the flow should be able to immediately update that field when the MQL stage is reached.

upvoted 0 times

...

Glendora

2 months ago

Okay, for this type of flow, I'd definitely use a Person/Lead token. That's the token type that gives you access to lead/contact fields, so it should let me update the 'MQL DateTime Most Recent' custom field when the MQL trigger fires.

upvoted 0 times

...

Elliot

2 months ago

Hmm, I'm not sure about this one. I'd have to double-check the different token types and which one would be best for updating a custom lead field. The question mentions a 'Change Data Value' step, so I'm guessing a Person/Lead token is the way to go.

upvoted 0 times

...

Sophia

2 months ago

I think I'd use a Person/Lead token to update the 'MQL DateTime Most Recent' field. That seems like the right type of token to access and update a custom lead field.

upvoted 0 times

...