Education-Cloud-Consultant Practice Test Questions

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:

A college wants to “map available classes” during a data migration into Education Data Architecture (EDA). In EDA, the object that represents an actual class being run in a specific academic term is Course Offering. Think of it this way:

A Course is the catalog entry (for example, BIO-101 Intro to Biology).

A Term represents the academic period (for example, Fall 2026).

A Course Offering is the specific instance of that course in that term (for example, BIO-101 offered in Fall 2026, section 01).

Salesforce’s EDA documentation is explicit that a Course Offering is always related to a Term, and it’s the record type used to represent a course being offered during that term. This is exactly what “a class is available for a given term” means in data-model terms: the institution is making a course available for enrollment during a particular term, which is represented by creating (or migrating) Course Offering records tied to the appropriate Term.

This also aligns with how schools usually migrate “available classes”: they typically import Terms, Courses, then create Course Offerings (often with fields like capacity, section, instructor, delivery mode, etc.). After Course Offerings exist, students and faculty are connected to them via Course Connections (enrollment/teaching relationships), and schedules can be added via related scheduling objects.

Why the other options are not correct

A. Course Connection
A Course Connection represents the relationship between a Contact (student/faculty) and a Course Offering—for example, a student enrolled in that offering or a faculty member assigned to teach it. It does not indicate availability; it indicates participation/association.

B. Attendance Event
Attendance-related objects track attendance occurrences (sessions/events) and participation. They are used after a class is running, not to define that a class exists in a term.

C. Time Block
A Time Block represents a scheduled time pattern (days/times) and is used to help build scheduling (often linked through course offering schedule concepts). It supports when something meets, but it does not represent the existence/availability of the class in a term.

Explanation:

B (Salesforce → Marketing Cloud one-way integration):
Marketing Cloud typically pulls data from Salesforce CRM (where student/prospect records live) to run campaigns. This is a one-way sync from Salesforce to Marketing Cloud, ensuring Marketing Cloud has the latest audience data. This is the most common and recommended pattern for Marketing Cloud integration (see reference below).

D (Event system ↔ Salesforce two-way integration):
Since the event system manages attendance and registration data, it must sync this data with Salesforce to update student engagement and academic progress records. Two-way integration allows both systems to stay synchronized:

Event attendance updates Salesforce student profiles and engagement history.
Salesforce can update the event system if needed (e.g., student status or cancellations).
This ensures a unified, up-to-date student profile for reporting and personalized outreach.

Why not A or C?
A one-way or two-way integration only between Marketing Cloud and the event system will not capture academic progress and career interests stored in Salesforce. The key is syncing event data into Salesforce to create the complete picture.

Valid Official References:
Salesforce Marketing Cloud Connect Overview
"Use Marketing Cloud Connect to integrate Salesforce CRM data with Marketing Cloud to create personalized, targeted marketing campaigns."
Salesforce Help - Marketing Cloud Connect Overview

Salesforce Education Cloud Integration Patterns
Explains the need for two-way integration between Salesforce and external systems like event management to keep student records up-to-date.
Trailhead Module: Education Cloud Integration (Look for Integration Patterns section)
Salesforce Event Management Integration
While Salesforce does not have a native event management system, best practice is to integrate third-party event systems with Salesforce to keep records aligned, usually with two-way sync.
Reference from Salesforce Success Community discussions and Education Cloud Best Practices guides.

Explanation:

The school district can install Work.com Command Center directly into its existing Salesforce org (configured with the K-12 Architecture Kit) to manage reopening safely. Here’s why:

Why B?
Work.com Command Center is designed to coexist with other Salesforce products (like Education Cloud/K-12 Kit).
It provides reopening tools (health checks, contact tracing, capacity management) that schools need post-pandemic.
No need for a separate org—installing in the existing org ensures:
Single source of truth for student/staff data.
No duplicate data entry.
Unified reporting across academics and health/safety.

Why Not the Other Options?
A. Work.com does not require a separate org—it’s built to integrate.
C. Student Success Hub focuses on academic advising, not pandemic safety.
D. A third-party app would add complexity when Work.com already meets the need.

Implementation Steps:
Install Work.com Command Center via Salesforce Setup.
Map K-12 data (e.g., Student/Staff Contacts, School Locations) to Work.com objects.
Train admins on health monitoring features (e.g., daily symptom surveys).

Explanation:

Why:
Recruitment staff need to work with Opportunities and Campaign Members (from Campaigns). Those are standard CRM objects that are included with the Salesforce (full CRM) user license, not with Platform licenses. Lightning Platform Starter/Plus licenses are intended for custom apps and a limited set of standard objects; they do not include access to core Sales objects like Opportunities or Campaigns, which recruitment teams rely on.

Eliminate the rest:
A. Unlimited Edition requires a full Salesforce license.
Edition (Enterprise/Unlimited, etc.) is an org choice; it doesn’t change that users who need Opportunities/Campaigns still require Salesforce (full) user licenses. The issue here is object access, not edition.

B. Education Data Architecture requires a Community license.
EDA/EDF is a data model on core CRM; internal staff don’t need a Community (Experience Cloud) license for it. Community licenses are for external users, not internal recruiters.

C. The business user case requires a Lightning Platform Plus license.
Platform licenses don’t include Opportunities or Campaigns, so they won’t meet the stated needs.

References:
Salesforce Help — Standard User Licenses (shows full Salesforce license includes standard CRM objects like Opportunities/Campaigns).
Salesforce Help — Features Available with Lightning Platform Starter/Plus (feature table for Platform licenses; excludes core Sales objects).
Salesforce Help — Experience Cloud User Licenses (for external users; not required for internal EDA users).

