Microsoft SQL Server — Authentication Modes Which authentication mode is NOT offered by SQL Server for client connections?

Introduction:
Authentication modes control how users and applications prove their identity to SQL Server. Knowing the supported modes is essential for secure deployments and compliance with organizational standards.

Given Data / Assumptions:

• SQL Server integrates tightly with Windows security.
• SQL Server also supports its own logins when configured appropriately.
• The question asks which mode is not provided.

Concept / Approach:
SQL Server supports two modes: Windows Authentication mode and Mixed Mode. Windows Authentication mode accepts only Windows principals. Mixed Mode accepts both Windows logins and SQL Server logins. There is no configuration that allows only SQL Server logins while excluding Windows accounts entirely.

Step-by-Step Solution:
1) Identify supported modes: Windows Authentication, Mixed Mode.2) Evaluate options against supported modes.3) Conclude that “SQL Server only security” is not a valid mode.

Verification / Alternative check:
During setup or via server properties, administrators can toggle between Windows Authentication and Mixed Mode only.

Why Other Options Are Wrong:

• Windows-only security: This is Windows Authentication mode, fully supported.
• Both SQL Server and Windows-only security / Mixed security: These both describe Mixed Mode, which is supported.
• Kerberos-only without Windows accounts: Kerberos operates within Windows domain auth and is not a separate SQL-only mode.

Common Pitfalls:
Assuming there is a “SQL Server only” mode; SQL logins require Mixed Mode, which still allows Windows logins.

Final Answer:
SQL Server only security