Explanation:

The question states:

“…elementary school plans to implement the K-12 Architecture Kit… wants to send SMS messages to parents.”

Here’s how to think about it:

The K-12 Architecture Kit is built on EDA (Education Data Architecture) but does not include SMS messaging out of the box.

Salesforce does not provide native SMS functionality in the core platform unless:
You purchase additional products (e.g. Digital Engagement).
Or install a third-party app from the AppExchange.

So, to send SMS messages, schools typically:

✅ Install an AppExchange SMS app, such as:
Mogli SMS
SMS Magic
Twilio for Salesforce
360 SMS

These apps integrate with Salesforce and:
Let you send individual or bulk SMS
Work with standard or custom objects (including EDA/K-12)
Are widely used in education for parent communication

Hence, D. App on the AppExchange is the correct recommendation.

Why Not the Other Options?

✅ A. Pardot (now Marketing Cloud Account Engagement)
Primarily an email marketing tool.
Does not natively send SMS.
Also focused more on marketing vs. operational communications like school-parent messaging.
→ Not suitable.

✅ B. Social Studio
Manages social media accounts (Twitter, Facebook, etc.)
Not used for SMS communication.
→ Not suitable.

✅ C. Education Data Architecture (EDA)
Provides data model for students, households, relationships.
Does not provide SMS functionality itself.
→ Not a messaging tool.

Therefore, the correct solution is an AppExchange app.

Explanation:

When installing EDA into an existing Salesforce environment, the process differs from starting with a fresh trial.

Marketplace Access: The Salesforce AppExchange is the official marketplace for all Salesforce packages. For existing customers, the AppExchange provides the entry point to the EDA Installer (managed via the MetaDeploy tool).

The Installation Process: While the actual installation technically runs through a specialized web-based tool (MetaDeploy), Salesforce documentation and exam standards point to the AppExchange as the starting location where consultants find the listing to begin the process.

Why use the Installer? Unlike a standard package link, the EDA installer on the AppExchange performs a "Pre-Install Validation." It checks your existing org for incompatible settings, record types, or namespace conflicts before it attempts to deploy the architecture.

Incorrect Answers

A. Trailhead:
Why it's incorrect: Trailhead is a learning platform. While it contains modules that teach you how to install EDA and provides "Playground" environments for practice, it is not the location used to install the architecture into a customer's production or sandbox environment.

B. Partner Community:
Why it's incorrect: The Partner Community is a portal for Salesforce partners to access resources, training, and support. While a consultant might find documentation or best practices there, the actual software package and installer are not hosted within the Partner Community.

References
Salesforce Help: Install EDA in an Existing Org
Salesforce AppExchange: Education Data Architecture (EDA) Listing
Trailhead: Education Data Architecture Basics - Install EDA

Explanation:

University Advancement staff are required to authenticate to internal systems using two factors:

something they know (username and password), and
something they have (an app on their phone).

This requirement directly describes Multi-Factor Authentication (MFA). MFA is an identity and access management feature that requires users to provide two or more verification factors during login. In Salesforce, MFA commonly combines a username/password with a second factor such as the Salesforce Authenticator app, a third-party authenticator app, a hardware security key, or a verification code. Salesforce explicitly defines MFA as a security control that adds an extra layer of protection beyond a password alone and requires at least two different authentication factors.

From a compliance and security standpoint, Salesforce has made MFA a baseline security requirement for most direct logins. Salesforce documentation states that MFA significantly reduces the risk of account compromise and is required for users who log in directly to Salesforce products. This makes MFA not only the correct functional choice, but also the correct best-practice and standards-aligned recommendation for a university handling sensitive advancement and donor data.

Because the scenario explicitly mentions “logging in with a username and password” and “authenticating via an app on their phone,” MFA is the most precise and correct answer.

Why the other options are not correct

A. Single sign-on (SSO)
SSO allows users to log in once and access multiple systems without re-entering credentials. While SSO can work together with MFA, SSO alone does not inherently require a second authentication factor. You can have SSO without MFA, so it does not meet the stated requirement by itself.

C. Connected apps
Connected Apps are used to authorize applications to access Salesforce via OAuth. They control app-level access and scopes, not end-user authentication flows involving phone-based verification.

D. Social sign-on
Social sign-on allows users to authenticate using third-party identity providers (such as Google or Facebook). It does not guarantee multi-factor authentication and is typically not appropriate for secure internal university systems.

Salesforce References (end)
Salesforce Help – Multi-Factor Authentication Overview
Salesforce Security Guide – MFA Requirement
Trailhead – Secure Your Users with Multi-Factor Authentication

Exam Tip (ED-Con-101)
If a question describes “username and password + phone/app/code/key”, the correct answer is almost always Multi-Factor Authentication (MFA)—even if SSO or identity providers are mentioned elsewhere.

Explanation:

These two metrics directly reflect user adoption and process efficiency, which are key indicators of a successful Salesforce implementation—especially when transitioning from manual processes like spreadsheets and paper:

✔ A. Percentage of staff logins each month:
Measures user adoption and engagement with the new system
A high login rate suggests that staff are actively using Salesforce instead of reverting to old tools
Helps identify training needs or resistance to change if adoption is low

✔ C. Time saved when creating business reports:
Reflects process efficiency gains from automation and centralized data
Demonstrates how Salesforce reduces manual effort and improves decision-making speed
Can be benchmarked against pre-implementation reporting timelines

Why the other options are less effective:
B. Volume of emails to the office: May fluctuate for unrelated reasons and doesn’t directly measure system success
D. Number of student phone inquiries: Could be influenced by external factors and doesn’t reflect internal process improvements

Explanation:

Why this is correct
The goal is to identify engaged prospects using student data in Salesforce by matching:
- Event registration/attendance (currently in the event management system)
- Career interest (likely tracked in Salesforce)
- Credit completion toward a major (academic progress data in Salesforce/EDA)

To do that reliably, Salesforce needs the event system’s registration + attendance data in Salesforce so it can be combined with the academic/career data already there. A two-way integration is the best recommendation because it typically supports:
- Inbound to Salesforce: attendance/registration updates for matching and reporting/scoring.
- Outbound from Salesforce: pushing the right student/prospect records (and updates) to the event system to reduce duplicates and keep identities aligned.

Why the other options are wrong
A. Two-way integration between the event system and Marketing Cloud
Even if Marketing Cloud has engagement messaging, it’s not the system of record for academic progress (credits) and often not where you want to do the cross-domain matching (attendance + credits + interest). This doesn’t ensure the data lands in Salesforce, which is where they want to identify engaged prospects.

B. One-way integration between Marketing Cloud and the event system
This might help with promotion logistics (e.g., sending invitations), but it doesn’t solve the core requirement: enriching/aligning Salesforce student records with event attendance and then analyzing alongside academic progress and career interest.

✅ Bottom line:
Bring event attendance/registration into Salesforce (and keep records aligned both ways), so Salesforce can do the matching and identification they want.