Explanation:

In the Education Data Architecture (EDA), the Relationship object is used to define how one Contact (e.g., a student) is connected to another Contact (e.g., a parent or emergency contact). This makes it the most appropriate functionality for tracking emergency contacts for students studying abroad.

Why Relationships?
Allows you to define person-to-person connections (e.g., Parent, Guardian, Emergency Contact).
Supports custom relationship types, so you can tailor it to your institution’s terminology.
Enables reporting and visibility into who to contact in case of emergencies.
Can be used alongside Household Accounts to model family structures, but is more precise for individual contact roles.

Why the other options don’t fit:

B. Household Accounts: Groups family members under a shared account but doesn’t define specific roles like “emergency contact.”

C. Affiliations: Used to link Contacts to organizations (e.g., departments, employers), not other people.

D. Success Teams: Designed for assigning internal support staff (e.g., advisors, counselors), not external emergency contacts.

Explanation:

EDA Ready Apps (D) are specifically designed to be compatible with the Education Data Architecture (EDA) and its Table Driven Trigger Management (TDTM) framework.

TDTM allows institutions to manage triggers declaratively, ensuring extensibility and avoiding conflicts between custom code and packaged solutions.

By choosing EDA Ready apps, the college ensures that future apps and configurations will integrate seamlessly with EDA and respect TDTM functionality.

Option A (yaml file from Salesforce.org GitHub): YAML files are used for configuration and deployment scripts but do not guarantee app compatibility with EDA or TDTM.

Option B (Salesforce.org community solution): Community solutions may be helpful but are not guaranteed to be formally vetted for EDA/TDTM compatibility.

Option C (third-party apps powered by EDA): "Powered by EDA" is not an official designation. Only EDA Ready apps are certified to work with EDA and TDTM.

📖 Reference:
Salesforce.org: EDA Ready Apps — official designation for apps compatible with EDA and TDTM.
Trailhead: Education Data Architecture Basics

Explanation:

Salesforce Inbox is the all-in-one solution that meets both email tracking and calendar scheduling requirements for recruiters.

Why Salesforce Inbox (D)?

Email Tracking:
See opens/clicks with real-time notifications
Logs interactions automatically in Salesforce

Scheduling:
Insert available time slots from the recruiter's calendar (Outlook/Gmail)
Lets students self-schedule meetings via embedded links

Native Integration:
Works seamlessly with Salesforce CRM (e.g., Contacts, Opportunities)

Why Not the Other Options?
A. Gmail Integration: Basic email sync, no advanced tracking/scheduling
B. Custom Automation: Complex to build and lacks out-of-the-box scheduling
C. Einstein Activity Capture: Tracks emails but no scheduling features

Implementation Tip
Pair with Education Cloud to track student engagement in recruitment pipelines

Explanation:

Recruitment/Admissions Process in Salesforce/EDA: The Recruitment and Admissions process is generally mapped to the standard Salesforce Opportunity object.

A Prospective Student is often represented by a Lead and/or Contact.

The student's actual application or potential enrollment is tracked using the Opportunity object.

The various stages in the recruitment process (e.g., Inquiry, Applied, Application Review, Admitted, Enrolled) are modeled using the Opportunity Stage field.

Visualization Requirement: The recruiters want to "visualize the number of prospective students at various stages."

Funnel Report: A Funnel Chart or Funnel Report is the definitive standard tool in Salesforce to visualize records (Opportunities) progressing through a defined multi-stage process (Opportunity Stages). It clearly shows the drop-off rate between each stage, which is precisely what recruitment staff need to manage their pipeline.

Why the Other Options are Incorrect:
A. Application Tabular report: A tabular report is a simple list of records and does not provide a visual representation of progress (funnel) or stage flow. The "Application" process is typically driven by the Opportunity Stage.

B. Education History dashboard: The Education History object (EDA) tracks a student's prior academic history (high school, previous college), not their current status in the recruitment pipeline.

C. Program Enrollment dashboard: The Program Enrollment object (EDA) tracks the student's actual enrollment in a program after they have been successfully admitted. It does not track the recruitment stages that lead up to enrollment.

Explanation:

Before Course Connections can be fully enabled or utilized in the Education Data Architecture (EDA), the system needs to know which record types to use for "Student" and "Faculty" connections.

Record Type Requirement: Course Connections rely on specific record types to distinguish between a student enrolling in a course and a faculty member being assigned to teach it.

EDA Settings Configuration: You must first create or identify these record types and then navigate to EDA Settings > Course Connections to specify which record type corresponds to the Student and which corresponds to the Faculty.

Validation: If you attempt to enable Course Connections without defining these record types, the system will not function correctly as it won't know how to categorize the relationships between Contacts and Course Offerings.

Why Other Options are Incorrect:
A. Run Course Connections Backfill: This is a critical step, but it must be done after the record types are set and Course Connections are enabled. The backfill converts existing legacy "Course Enrollment" records into the new "Course Connection" format.

B. Set up Course Offering Schedule: This is part of the general academic setup but is not a technical prerequisite for enabling the Course Connection functionality itself.

C. Disable Course Enrollments: In EDA, Course Connections actually replace/enhance the legacy way of tracking enrollments. However, you do not "disable" them first; you configure the new model to take over their function.

References:
Salesforce Help: Configure Course Connections
Trailhead: Course Connections in EDA