You need to configure authentication to access the SQL data source during development. Which authentication mechanism should you use?

Impersonated Windows Identity requires specifying a fixed Windows account whose credentials are stored and used to connect, which is unnecessary overhead during development and introduces credential management complexity.

Pass Through authentication forwards the currently authenticated user's credentials directly to the SQL data source without impersonation or stored credentials. During development, this is the preferred mechanism because the developer's own Windows identity is used to connect, making it easy to test with existing permissions and avoiding the need to configure stored or impersonated accounts.

Impersonated Custom Identity uses a stored username and password for a non-Windows account, which requires additional configuration and is not suited for a development scenario where the developer's own credentials are sufficient.

Forms Based Authentication is used for web application user authentication, not for backend data source connections to SQL Server, making it architecturally incorrect for this scenario.