Education-Cloud-Consultant Practice Test Questions

Explanation:

In Salesforce (especially with EDA), Contacts without parent Accounts have significant implications for data visibility and security.

Key Impacts:
Public Visibility: Contacts without Accounts default to org-wide sharing settings (often "Public")
Data Exposure Risk: Sensitive student data becomes accessible to unauthorized users
EDA Dependency: Account relationships drive sharing models in Education Data Architecture

Why Not the Others?
A: Contacts aren't automatically private without specific sharing settings
B: Ownership skew requires mass records under one user, not missing Accounts
C: Affiliations track relationships but don't control sharing

Recommended Solution:
Use "Administrative Accounts" in EDA to maintain control while meeting staff requirements

Explanation:

Since students and alumni are served on a first come, first served basis without assignment to a specific advisor, Queue Management is the best fit. Queues allow incoming requests (cases, tasks, or appointments) to be placed in a shared pool where staff can pick up the next item in line, ensuring fair and efficient handling.

Why not the others?
A. Success Teams are used to assign groups of collaborators to a student but don’t manage first-come, first-served workflows.
C. Appointment Scheduling helps book appointments but doesn’t manage work distribution in a queue.
D. Assignment Rules automatically assign records to users or queues but doesn’t handle shared picking or first-come, first-served processing.

Explanation:

To track teaching assistants (TAs) for classes, the Course Connection object in EDA is the proper choice.

Why Course Connection (B)?
Role Tracking: Stores student/teacher relationships with Role field options
Flexibility: Supports multiple TAs per course with custom fields
EDA Integration: Works with Term Grade and Attendance objects

Why Not the Others?
A. Course Offering: Defines class details but not participant roles
C. Term Grade: For student grades only
D. Program Enrollment: For degree programs, not course assignments

Implementation Tip:
Create a "Teaching Assistant" record type for easy filtering

Explanation:

For alumni engagement, networking, and fundraising, these Education Cloud considerations are most relevant:

Relationships (A):
Tracks alumni-to-alumni and alumni-to-staff connections (e.g., "Mentor," "Board Member").
Supports networking initiatives by mapping professional relationships.

Third-Party Event App (D):
Education Cloud lacks native event management for complex alumni gatherings.

Apps like Eventbrite or Certain integrate with Salesforce for:
Registration pages.
Attendance tracking.
Donation tie-ins.

Why Not the Others?
B. Grants Management: For scholarship disbursements, not general alumni fundraising.
C. Insights Platform: Overkill for basic alumni data (standard reports suffice).

Implementation Tips:
Use Affiliation + Relationship objects for board membership tracking.
Look for AppExchange apps with Education Cloud compatibility.

Explanation:

The Attribute object in Education Data Architecture (EDA) is designed to store characteristics or data points related to a Contact (student), such as:

Visa type or status
Passport expiration date
Vaccination records
Special needs or preferences

This makes it ideal for tracking student-specific documentation required by the Study Abroad office. Attributes are flexible and can be configured with custom types and values to match institutional requirements.

Why the other options don’t fit:
A. Program Plan: Defines the structure of an academic program—not used for storing student documentation
B. Success Team: Represents a group of staff supporting a student—not related to document tracking
D. Affiliation: Tracks relationships between a Contact and an Account (e.g., employer, department)—not for storing personal documentation

Explanation:

Service Cloud provides robust case management features that allow help desks to track and measure key metrics like average resolution times and escalations. It supports tracking student requests (such as password resets), automating workflows, managing service levels, and generating reports on help desk performance.

Why not the others?
A. Salesforce Identity focuses on identity and access management, not case tracking.
B. Digital Engagement extends Service Cloud to support omni-channel interactions but doesn’t handle case resolution metrics by itself.
C. Einstein Next Best Action provides AI-driven recommendations but is not a case management solution.

Explanation:

In the Education Data Architecture (EDA), the Administrative Account model is best suited for representing institutional relationships, such as a student’s connection to a residence hall, department, or program. Here's why it fits this scenario:

✔ Administrative Account model:
Used when a Contact (e.g., an international student) is associated with an institutional entity rather than a household
Ideal for residence halls, university departments, or study abroad programs
Allows address information to be stored on the Administrative Account and linked to the student via an Affiliation
Supports multiple addresses and address synchronization for institutional Accounts

Why the other options don’t fit:
A. Standard Account: Generic Salesforce model—not tailored for education use cases
B. Person Account: Not supported by EDA; EDA uses Contact + Account relationships instead
C. Household Account: Used for family or donor relationships—not for institutional housing or services

Explanation:

While Advisor Link includes features like tracking student milestones (Success Plans), visualizing degrees, and scheduling appointments, syncing appointments with external calendars like Outlook requires third-party integration. Calendar syncing functionality is typically provided by apps or connectors that integrate Salesforce events with Outlook or other calendar systems.

Why not the others?
A. Success Plans is included in Advisor Link for milestone tracking.
C. Degree visualization is supported within Advisor Link or related Education Cloud features.
D. Appointment scheduling is a core feature of Advisor Link.

Explanation:

To protect sensitive student data in a sandbox used for training, Salesforce Data Mask is the ideal solution because:

Automated Anonymization:

Scrambles personal data (e.g., names, emails, IDs) in sandboxes while preserving:
Data structure (field types, relationships).
Formatting (e.g., john.doe@university.edu → user123@example.com).

Education-Specific Protections:
Masks Contact fields (student records).
Complies with FERPA/GDPR for training environments.

No Custom Development Needed:
Pre-built masking templates for common fields.

Why Not the Others?
B. Formula Fields: Can’t anonymize existing data (only calculate values).
C. Event Monitoring: Tracks user activity, doesn’t mask data.
D. Salesforce Shield: For encryption/auditing, not sandbox anonymization.

Implementation Tip:
Run Data Mask during sandbox creation/refreshing.

Explanation:

In Salesforce Education Data Architecture (EDA), the default Account model determines how Contacts are grouped and associated with Accounts. The Administrative Account model is the recommended default for most institutions because it creates a one-to-one relationship between a Contact (e.g., a student) and their Account.

When the system admin selects the Educational Institution record type as the default Account model, the consultant should confirm whether this aligns with the university’s data strategy. However, Salesforce recommends using the Administrative Account record type as the default container for Contacts in EDA, especially for students, faculty, and staff.

Why the other options are incorrect:
B. A new Program Enrollment record will automatically be created: This does not happen automatically when a Contact is created. Program Enrollments must be created explicitly.
C. Multiple address management can only be enabled for the House Account record type: Not true—multiple address management is supported for both Administrative and Household Accounts in EDA.
D. Contacts are private only to Administrative Account record type: Contact visibility is governed by org-wide defaults and sharing rules—not by the Account record type alone.