Explanation:

Extended Mail Merge is a Salesforce solution that enables users to generate preformatted documents (like letters) by merging Salesforce data into templates. It supports:

- Creating personalized letters for scholarship and admission decisions.
- Generating documents that can be electronically sent, printed, and mailed.
- Using templates designed in Microsoft Word or other formats, which can be customized with data fields from Salesforce.

This makes it the ideal choice for managing formatted communications that need both electronic delivery and physical mailing.

Why not the others?
- Salesforce reports can generate lists and summaries but don’t produce formatted, customizable letters ready for printing or mailing.
- A third-party app could work but is unspecified and may not be necessary if Extended Mail Merge meets requirements.
- Salesforce Files is a storage solution and doesn’t create merged documents from data.

Explanation:

To properly map legacy data to EDA objects and fields during migration, the EDA Data Dictionary is the essential reference.

Why EDA Data Dictionary (A)?
Comprehensive Field Guide: Lists all standard EDA objects and their fields
Migration-Specific Details: Shows required fields and picklist values
Avoids Guesswork: Ensures proper alignment with EDA's data model

Why Not the Others?
B. Lightning Connect: For real-time external data access, not migration
C. Data Loader: Just an import tool, doesn't provide field guidance
D. EDA Settings: Configures features, not data mapping

Explanation:

Address Management is a standard feature of the Education Data Architecture (EDA). It allows institutions to track and manage multiple addresses for both Contacts (e.g., students, alumni) and Accounts (e.g., households, academic programs).

Key capabilities include:
Support for multiple address records per Contact or Account
Configuration of primary, seasonal, and alternate addresses
Automatic creation of new address records for significant changes, with options to update existing ones for minor edits
Synchronization between Contact and Account address records when appropriate

Why the other options are not standard EDA features:
A. Student Advising: Requires Advisor Link or Student Success Hub, which are add-on products
B. Event Management: Not included in EDA; typically handled via third-party apps or Marketing Cloud
C. Degree Auditing: Not part of EDA; usually managed by external Student Information Systems (SIS)

Explanation:

To support course selection and purchasing for corporate training programs, the university needs functionality that includes:

A catalog of available courses
E-commerce capabilities (e.g., shopping cart, checkout, payment processing)
A user-friendly interface for students to browse and register

Salesforce does not provide this functionality natively in CPQ, Financial Services Cloud, or Files. Therefore, a third-party app—often available on the AppExchange—is the most appropriate solution.

Examples of suitable third-party apps:
LearnTrac or EVA Event Tech Hub: Offer course registration, payment integration, and session management
Fonteva Events: Supports event/course registration with payment and agenda-building
Blackthorn Events: Offers branded registration pages, ticketing, and payment processing

Why the other options don’t fit:
A. Salesforce CPQ: Designed for configuring and quoting complex products—not for course registration or e-commerce
B. Financial Services Cloud: Tailored for banking, insurance, and wealth management—not education or training
C. Salesforce File: Used for document storage and sharing—not for course selection or purchasing

Explanation:

Digitizing and automating transcript requests typically requires a user-friendly, public-facing form that applicants can use to submit requests directly into Salesforce. While Salesforce provides some native tools, this scenario calls for a solution that can handle form submission, automate processes, and integrate seamlessly with Salesforce data—all preferably declaratively.

Many third-party apps on the AppExchange specialize in creating public-facing forms with automation capabilities that feed data directly into Salesforce. These apps often support complex workflows and offer a better user experience without requiring custom development.

Why not the others?
A. Email-to-case is used to convert incoming emails into cases, not for creating public-facing forms.
B. Process Builder is an automation tool within Salesforce but cannot create external forms or interfaces.
C. Salesforce Files is for storing and managing files, not form creation or automation.

Explanation:

The K-12 Architecture Kit provides specific objects to track student performance and engagement. For the use case of monitoring midyear grades and class absences, these two objects are purpose-built:

✔ C. Term Grade:
Captures student performance for a specific course during a defined academic term (e.g., midyear or semester grades)
Linked to Course Offering and Program Enrollment
Enables reporting on academic progress across terms

