Cisco®
Oracle
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
All Vendors
  2. Home
  3. Exams
  4. Salesforce
  5. PDX-101

Free Salesforce PDX-101 Exam Braindumps (page: 8)

Page 8 of 77
PDF with 304 Questions

What list email or email template report deliverability metric could indicate an unverified sending domain?

  1. Forward count
  2. Hard bounces
  3. Skimmed percentage
  4. Total queued

Answer(s): B

Explanation:

The list email or email template report deliverability metric that could indicate an unverified sending domain is hard bounces. Hard bounces are permanent delivery failures, such as invalid email addresses or blocked domains. Hard bounces can negatively affect the sender reputation and the email deliverability. One of the possible causes of hard bounces is an unverified sending domain, which means that the email domain used to send emails from Marketing Cloud Account Engagement is not authenticated and verified by Marketing Cloud Account Engagement. An unverified sending domain can result in the email servers rejecting the emails as spam or phishing attempts. To avoid hard bounces and improve email deliverability, the marketer should verify the sending domain in Marketing Cloud Account Engagement by following the steps in the reference link. Forward count, skimmed percentage, and total queued are not deliverability metrics that could indicate an unverified sending domain. Forward count measures how many recipients forwarded the email to another person. Skimmed percentage measures how many recipients opened the email for less than two seconds. Total queued measures how many emails were waiting to be sent from Marketing

Cloud Account Engagement. These metrics are not related to the email domain verification or the email delivery failures. Reference Verify Your Sending Domain



A Marketing Cloud Account Engagement administrator wants to gather a prospect's company name and Job title, but only once they have captured prospect's first name, last name and email address in a previous form submission.
Which feature should they use?

  1. Progressive Profiling
  2. Always display even if previously completed
  3. reCaptcha
  4. Dependent Fields

Answer(s): A

Explanation:

The feature that the Marketing Cloud Account Engagement administrator should use to gather a prospect's company name and job title, but only once they have captured the prospect's first name, last name, and email address in a previous form submission, is progressive profiling. Progressive profiling is a feature that allows the administrator to display different fields on a form based on the information that the prospect has already provided. This way, the administrator can avoid asking the same questions repeatedly and collect more information gradually. Progressive profiling can be enabled on a form by selecting the option "Always display even if previously completed" for the fields that are required, such as first name, last name, and email address, and selecting the option "Only display if progressive profiling is enabled and the field is blank" for the fields that are optional, such as company name and job title. This way, the form will only show the optional fields once the required fields are filled out. Always display even if previously completed, reCaptcha, and dependent fields are not features that can achieve the same goal as progressive profiling. Always display even if previously completed is an option that can be used to enable progressive profiling, but it is not a feature by itself. reCaptcha is a feature that can be used to prevent spam submissions on a form, but it does not affect the fields that are displayed on the form. Dependent fields are fields that are displayed or hidden based on the value of another field, but they do not depend on whether the prospect has already provided the information or not. Reference Progressive Profiling



What is needed for a page action to trigger for a prospect visiting a high value web page?

  1. Create an automation rule based on the specific webpage.
  2. Add a completion action on the landing page.
  3. Adding a page action and Marketing Cloud Account Engagement tracking code on the page.
  4. Adding a page action on the form.

Answer(s): C

Explanation:

What is needed for a page action to trigger for a prospect visiting a high value web page is adding a page action and Marketing Cloud Account Engagement tracking code on the page. A page action is a Marketing Cloud Account Engagement feature that allows the administrator to perform certain actions when a prospect views a specific page on the website, such as increasing the score, changing the field value, adding to a list, etc. A page action can be created by entering the URL of the page and selecting the actions to be performed. A Marketing Cloud Account Engagement tracking code is a snippet of code that can be added to the website to track the page views and activities of visitors and prospects on the website. The Marketing Cloud Account Engagement tracking code is required for the page action to work, as it identifies the prospects who visit the page and executes the actions on them. Creating an automation rule, adding a completion action, or adding a page action on the form are not what is needed for a page action to trigger for a prospect visiting a high value web page. An automation rule is a rule that runs in the background and matches prospects based on certain criteria and performs certain actions. An automation rule can use page views as a criterion, but it is not the same as a page action, as it does not depend on a specific URL. A completion action is an action that is triggered when a prospect completes a specific activity, such as submitting a form, clicking a link, or opening an email. A completion action is not related to a page view, unless the page contains a form or a link. A page action on the form is not possible, as a page action can only be added on a page, not on a form. Reference [Page Actions] [Marketing Cloud Account Engagement Tracking Code]



What is the expected behavior if an automation rule is NOT set to repeat?

  1. The prospect can match the criteria multiple times and the action runs each time.
  2. The action can only run once per day on the prospect.
  3. The prospect matches the criteria once, but the action runs multiple times.
  4. The prospect matches the criteria once and the action runs once.

Answer(s): D

Explanation:

The expected behavior if an automation rule is not set to repeat is that the prospect matches the criteria once and the action runs once. An automation rule is a rule that runs in the background and matches prospects based on certain criteria and performs certain actions. An automation rule can be set to repeat or not repeat, depending on whether the administrator wants the rule to run multiple times or only once on the same prospect. If the automation rule is not set to repeat, it means that the rule will only run once on each prospect who matches the criteria, and it will not run again even if the prospect matches the criteria again in the future. The other options are not the expected behavior if an automation rule is not set to repeat. The prospect cannot match the criteria multiple times and the action runs each time, as this would require the rule to be set to repeat. The action cannot run only once per day on the prospect, as this would require the rule to have a daily frequency limit. The prospect cannot match the criteria once, but the action runs multiple times, as this would require the rule to have multiple actions or a recurring action. Reference [Automation Rules Overview]



Viewing page 8 of 77
Viewing questions 29 - 32 out of 304 questions



Post your Comments and Discuss Salesforce PDX-101 exam prep with other Community members:

PDX-101 Exam Discussions & Posts