The consultant should use the Course Offering Schedule object in EDA to meet the requirement oftracking the Biology 101 class for next semester that will be held on Tuesdays and Thursdays from 3:00-4:00 PM in Lecture Hall A and on Wednesdays and Fridays from 1:00-2:30 PM in the adjacent lab facility for the university. The Course Offering Schedule object is an object in EDA that allows users to store information about when and where a course offering is held, such as day of week, start time, end time, or location. The Course Offering Schedule object can help the consultant meet the requirement of tracking the Biology 101 class for next semester that will be held on Tuesdays and Thursdays from 3:00-4:00 PM in Lecture Hall A and on Wednesdays and Fridays from 1:00-2:30 PM in the adjacent lab facility for the university by creating two Course Offering Schedule records for the Biology 101 course offering, one for the lecture sessions and one for the lab sessions, and specifying the day of week, start time, end time, and location for each record. Time Block, Program Enrollment, or Course Connection are notobjects in EDA that the consultant should use to meet the requirement of tracking the Biology 101 class for next semester that will be held on Tuesdays and Thursdays from 3:00-4:00 PM in Lecture Hall A and on Wednesdays and Fridays from 1:00-2:30 PM in theadjacent lab facility for the university. References:
https://powerofus.force.com/s/article/EDA-Course-Offering-Schedules
https://powerofus.force.com/s/article/EDA-Course-Offerings

The Household Account Model in EDA creates one account for each household and associates multiple contacts with that account. This model is suitable for tracking students' families and communicating with the parents on issues. The Household Account Model also provides features such as automatic household naming, address management, and rollup fields. The consultant should recommend thismodel for the primary school that will implement Student Success Hub. References: [Salesforce Education Cloud Academy: Consultant Fundamentals], [EDA Account Models]

The consultant should recommend to disable address-related Trigger Handler records for the university thatuses EDA to manage its prospective and current students and has the student Contact Mailing Address fields and records populated in Salesforce through an integration with an external system. Trigger Handler records are records that control the behavior ofEDA triggers and can be disabled or enabled as needed.
Disabling address-related Trigger Handler records can help prevent duplicate or conflicting address records from being created or updated by EDA when the student Contact Mailing Address fields and records are populated in Salesforce through an integration with an external system. Disabling all EDA and custom Trigger Handler records, setting record-level trigger firing based on the Account record type, or setting the Default Account Model to Administrative are not recommendations for the university that uses EDA to manage its prospective and current students and has the student Contact Mailing Address fields and records populated in Salesforce through an integration with an external system. References:
https://powerofus.force.com/s/article/EDA-TDTM
https://powerofus.force.com/s/article/EDA-Addresses

Nonprofit Success Pack (NPSP) is a solution that the consultant can recommend to meet the requirement of extending EDA org to support fundraising needs. NPSP is built on top of EDA and provides features such as donations management, gift processing, donor engagement, and reporting. Gift Entry Manager, Giving Pages, and Elevate are not solutions that can extend EDA org to support fundraising needs, but rathertools that can work with NPSP to enhance the fundraising experience. References:
https://www.salesforce.org/education/education-cloud-for-advancement/
https://www.salesforce.org/nonprofit/nonprofit-success-pack/

The consultant should verify that trigger handlers were loaded into production when troubleshooting the issue of only the contact record being created when a contact record is created and a Community user is supposed to be created leveraging Table-Driven Trigger Management (TDTM) for the school that is implementing Salesforce with EDA to track parents and students in a community. Trigger handlers are classes that contain the logic for EDA triggers and can be controlled by Trigger Handler records. Trigger handlers need to be loaded into production before deploying declarative customizations or enabling features that depend on them.
The consultant should verify that trigger handlers were loaded into production by checking if the EDA_TDTM package was installed or if the Trigger Handler records were created. The community being set to Active or declarative automations being deployed successfully are not steps that the consultant should verify when troubleshooting the issue of only the contact record being created when a contact record is created and a Community user is supposed to be created leveraging TDTM for the school that is implementing Salesforce with EDA to track parents and students in a community. References:
https://powerofus.force.com/s/article/EDA-TDTM
https://powerofus.force.com/s/article/EDA-Installation