Explanation:

The K-12 Architecture Kit includes pre-built dashboards that meet basic reporting needs.

Why Sample Dashboard (B)?
Ready-to-Use: Includes standard demographic reports out-of-the-box
Time-Saving: No need to build from scratch
Customizable: Can be modified if needed

Why Not the Others?
A. New Dashboard: Unnecessary when samples exist
C. Tableau Accelerator: Overkill for basic reporting

Implementation Steps:
Open Analytics Studio
Locate "Student Demographics" dashboard
Apply filters as needed

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 Salesforce Trust website provides up-to-date information on Salesforce product release dates, system status, and maintenance schedules for all Salesforce instances. The university can use this site to confirm release windows that might impact their project timeline.

Why not the others?
A. Trailhead is a learning platform and does not provide release schedules.
C. Setup Menu in Salesforce shows org settings but not global release dates.
D. Partner Community is for Salesforce partners and may have some information but the Trust site is the authoritative source.

Explanation:

The Alumni Association needs to track alumni interests and host networking activities, which involves managing events, registrations, and attendee engagement.

While Education Cloud provides a strong foundation for managing constituent data, event management functionality is often enhanced with specialized third-party apps available on the Salesforce AppExchange.

These apps offer robust tools for event creation, registration, ticketing, communication, and reporting, tailored for complex event needs like networking activities.

Why not the others?
A. Install Insights Platform to understand alumni data —
Insights Platform is useful for data analysis but does not provide event management features.
B. Install NPSP into their Education Cloud environment —
The Nonprofit Success Pack (NPSP) is tailored for nonprofits, not education institutions, and may introduce unnecessary complexity or overlap with Education Cloud functionality.

Explanation:

The consultant should review the Relationships object first when noticing that there are more than 10,000 child records associated to a single parent record for the institution that is experiencing record locking and sharing performance issues in a Salesforce org with EDA.

The Relationships object is an object in EDA that allows users to store information about how two Contacts are related to each other, such as parent-child, sibling, or spouse. The Relationships object can cause record locking and sharing performance issues in a Salesforce org with EDA if there are too many child records associated to a single parent record, such as a Contact with many Relationships or Affiliations.

The consultant should review the Relationships object first when noticing that there are more than 10,000 child records associated to a single parent record for the institution that is experiencing record locking and sharing performance issues in a Salesforce org with EDA by checking if there are any data skew or ownership skew issues and applying best practices to resolve them.

Accounts or Affiliations are not objects that the consultant should review first when noticing that there are more than 10,000 child records associated to a single parent record for the institution that is experiencing record locking and sharing performance issues in a Salesforce org with EDA.