The consultant should discuss with the Recruitment office that EDA requires custom automation for lead conversion as a compatibility consideration for using Pardot and Salesforce with EDA. Lead conversion is a process that converts a Lead record into an Account, a Contact, and an Opportunity record in Salesforce. EDA does not support the standard lead conversion process in Salesforce, because it uses different account models and objects to store information about individuals and organizations. The consultant should create custom automation for lead conversion, such as using Process Builder, Flow, or Apex, to map the Lead fields to the appropriate EDA fields and objects. Pardot being incompatible with the Household account model, the Do Not Contact TDTM record needing to be disabled, or Pardot beingable to create only Leads and Contacts are not compatibility considerations for using Pardot and Salesforce with EDA. References:
https://powerofus.force.com/s/article/EDA-Lead-Conversion
https://trailhead.salesforce.com/en/content/learn/modules/pardot-basics

Accounting Subledger is a solution that allows education institutions to synchronize fundraising data between Advancement and Finance departments. It enables them to create accounting-ready summaries of donations and other transactions from Salesforce and export them to their accounting systems1. This solution can help the college avoid manual data entry, reduce errors, and streamlinethe allocation of donations. References: Salesforce Education Cloud Academy: Consultant Fundamentals, [Accounting Subledger Overview]

The consultant should use a custom index to resolve the issue oftaking a long time to search and generate list views for the large online university's Salesforce environment that has a large volume of records and uses EDA. A custom index is a feature that allows users to create an index on a field that is not indexed by default, such as a custom field, a long text area field, or a multi-select picklist field. A custom index can help improve the performance and speed of queries and list views that use the indexed field as a filter. The consultant should identify the fields that are frequently used in searches and list views, and request Salesforce Support to create a custom index on them. MuleSoft Anypoint Platform, Data Loader error logs, and Table-Driven Trigger Management are not features that can resolve the issue oftaking a long time to search and generate list views for the large online university's Salesforce environment that has a large volume of records and uses EDA. References:
https://help.salesforce.com/s/articleView?id=sf.customize_index.htm & type=5
https://developer.salesforce.com/docs/atlas.en-us.salesforce_large_data_volumes_bp.meta
/salesforce_large_data_volumes_bp/ldv_deployments_infrastructure_indexes.htm

The consultant should recommend Pathways for the academic advisor to review the classes associated with the student's course of study and ensure the student is on track for graduation. Pathways allow advisors to create and monitor academic plans for students based on their program requirements and course offerings.
Academic Program is an object that defines the program of study that a student is enrolled in, but it does not show the classes or progress. Affiliation is an object that tracks the relationship between a Contact and anAccount, such as a student and a school, but it does not show the classes or progress. References:
https://help.salesforce.com/s/articleView?id=sf.ssh_pathways.htm & type=5
https://help.salesforce.com/s/articleView?id=sf.ssh_academic_program.htm & type=5
https://help.salesforce.com/s/articleView?id=sf.ssh_affiliation.htm & type=5

After installing EDA, the consultant needs to make the EDA record types available to profiles that need to accessthem. This is because EDA comes with several custom record types for standard objects, such as Account, Contact, Course, and Program Enrollment. These record types enable different views and fields for different types of records, such as Household, Student, Faculty, Course Offering, and Program Enrollment. By default, these record types are not assigned to any profiles, so the consultant needs to manually assign them to the appropriate profiles based on the business requirements and user roles of the university. This will ensure that the users can see and use the EDA record types and fields correctly and efficiently. References: Education Data Architecture Basics, Assign Record Types to Profiles