Which API capabilities does the Salesforce CLI provide?

Which API capabilities does the Salesforce CLI provide?

• A. Tooling API
• B. Metadata API
• C. Data (SOAP) API
• D. ANT migration tool scripting

Answer: (B)

The Salesforce CLI is designed around managing metadata for deployment and source-driven development, and it uses the Metadata API to perform those operations. When you push or pull metadata with the CLI, you’re working with components like custom objects, fields, layouts, Apex classes, validation rules, and other metadata types, all handled through the Metadata API under the hood. The Tooling API exists for certain development tooling and real-time metadata interactions, but it isn’t the primary mechanism the CLI relies on for source-based workflows. The Data (SOAP) API deals with runtime data, not metadata movement, so it isn’t what the CLI uses for managing deployments. ANT migration tool scripting is an older, separate approach that used the Metadata API via Ant; the CLI provides a newer, command-based interface focused on metadata management rather than Ant scripting.

The Salesforce CLI is designed around managing metadata for deployment and source-driven development, and it uses the Metadata API to perform those operations. When you push or pull metadata with the CLI, you’re working with components like custom objects, fields, layouts, Apex classes, validation rules, and other metadata types, all handled through the Metadata API under the hood. The Tooling API exists for certain development tooling and real-time metadata interactions, but it isn’t the primary mechanism the CLI relies on for source-based workflows. The Data (SOAP) API deals with runtime data, not metadata movement, so it isn’t what the CLI uses for managing deployments. ANT migration tool scripting is an older, separate approach that used the Metadata API via Ant; the CLI provides a newer, command-based interface focused on metadata management rather than Ant scripting.