Ownership data skew is what the consultant shoulddiscuss with the university, because it is a potential performance issue that can occur when a large number of records are owned by a single user. In this case, the Integration User owns over one million Contact records, which can cause slow or failed queries, reports, or list views. The consultant should advise the university to distribute the ownership of the records among multiple users or queues to avoid ownership data skew. API call limits, account data skew, and OAuth token limits are not relevant tothis scenario. References:

https://help.salesforce.com/s/articleView?id=sf.data_skew_ownership.htm & type=5

https://developer.salesforce.com/blogs/engineering/2012/04/avoid-account-data-skew-for-peak-performance.html

Action Plans are a feature of Admissions Connect that allow staff to create and assign tasks to students, track their progress, and automate reminders and notifications. Action Plans can be used to streamline the Study Abroad process by creating a template of tasks that students need to complete to qualify for the program, such as submitting an application, attending an orientation, obtaining a visa, etc. Staff can then assign the Action Plan to each student who is interested in studying abroad and monitor their completion status. Action Plans can also be integrated with Salesforce Communities to provide students with a self-service portal where they can view and update their tasks, upload documents, and communicate with staff. References: [Admissions Connect Documentation], [Admissions Connect: Action Plans]

Affiliation Mappings are used to automatically create and populate the PrimaryAffiliation field on the Contact record based on the Account record type of the related Affiliation. For example, if a Contact has an Affiliation with an Account of record type “Academic Program”, the Primary Affiliation field on the Contact record will bepopulated with that Account name. The consultant can go to Affiliation Mappings in EDA Settings to configure which Account record types should trigger this behavior and which fields should be used to store the Primary Affiliation. References:

Education Data Architecture Basics - Unit 3: Affiliations and Relationships

EDA Documentation - Affiliation Mappings

The initial step that the consultant should take when planning to integrate Salesforce with the StudentInformation System (SIS) is B. Define the process1. This means that the consultant should identify the business requirements, use cases, and scenarios that the integration should support, such as data synchronization, data transformation, data validation, error handling, etc. The consultant should also determine the scope, frequency, direction, and volume of the data exchange, as well as the security and performance considerations2.

A. Disable Trigger Handler records and C. Use the Data Import Wizard are not valid steps for the initial integration planning. DisablingTrigger Handler records is a step that may be required when installing the Education Data Architecture (EDA) package in an existing Salesforce org, as it can prevent conflicts with existing triggers and workflows3. However, this is not related to the integration with the SIS. Using the Data Import Wizard is a tool that can be usedto import data from external sources into Salesforce, such asaccounts, contacts, leads, etc4. However, this is not a step for the initial integration planning, but rather a possible option for the data migration or loading.

Understanding Licensing Requirements:

Full-time recruitment staff need access to Opportunity and Campaign Member objects, which are part of core Salesforce functionalities.

Salesforce Platform licenses have limitations on access to certainstandard objects such as Opportunities and Campaigns, which are essential for the recruitment use case.

Business Use Case for Full Salesforce License:

Opportunity Management: Recruitment staff need to manage opportunities related to student admissions andengagement.

Campaign Management: Access to Campaign Members allows recruitment staff to track and manage student participation in various recruitment campaigns.

Advanced CRM Functionalities: Full Salesforce licenses provide access to all Salesforce CRM capabilities, which are necessary for comprehensive recruitment operations.

Cost Considerations:

While full Salesforce licenses are more expensive than platform licenses, they provide the necessary functionality without limitations.

Discuss potential volume discounts or bundling options with Salesforce to mitigate costs.

Implementation Steps:

License Assignment: Ensure that full Salesforce licenses are assigned to recruitment staff.

Training: Provide training to recruitment staff on how to effectively useOpportunities and Campaign Members.

Customization: Customize Salesforce to meet specific recruitment needs, leveraging Opportunities and Campaign functionalities.

The consultant should ask about the success metrics for the project to understand the goals and expectations of the Career Services department andhow to measure them. This will help the consultant design a solution that aligns with the department’s vision and needs. Which users need system admin access and what is the estimated project budget are questions that can be asked later in the project planning or execution phase, not during the discovery session. References:

https://trailhead.salesforce.com/en/content/learn/modules/education-cloud-basics/education-cloud-discovery

https://trailhead.salesforce.com/en/content/learn/modules/education-cloud-basics/education-cloud-project-planning

Understanding Account Models inEducation Cloud: Education Cloud typically uses the Administrative Account model to manage relationships and hierarchies between contacts (students, parents, etc.) and accounts (departments, institutions, etc.).

Administrative Account Model: This model allows educational institutions to maintain a structured and organized view of their data, which is essential for managing various relationships and processes within the institution.

Migration Considerations:

Data Mapping: Map existing data fields from theprevious Education Data Architecture (EDA) to the new Administrative Account model.

Customizations: Ensure that any custom objects or fields are compatible with the Administrative Account model.

Testing: Rigorously test the migrated data to ensure integrity and accuracy.

Steps to Implement:

Data Export: Export data from the EDA org.

Data Transformation: Transform the data to fit the Administrative Account model structure.

Data Import: Import the transformed data into the new Education Cloud instance.

Validation: Verify that the data aligns with the Administrative Account model and functions as expected.

Affiliation is an object in EDA that indicates a student’s major or primarycourse of study. Affiliation is an object that represents a relationship between a Contact and an Account or another Contact. Affiliation can be used to track various types of relationships, such as student, faculty, staff, alumni, donor, or advisor. The consultant can create an Affiliation record for each student and associate it with their major or primary course of study. Education History, Relationship, and Program Plan Requirement are not objects in EDA that indicate a student’s major or primary courseof study. References:

https://powerofus.force.com/s/article/EDA-Affiliations

https://powerofus.force.com/s/article/EDA-Affiliations-Mappings

The college should consider that Pathways uses Program Plan and Plan Requirement records when implementing Pathways to support students in their academic journey. Pathways is a feature in Student Success Hub that allows users to create and manage personalized learning plans for students based on their goals and interests. Pathways uses Program Plan and Plan Requirement records to define the structure and requirements of a learning plan, such as courses, credits, or milestones. The college should consider that Pathways uses Program Planand Plan Requirement records when implementing Pathways to support students in their academic journey by configuring and customizing these records to match their academic programs and policies. There is a limit to the number of Plan Requirement records orthere are only two levels of Program Plan requirements in Pathways are not things that the college should consider when implementing Pathways to support students in their academic journey. References:

https://www.salesforce.org/products/student-success-hub/overview/

https://powerofus.force.com/s/article/SSHub-Pathways

Attribute is an EDA object that the consultant should use to meet the requirement of tracking student documentation such as visa, passport, vaccinations, and other information. Attribute is an object that stores additional information about a student or an applicant that is not captured by other EDA objects. Attribute can be used to track various types of information, such as test scores, languages, hobbies, certifications, and documents. Program Plan, Success Team, and Affiliation are not EDA objects that can store student documentation. References:

https://powerofus.force.com/s/article/EDA-Attributes

https://powerofus.force.com/s/article/EDA-Data-Dictionary