🗣️ [Mentor Alex Phi] 🌟 Adobe Marketo Engage Community Mentorship Program 2024 🌟

[nmillar]

Final Quiz Time!

>>>>>

1. An organization has added a Welcome Series Engagement program for both B2B and B2C trial downloads of a promising new product. The first email in the Engagement Program has poorer deliverability than expected as compared to the rest of the series.

What solution of those listed below would have the greatest impact on deliverability and the best outcome for the organization?

A: Implement a bounce management to proactively suspend records who bounce multiple times.

>>>>>
2. Your organization has requested more stringent data rentention around consent history based on opt-ins and unsubscribes. They've created a "Consent History" Text Area field to assist with this goal.

Which method would be functional, and have the most robust and efficient data retention for analysis within Marketo?

For the sake of brevity, assume "Consent Given/Withdrawn" accounts for the respective steps or choices.

D : Change Data Value flow step for "Consent History" to "Consent Given/Withdrawn {{system.dateTime}}" followed by Interesting Moment flow step for "{{lead.Consent History}}"

[alludoalex]

1. The focus on the question was the first email in the nurture series, so bouncing multiple times likely wouldn't happen until later in the series. The form would be the best point to check for validity - and give that feedback to the user. This would ensure that good data makes it into the platform at a higher rate, and more effective than blocking freemail as this trial targets both B2B and B2C. 

So B would be the preferred answer here.

2. Activity History for Interesting Moments is 25 months, Activity History for Change Data Value is 90 days. However, a text area field has a character limit high enough that it will likely never be exceeded for this purpose (65,535 total characters), and a token for a field can actually be referenced in a flow step that changes it. 

So Consent History can be changed to [new string] + [old string] with [tokens or values]  + {{lead.Consent History}}. For this use case, the positive and negative opt-in retention would permanently be logged in this field as the user gives and withdraws consent and it would be self contained in this field for analysis. 

This is an edge case, but considering all the options in answering the question has several nuances that might be helpful on the exam.

In D, the Activity History isn't really being fully captured each time as it's being updated by the most recent activity, and then stamped onto an Interesting Moment. It's helpful, but not quite as thorough as A.

There could be other considerations in a given tech stack with other limitations - so the question is focused on "analysis within Marketo". This solution has less steps and effectively has permanent retention with each change being logged.

[nmillar]

Wow that second one is tough but the first one totally makes sense now that I think it through more!!

[nmillar]

I think what I struggle with the biggest on these tests are "what could be the answer" and "what makes the most sense for the answer" a lot of them "seem" like they could be right and then I second guess myself!

Thank you for answering all of my questions and for this program! It has been great!

[derelict_wombat]

Agreed.  There is clearly a "we are looking for a specific answer" in a lot of the questions when there could be some ambiguity around it or how its asked.  Adobe is looking for the "best" answer in some cases based on a "textbook" implementation.  But in reality when I feel that a grain of salt needs to be taken and thats where i get messed up a lot on the test questions as my experience there can be several correct ways of doing things even if its not what the test writers had in mind. 

Good luck @nmillar with the test!

@alludoalex Thanks for the help.  This has been great. 

[nmillar]

Good luck to you as well!!!