AD0-E559 Sample Questions Answers

To find out where the email is still being used, he can use the Used By tab of the email. This tab shows all the places where the email is referenced, such as smart campaigns, programs, snippets, etc. He can then remove or replace the email from those places before unapprovingand deleting it. The Audit Trail and the Used By page of the program will not show where the email is being used

One new benefit Bhaskar will gain by implementing this new naming convention is that he will be able to create a global product-specific scoring program that triggers off Program Status Changes with a Program Name constraint. This will help him score leads based on their engagement with different product lines across different programs. For example, he can create a trigger that fires when Program Status is Changed and Program Name contains PROD1, and then add a flow step that increases the score for PROD1 by a certain amount. Creating product-specific dynamic content or nurtures does not require this naming convention. 

A trigger token cannot successfully be used within a batch smart campaign. This is because a trigger token references a value that is specific to a trigger event, such as {{trigger.web page}} or {{trigger.email name}}. A batch smart campaign does not have any trigger events, so the trigger token will not have any value. A different smart campaign must be used for each web page or a custom field must be used to accomplish this. It is possible to customize what is shown in an interesting moment view

The administrator needs to add all stages to the success path to correct the model validation error. This is because a revenue model must have at least one stage on the success path, and the success path must be continuous and sequential. The administrator cannot leave any gaps or jumps between stages on the success path. Adding triggers or SLA stages is not required to validate the model.

Two places to troubleshoot are to check to see if the smart campaign handling the registration has any members and to check to see if the person is a member of the Adobe Marketo Engage webinar program and set to the registered status. These checks will help Aya determine if there is any issue with her smart campaign logic or her program membership settings that prevented her from receiving the confirmation email. Checking if the confirmation email has the correct token or if the smart campaign is set to run every time or run once will not help Aya troubleshoot this issue, as they do not affect whether she receives the confirmation email or not.

To find a comprehensive list of actions that users have taken within the Adobe Marketo Engage instance in the last six months, Ajay can use Audit Trail. Audit Trail is a feature that tracks all user activities within an Adobe Marketo Engage instance, such as creating, updating, or deleting programs, assets, fields, users, roles, etc. Audit Trail also shows who updated the Webinar registration landing page in the last month by filtering by user name, date range, and activity type.

To grant access to a different Workspace, Greg needs to adjust the team member’s User to allow access to the APJ Workspace. This can be done by editing the User and selecting the APJ Workspace from the Workspaces drop-down menu. Assigning the User to a different Partition will not change the Workspace access, and adjusting the Role will affect all Users with that Role

To find the list of people who received the losing email, they would use the Was Sent Email filter with the Test Variant constraint. This filter allows them to specify which email and which test variant they want to target. The Was Sent A/B Test filter does not have a Variant constraint, and it is not possible to see who received which test variant without using a constraint. 

The 10 people would automatically follow the new duration. This is because when a wait step duration is modified in an active smart campaign, it affects all people who are currently in the wait step as well as new people who enter the wait step. The new duration will be calculated from the time each person entered the wait step. The 10 people would not remain in the old duration or error out and skip the wait step.

Two fields on the person’s record that have the power to prevent email sends to this extent are Unsubscribed and Email Invalid. Unsubscribed is a field that indicates whether a person has opted out of receiving marketing emails. If this field is set to True, Marketo Engage will not send any non-operational emails to that person. Email Invalid is a field that indicates whether a person’s email address is valid or not. If this field is set to True, Marketo Engage will not send any emails (operational or non-operational) to that person. Marketing Suspended and Email Address do not have the same effect as Unsubscribed and Email Invalid.

A person would not appear on this smart list if the email sent to them last week bounced. This is because a bounced email is not considered as a sent email in Adobe Marketo Engage. Therefore, the person would not meet the criteria of the Was Sent Email filter and would be excluded from the smart list. The person would appear on the smart list if they were last sent an email 6 months ago or if they unsubscribed from the email they received last month, as long as they met the date of activity constraint

Adobe Marketo Engage natively synchronizes with Salesforce and Microsoft Dynamics CRM platforms. These are the only two CRM platforms that have a native integration with Adobe Marketo Engage and do not require any third-party connectors or custom solutions