Explanation
Two QA checks that Rocky would perform on the email before it is launched are to ensure the right tokens are used and default values are set and to ensure there are HTML and text versions of the email. These checks will help Rocky avoid errors or blank spaces in his email content and ensure that his email can be viewed by different email clients and devices. Ensuring that marketing suspended records have been added to the target audience or ensuring that the unsubscribe link is not used are not QA checks for the email, as they do not affect its appearance or functionality

Explanation
Two statements that are true for archived assets are that a filter to select archived assets for use in reports cannot be used and that archived pages cannot be used in landing page test groups. This is because archiving an asset or a folder means that it will no longer be visible or available for use in most cases. Archived assets will not appear in search results, auto-suggest, templates, test groups, etc. Archived assets are not deactivated and archived templates are not available when creating an email or landing page in Design Studio

Explanation
Two benefits to using global forms versus local forms are that global forms allow for consistent scoring and reporting and data standardization, and that global forms offer a scalable solution especially when there are universal changes that need to be made, saving time and resources. Global forms are forms that are created in Design Studio and can be used across multiple programs and landing pages. They help maintain data quality and consistency, as well as reduce duplication and errors. Global forms do not natively offer custom stylization or tracking without additional constraints.

Explanation
A reason why the webhook failed is that webhooks can only be used successfully once they are approved.
Webhooks are like assets that need to be approved before they can be used in smart campaigns. If a webhook is not approved, it will fail when called by a smart campaign. Webhooks can be used successfully in conjunction with the Member of List filter, in batch campaigns, and without approval.

Explanation
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.