What is the N+1 query problem in Entity Framework Core and how is it typically resolved?
-
A
Loading a collection triggers one query per item; resolved by using .Include() for eager loading
-
B
The application makes N database connections before the first result; resolved by connection pooling
-
C
Queries run N times per second before scaling kicks in; resolved by adding more instances
-
D
The ORM generates N redundant indexes; resolved by running a migration