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:

Opportunity and Campaign Member objects are standard Salesforce CRM objects that require a full Salesforce license (also called Salesforce license or Salesforce CRM license) to access.

Lightning Platform licenses (and other lighter licenses such as Community licenses) have restricted access and generally do not include access to standard Sales objects like Opportunity and Campaign Member.

Since recruitment staff need to interact with those core CRM objects for recruitment processes (tracking opportunities and campaign membership), full Salesforce licenses are required.

While cost is a consideration, using lower-tier licenses (like Platform licenses or Community licenses) will not provide the required access to these standard objects.

Unlimited Edition is an edition type, not a license type, so A is inaccurate.

Education Data Architecture is a data model, not a license, so B is incorrect.

Lightning Platform Plus license offers more flexibility than the standard Platform license but still does not provide access to standard Sales objects like Opportunities and Campaign Members, so C is incorrect.

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:

Table Driven Trigger Management (TDTM) is a core feature of EDA that governs business logic execution using configuration tables rather than hard-coded triggers.

To maintain compatibility and avoid breaking existing functionality, any third-party apps or customizations must be "EDA Ready" — meaning they follow Salesforce.org best practices, including leveraging TDTM and respecting the EDA trigger framework.

Simply using third-party apps "powered by EDA" (option C) or community solutions (option B) is not enough unless they are explicitly certified or documented as EDA ready.

The yaml file from Salesforce.org GitHub (option A) is a developer tool to define TDTM behavior or deploy trigger configurations but not a solution for ensuring app compatibility.

Therefore, the consultant should advise the college to select third-party apps that are EDA ready, ensuring compatibility with TDTM and EDA best practices.

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:

An Opportunity Funnel report is the best fit when recruiters want to visualize how prospective students are progressing through different stages of the recruitment process (e.g., Inquiry → Application Started → Application Submitted → Admitted → Enrolled).

Why Opportunity Funnel?
It uses the Opportunity Stage field to group and display prospects by recruitment stage.
The funnel chart visually represents conversion rates and drop-offs between stages.
It helps identify bottlenecks and optimize outreach strategies.
It’s a standard Salesforce report type that aligns with Education Cloud’s use of Opportunities to track student journeys.

Why the other options don’t fit:
A. Application Tabular report: Tabular reports are flat lists and don’t support visual stage progression.
B. Education History dashboard: Focuses on academic records, not recruitment stages.
C. Program Enrollment dashboard: Tracks enrolled students, not prospective ones in the recruitment pipeline.

Explanation:

When enabling Course Connections in the Education Data Architecture (EDA), the first step is to run the Course Connections Backfill process.

This backfill process creates Course Connection records based on existing data (like course enrollments), ensuring that historical course relationships are properly reflected.

Only after backfilling can you effectively use Course Connections for tracking relationships between courses (such as prerequisites, co-requisites, or related courses).

Other options:

B (Set up Course Offering Schedule) is related to scheduling but is not the first step in enabling Course Connections.

C (Disable Course Enrollments) is not applicable because Course Enrollments are still needed.

D (Set Record Types for Course Connections) might be required for customization but comes after enabling and backfilling.

Explanation:

The Power of Us Hub has various groups that cater to different community and collaboration needs around Salesforce and open source projects. While the Open Source Commons & Community Sprints group is focused on organizing and participating in sprint events and collaboration, many open source projects and ongoing collaboration happen within the SFDO Open Source Contributors group.

SFDO Open Source Contributors is the group where members collaborate on current and past open source projects, discuss development, contribute code, and share resources related to Salesforce.org open source initiatives.

The Sector: Higher Education group is more about sector-specific discussions and may not focus specifically on open source projects.

SFDO Major Release Announcements is about release updates and announcements, not project collaboration.

CumulusCI (CCI) group is focused on the CumulusCI tool used for automating Salesforce development and deployments, not on open source project discovery.

Reference:
Power of Us Hub community groups and their purpose are documented on the Salesforce Power of Us Hub itself, and the SFDO Open Source Contributors group is the main collaboration space for open source projects under Salesforce.org.

Explanation:

Data skew (uneven distribution of records) is the most likely root cause for all the reported performance issues:

Record Locking:
Occurs when too many records are owned by/assigned to a single user or queue, creating contention.
Example: 90% of student cases assigned to one advisor.

Long Search Times:
Skewed data makes indexes ineffective (e.g., searches on overpopulated values).
Example: Most Course Offerings tied to a single Term.

Long Save Times:
Triggers/validation rules slow down when processing "hot" records (e.g., updates to a widely shared Account).

Why Not the Other Options?
A. TDTM: While trigger logic can impact performance, it wouldn’t cause all these issues.
B. Insufficient code coverage: Affects deployments, not runtime performance.
D. Insufficient storage: Causes "out of space" errors, not locking/search delays.

How to Fix Data Skew:
Identify skewed objects with:
SELECT OwnerId, COUNT() FROM Case GROUP BY OwnerId ORDER BY COUNT() DESC LIMIT 10
Redistribute records (e.g., reassign Cases to multiple queues).
Archive old records to reduce volume.

Explanation:

Campaign Influence is the Salesforce feature specifically designed to connect Opportunities with the Campaigns that helped generate them. It enables institutions to:

Attribute revenue to specific marketing efforts
Measure return on investment (ROI) for each campaign
Track Opportunity conversion influenced by campaign engagement
Report on multi-touch attribution using customizable models

This is essential for advancement teams that want to understand which campaigns are driving donations, applications, or other key outcomes.

Why the other options don’t fit:
Campaign Member: Tracks individual engagement (e.g., email opens), but doesn’t link to Opportunities or ROI.
Parent Campaigns: Useful for organizing campaigns, but not for measuring effectiveness or conversions.
Campaign Hierarchy: Helps with roll-up reporting, but still requires Campaign Influence to connect to Opportunities.

Explanation:

Multi-factor authentication (MFA) requires users to provide two or more verification methods to gain access to a system, which increases security. In this case, the staff must:

Log in with a username and password (something they know), and
Authenticate via an app on their phone (something they have, like an authenticator app).

This matches the definition of MFA, where you combine multiple factors (password + app authentication).

Why not the others?
A. Single sign-on (SSO) allows users to log in once and gain access to multiple systems without re-authenticating, but it does not require multiple authentication factors by itself.
C. Connected apps are used to manage third-party app access to Salesforce but don’t enforce authentication factors.
D. Social sign-on allows users to log in using social media credentials (Google, Facebook, etc.), but it doesn’t inherently require multiple factors.