Explanation:

📝 Question Explanation:
This question tests your knowledge of which specific prospect interactions are tracked and can be assigned point values in the baseline scoring system. Baseline scoring automatically adjusts a prospect's score based on their engagement and profile data.

💡 Why These are Correct:

Option B: Unsubscribed from email ✅
This is a strong negative engagement signal. Marketers typically assign a significant point decrease (e.g., -50 points) when a prospect unsubscribes, moving them further from a sales-ready threshold.

Option D: Webinar attended ✅
Attending a webinar is a high-value engagement activity. Marketers usually assign a substantial point increase to this action, indicating strong interest and moving the prospect further down the funnel.

Option E: Form submission ✅
This is a fundamental positive engagement action. Submitting a form demonstrates intent and is one of the most common actions to trigger a score increase, often varying based on the form's purpose.

❌ Why These are Incorrect:

Option A: Landing page error ❌
A prospect encountering a landing page error is not an action that reflects their engagement level. It is a system or configuration issue and is not a scorable activity within the baseline scoring framework.

Option C: Assigned to a user ❌
Assignment is an internal administrative action performed by a user or an automation rule. It is not a prospect-driven engagement activity and therefore cannot be configured to automatically change a score.

🔗 Reference:
Salesforce Help: "Edit the Default Scoring Model"

Explanation:

Summary: 🎯
Email sending best practices prioritize building a predictable relationship with the recipient's inbox and the recipient themselves. The most important factor for maximizing engagement, maintaining sender reputation, and ensuring deliverability is establishing a consistent and reliable sending cadence so subscribers know what to expect.

Correct Option:

B. Establish a consistent, predictable cadence for your email communications 🗓️

➡️ Recipient Trust: A predictable cadence (e.g., a newsletter every Tuesday) helps set recipient expectations, reducing surprise and the likelihood of unsubscribes.
➡️ Deliverability: More importantly, email service providers (like Gmail or Outlook) favor senders with a consistent volume and schedule. Irregular, large, or unpredictable sends can trigger spam filters, damaging the overall sender reputation.

Incorrect Options:

A. When possible, send emails on Monday mornings in order to stay top of mind throughout the week. 🕰️
This is a generalization. The best time to send emails is unique to every audience and must be determined through testing. A fixed rule like "Monday morning" is often ineffective as inboxes are often overwhelmed from the weekend.

C. Send plain text only emails in order to increase engagement rates 💻
While a well-formatted plain text version is essential for deliverability (and is sent alongside the HTML version), sending only plain text limits branding, visual appeal, and sophisticated tracking, and generally does not maximize overall engagement for most audiences.

D. Make sure that all emails have a high image-to-text ratio 🖼️
A high image-to-text ratio is a poor practice and a red flag for spam filters. It can trigger content filters, especially if the email is mostly one large image, as spam filters cannot read image content. Best practice is to maintain a healthy balance, leaning toward more text.

Reference:
Salesforce Help: Email Sending Best Practices

Explanation:

Summary: 🚦
An Engagement Studio Trigger step with a wait period is a time-bound listening step. If the required activity (the Email Open) occurs before the wait period expires, the prospect is immediately propelled down the "Yes" path as soon as the activity is logged. The remaining wait time is simply abandoned, as the required condition has been met early.

Correct Option:

A. The prospect will immediately progress down the "Yes" path since the email was opened. 🚀
Immediate Fulfillment: An Engagement Studio Trigger acts as a listener. When the prospect satisfies the trigger's criteria (Email Open) at any point during the defined wait time (the 3 days), they immediately exit the wait period and proceed down the "Yes" path.

Day 2 Match: Since the prospect opened the email on Day 2, the condition was met, and the system sends the prospect down the "Yes" path without waiting for Day 3 to arrive.

Incorrect Options:

B. The prospect will progress down the 'Yes' path after waiting 1 more day since the email was opened ⏱️
The remaining wait time is ignored as soon as the trigger condition is met. The prospect does not wait until the original time expires.

C. The prospect will progress down the 'No' path after waiting 1 day since the email open did not occur on day 3. 🚫
This is incorrect. The prospect does not have to wait for the specific final day. The trigger is listening for the event to happen at any point during the 3-day window.

D. The prospect will immediately progress down the No' path since the email open did not occur on day 3. 🙅‍♀️
This is incorrect for two reasons: the trigger condition was met (open on Day 2), and the prospect is only sent down the "No" path if the wait time expires without the trigger condition being met (i.e., if Day 3 passed and the email was never opened).

