A Salesforce DX project includes which of the following?

A Salesforce DX project includes which of the following?

• A. Contains only Salesforce DX configuration files
• B. Is an exact copy of your development sandbox
• C. Does not have to be checked into source control
• D. Contains your source and Salesforce DX configuration files.

Answer: (D)

A Salesforce DX project is a portable, source-driven repository that holds both the actual metadata (source) and the DX-specific configuration needed to build, organize, and deploy that metadata across scratch orgs and environments. The right choice reflects this by containing your source and Salesforce DX configuration files. The source includes metadata components like Apex, objects, Lightning components, and other metadata you develop or modify, while the DX configuration includes files such as the project manifest and settings (for example, sfdx-project.json and related DX setup). This combination enables consistent source-driven development, easy sharing, and reliable deployments. Why the other options aren’t correct: a project isn’t limited to configuration files only, since it also stores the actual metadata you develop. It's not an exact clone of a development sandbox, because a DX project is a portable representation of your source and configuration, not a sandbox snapshot. And while you could keep a DX project elsewhere, best practice is to check it into source control to track changes, enable collaboration, and integrate with CI/CD.

A Salesforce DX project is a portable, source-driven repository that holds both the actual metadata (source) and the DX-specific configuration needed to build, organize, and deploy that metadata across scratch orgs and environments. The right choice reflects this by containing your source and Salesforce DX configuration files. The source includes metadata components like Apex, objects, Lightning components, and other metadata you develop or modify, while the DX configuration includes files such as the project manifest and settings (for example, sfdx-project.json and related DX setup). This combination enables consistent source-driven development, easy sharing, and reliable deployments.

Why the other options aren’t correct: a project isn’t limited to configuration files only, since it also stores the actual metadata you develop. It's not an exact clone of a development sandbox, because a DX project is a portable representation of your source and configuration, not a sandbox snapshot. And while you could keep a DX project elsewhere, best practice is to check it into source control to track changes, enable collaboration, and integrate with CI/CD.