Explanation/Reference:
Explanation:
Box 1: Table-per-type: 3
Table per Type is about representing inheritance relationships as relational foreign key associations. Every class/subclass that declares persistent properties-including abstract classes-has its own table. The table for subclasses contains columns only for each noninherited property (each property declared by the subclass itself) along with a primary key that is also a foreign key of the base class table. This approach is shown in the following figure:

Box 2: Table-per-hierarchy: 1
Table-per-hierarchy (TPH) inheritance uses one database table to maintain data for all of the entity types in an inheritance hierarchy.
Box 3: Table-per-concrete class: 2
In Table per Concrete type (aka Table per Concrete class) we use exactly one table for each (nonabstract) class.
Vehicle is an abstract class, while car and sportscar and nonabstract classes.
References:
https://weblogs.asp.net/manavi/inheritance-mapping-strategies-with-entity-framework-code-first-ctp5-part-
1-table-per-hierarchy-tph
https://msdn.microsoft.com/en-us/library/jj618292(v=vs.113).aspx