Hello All,
I am preparing for MCE & came across below question. I am confused on the correct answer as the key say option B is correct.
Can someone guide how is option B correct.
An Adobe Marketo Engage expert is tasked with creating an operational email compliance campaign that needs to update the “Unsubscribed Date” and the “Unsubscribed History” fields. The “Unsubscribed Date” is a custom date type field created to log the person's date of unsubscribe and clear out the field when a person re-subscribes. The “Unsubscribe History” is a custom text area field created to store the dates when a person's “Unsubscribed” field changed to the True value. How should the campaign be set up to ensure that both the custom fields are updated for all the Unsubscribed people created or updated?
o Smart List - Use "Person is Created" and “Data Value Changes” triggers. Use the “Unsubscribed” field is False filter.
Flow Step 1 - Use "Change Data Value" step to update the "Unsubscribed Date" field to {{system.date}} value when the “Unsubscribed” field is True.
Flow Step 2 - Use "Change Data Value" step to append the “Unsubscribed History” field as per “{{lead.Unsubscribed Date}}, {{lead.Unsubscribed History}}" value when the “Unsubscribed” field is False.
o Smart List - Use “Data Value Changes” trigger.
Flow Step 1 - Use "Change Data Value" step, Choice 1 updates the “Unsubscribed Date” field to {{system.date}} and Choice 2 updates the “Unsubscribed History” field as per “{{lead.Unsubscribed Date}},{{lead.Unsubscribed History}}".
o Smart List - Use "Person is Created” and “Data Value Changes” triggers. Use the “Unsubscribed” field is True filter.
Flow Step 1 - Use "Change Data Value" step to update the "Unsubscribed Date” field to {{system.date}} value when the ) "Unsubscribed" field is True.
Flow Step 2 - Use "Change Data Value" step to append the “Unsubscribed History” field as per “{{lead.Unsubscribed Date}}, {{lead.Unsubscribed History}}” value when the “Unsubscribed” field is False.
o Smart List - Use "Person is Created" and “Data Value Changes” triggers. Add the “Unsubscribed” field is True filter.
Flow Step 1 - Use "Change Data Value" step to
update "Unsubscribed Date" field to {{system.date}} value when the “Unsubscribed” field is True and to NULL otherwise.
Flow Step 2 - Use "Change Data Value" step to append the “Unsubscribed History” field as per “{{lead.Unsubscribed Date}}, {{lead.Unsubscribed History}}”
value when the “Unsubscribed” field is True.
Solved! Go to Solution.
Uhh... Option B (if you mean the second setup in your list) is not correct.
Without a constraint on the New Value, you would be changing the date + history fields even when the value changes to false!
The question is also needlessly confusing because it says “changed” in one part but then at the end throws in “Unsubscribed people created.”
If you want to capture people who were created with their Unsubscribed field set to true from the start, that requires a Person is Created trigger in addition to a Data Value Changes trigger. If you’re created that way, there’s no material change. Should you be setting the Unsubscribed Date to the current {{system.date}} even though it’s not a change? It’s not clear from the wording.
In any case, none of the answers are correct. Option D is the only one that mentions setting to NULL (which is a requirement) but it’s impossible for that Add Choice to ever match, since there’s a filter on Unsubscribed=True.
P. S. There’s also another wrinkle here, Durable Unsubscribe, that makes it more complex. But we can leave that aside for the moment.
Uhh... Option B (if you mean the second setup in your list) is not correct.
Without a constraint on the New Value, you would be changing the date + history fields even when the value changes to false!
The question is also needlessly confusing because it says “changed” in one part but then at the end throws in “Unsubscribed people created.”
If you want to capture people who were created with their Unsubscribed field set to true from the start, that requires a Person is Created trigger in addition to a Data Value Changes trigger. If you’re created that way, there’s no material change. Should you be setting the Unsubscribed Date to the current {{system.date}} even though it’s not a change? It’s not clear from the wording.
In any case, none of the answers are correct. Option D is the only one that mentions setting to NULL (which is a requirement) but it’s impossible for that Add Choice to ever match, since there’s a filter on Unsubscribed=True.
P. S. There’s also another wrinkle here, Durable Unsubscribe, that makes it more complex. But we can leave that aside for the moment.
Hi Sanford,
Thank you for the clarification. Much appreciated.
I also marked option D, as thats the only theoretically most appropriate option.
Except D is still clearly, even deliberately, wrong!
Exactly... they want the unsubscribe date cleared when someone resubscribes, so you can't have a filter of unsubscribed being true.
Where did you find this question? Not in the exam itself, right? Was it among the test questions that Adobe released for the MCE? I think I had gone through these and made comments on at least half of the questions due to unclear or flat our incorrect statements.
Hi,
Yes, its one of the question on the Sample test series for MCE.
Can you suggest any other sample test which i can use for preparations.