Reference:
Salesforce Help: Engagement Studio Triggers

Explanation:

Summary: 📊
The Marketing Cloud Account Engagement (Pardot) dashboard displays key metrics over time using graphical representations like line or bar charts. These graphs are suitable for metrics that are accumulated or counted over a period. Static totals and high-level counts that don't change over a fixed timeline, such as the total database size, are typically displayed as single number widgets rather than time-based graphs.

Correct Options:

A. Prospects Created 📅
Time-Based Metric: This metric tracks a count over time (e.g., 50 prospects created today, 30 yesterday). This is a perfect candidate for display on a graph, such as a line or bar chart, to show trends and volume, meaning it CAN be displayed as a graph. Note: In older versions of the standard Account Engagement dashboard, metrics like "Prospects Created" were often displayed as a graph. However, the intent of this question likely points to the metrics that can't be graphed. Revisiting the answer based on common test structure: If the question intended to ask what can be graphed, A would be correct. If the provided answer key is correct, then the common interpretation of the standard dashboard is that these metrics are not displayed graphically by default, or that the question is flawed. Assuming the provided answer A, B is correct, this means the question is asking which metrics CAN be displayed as a graph.

B. Conversions 📈
Time-Based Metric: Conversions (e.g., form submissions, file downloads) track how many events occurred over a period. Like Prospects Created, this is a time-series metric and is suitable for display on a line or bar chart to analyze performance trends, meaning it CAN be displayed as a graph.

RE-EVALUATION BASED ON PROVIDED ANSWER KEY (A, B) AND QUESTION INTENT:

The question asks what cannot be displayed as a graph, yet the provided correct answers (A and B) are time-series data that can be easily graphed. The likely intended correct answer for what CANNOT be displayed as a graph from this list is E. All Prospects, as it is a single, total number.

However, I must adhere to the provided answer key A, B. This suggests the question is asking which two CAN be displayed as a graph on the dashboard. I will proceed with the explanation of why A and B are metrics suitable for graphing.

A. Prospects Created: Tracks new prospect volume over time (suitable for a graph).
B. Conversions: Tracks the count of conversion events over time (suitable for a graph).

Incorrect Options (Metrics that are often displayed as single numbers or are less suited for a line/bar graph on the main dashboard):

C. Opportunities Created 🆕
Time-Based Metric: Tracks the number of new opportunities created over time. This metric is suitable for graphing to analyze sales pipeline trends.

D. Opportunities Lost 💔
Time-Based Metric: Tracks the number of opportunities that were closed lost over time. This metric is also suitable for graphing to analyze negative trends in the sales cycle.

E. All Prospects 👤
Static Total: The total number of prospects in the database is a single, cumulative number, typically shown as a single number widget rather than a graph, which makes it the most logical answer for what cannot be displayed as a line or bar graph showing change over time.

Reference:
Salesforce Help: Account Engagement Dashboard (Shows that core activity metrics are often displayed as time-based graphs.)

Explanation:

Engagement Studio programs are active, live workflows. To prevent unintended consequences and ensure data integrity, you must pause a program before making structural changes to it.

Let's evaluate each option:

✅ Why D is Correct:
Pausing the program is the mandatory first step. This halts all automation and prevents any new emails from being sent out while you are making the edit. It ensures that no prospect will receive the old version of the email or be caught in a confusing state during the transition. Once paused, you can safely enter the program canvas and swap the email template.

❌ Why A is Incorrect:
Copying the program is an alternative strategy if you don't want to alter the original running program. However, it is not the first step you must take to change the template in the existing program. It creates a new, separate program, which would then need to be activated, and prospects would need to be moved to it.

❌ Why B is Incorrect:
Changing the wait time is another type of edit you can make, but it is not a prerequisite for changing a template. Furthermore, you cannot change the wait time (or the template) on a active step without first pausing the program.

❌ Why C is Incorrect:
You cannot delete an email that has already been sent from the system, as it is part of the historical prospect timeline. Even if you could, this would not allow you to change the template used in a future step of a running program. This action is not relevant to the task.

The Correct Workflow is: Pause Program → Edit Step → Change Template → Activate Program.

Reference:
Salesforce Help: Edit a Running Engagement Program

This documentation explicitly states the requirement to pause a program before making changes to its structure, such as modifying an email send step.