✔ D. Attendance Event:
Tracks student attendance at the class or session level
Records absences, tardies, and presence with timestamps and reasons
Supports intervention workflows and attendance analytics

Why the other options don’t fit:
A. Behavior Involvement: Used to log behavioral incidents, not attendance or grades
B. Program Enrollment: Tracks a student’s enrollment in a program or school, but not specific attendance or term grades

Explanation:

Einstein Prediction Builder enables Salesforce users to create custom AI-powered predictions without needing code. In this case, the Admissions Department can build a predictive model to analyze historical data and estimate the likelihood that accepted students will enroll.

Why not the others?
A. Advisor Link Pathways focuses on student advising and success, not predictive analytics for enrollment.
B. Tableau Prep Builder is a data preparation tool used to clean and transform data before analysis but does not provide predictive modeling.
C. Einstein Next Best Action suggests personalized recommendations based on business rules or AI but is not used to build enrollment likelihood models.

Explanation:

The Education History object in the Education Data Architecture (EDA) is designed to store and track a Contact’s prior educational experiences. For Advancement teams, this is especially useful when:

Tagging alumni based on their previous schools or programs
Segmenting outreach based on graduation year, degree earned, or GPA
Identifying potential donors with shared academic backgrounds

Why Education History fits this use case:
Enables targeted engagement based on academic history
Supports donation opportunity segmentation by school, program, or credential
Can be extended with custom fields for campaign tagging or affinity scoring

Why the other options don’t fit:
B. Program Plan: Defines academic requirements—not used for historical tracking or outreach
C. Attribute: Stores characteristics like interests or preferences—not structured academic history
D. Relationship: Tracks person-to-person or person-to-organization connections—not school history

Explanation:

To segment email content by department while maintaining centralized control, Marketing Cloud Business Units are the ideal solution.

Why Marketing Cloud Business Unit (D)?
Department-Level Isolation: Separate workspaces for each team's contacts and content
Centralized Oversight: Share brand assets while keeping data segmented
Alumni-Specific Benefits: Supports complex segmentation by graduation year/donation history

Why Not the Others?
A. Salesforce DMP: For advertising, not email governance
B. Einstein ABM: For B2B targeting, not alumni communications
C. Pardot Business Unit: Lacks scale for large alumni databases

Implementation Tip:
Structure Business Units by department (e.g., Alumni-Engineering, Alumni-Business)

Explanation:

To ensure that each program director only sees data relevant to their own program, the dashboard must respect row-level security based on the user’s access. Setting the dashboard to “View as: The dashboard viewer” ensures that:

Each viewer sees the dashboard as themselves, not as the Dean
The data displayed is filtered by the user’s sharing and role-based access
No additional filters or customization are needed to restrict visibility

Why the other options don’t meet the requirement:
A. Let Dashboard Viewers Choose Whom They View the Dashboard As: This allows users to impersonate others, which could expose data they shouldn’t see
B. View as the Dean: Would show all data the Dean can access, violating the sharing model
C. Add a dashboard filter: Filters are user-selectable and don’t enforce security—users could still view data outside their scope

Explanation:

When a large volume of records (like over a million student Contact records) are integrated into Salesforce and owned by a single user (such as an Integration User), this creates ownership data skew. This happens because many child records (Contacts) are related to the same owner record, which can cause record locking, performance issues, and slow transaction processing.

Why not the others?
A. API call limits relate to the number of API requests, but the question focuses on record ownership and performance.
C. Account data skew refers to many child records (like Contacts) related to the same Account; here, the issue is related to ownership, not account hierarchy.
D. OAuth token limits relate to authentication limits and are not related to record ownership or performance.

Explanation:

Two key objects in the Education Data Architecture (EDA) data model are:

Affiliation: Represents a relationship between a person (Contact) and an organization (Account), such as a student’s affiliation with a school or department.
Attribute: Used to capture additional descriptive information about contacts or accounts, like tags or custom characteristics relevant to education.

Why not the others?
Opportunity: While Opportunities exist in Salesforce and are used for fundraising and donations, they are not unique or core to EDA specifically.
Account: Accounts are standard Salesforce objects representing organizations or households, but they are not unique to or specifically part of the EDA extension.