Free and Premium Salesforce Development-Lifecycle-and-Deployment-Designer Dumps Questions Answers

Can store code on a local machine, or a version control system.

Can quickly deploy metadata using Execute Anonymous.

Can create scratch orgs.

Can use native Deployment Rollback Tool to quickly revert to prior state.

Can Install application metadata from a central repository.

Automated loads can be done with no human oversight.

FRED Automated loads are reliable in their results.

Automated loads cannot be scripted by CICD tools.

Automated loads will increase costs.

Create an adoption plan for end users using Salesforce dashboards and reports.

Create a design standard requiring integration to use declarative configurations patterns

Create a governance process requiring all projects to create project deliverable documentation.

Create a standard method for deprecating classes and fields using design standards.

Create a governance framework focused on high-level business strategy and goals.

Single-org strategy, as the high level of business process standardization will be easier to implement in a single org.

Multi-org strategy, as it is uncommon for the diversified business units to get used to working in the same space as the other business units.

A Multi-org strategy, as they could deploy a common managed package into the orgs of the different business units.

Single-org strategy, as costs increase as the number of orgs go up.

Partial Copy sandbox

Developer sandbox

Full sandbox

Developer Pro sandbox

Use an Excel sheet to track deployment steps and document the SFDX commands.

Use an AppExchange or third-party tool that is specialized in Salesforce deployment.

Use ChangeSet to track deployed customizations.

Use Salesforce SFDX commands to deploy to different sandboxes.

In change sets, external objects are included in the custom object component.

In the Metadata API, the External Object metadata type represents external objects.

In change sets, external objects are included in the External Object component.

In the Metadata API, the Custom Object metadata type represents external objects.

Continue with the current approach, since Salesforce will rectify the issue prior to updating the production environment to the new platform release

Continue development in a non -upgraded sandbox, and have the developer update the API version of the code to the upcoming API version for testing purposes

Submit a request to Salesforce to enable the 'delay upgrade' feature in their org. Have the UC administrator schedule the upgrade for a later date

Determine the developer sandbox upgrade schedule, and have the developer refactor the approach to the feature in the upgraded sandbox

Waterfall, because it defines a fixed schedule and duration for each activity.

DevOps, because monitoring and logging practices help you stay informed of performance in real time.

Scrum, because openness is one of the five core Scrum values.

Kanban, because oneof its basic elements is to make everything visible, creating consistent transparency of work items

Use continuous integration with automation testing.

Encourage the development team to be self-organizing.

Enable developer teams to do peer code review.

Incorporate test-driven deployment into the project structure.

Enable a short and timely feedback loop with customers

Present the feature requests at a Center of Excellence meeting.

Create design standards around the new features being requested.

Bring the feature request to the Test Manager to gain quality checks.

Create the backlog or priority list in a project management tool.

Send the requests to IT for a formal review at the end of the year.

Review the Checkmarx errors. If there is no need to fix, mark them as false positive and

attach explanation, then submit.

Leave them to the Salesforce security review team, they would catch it if those are true

problems.

Leavee a partner support case, the partner manager will engage Salesforce support

resources to help.

Review the Checkmarx errors and fix all of them before submitting security review.

Salesforce security review team will reject the request if any error remains.

The first task of the new sprint must be the deployment approval. After that, the other tasks of the sprint can be performed in the environments and Git.

Using Git, create a release branch from the develop branch. All fixes must be made in the release branch. After deployment, merge release with develop.

Commit upcoming changes to the features branch without merging into the develop branch. Deploy from the develop branch and then merge new sprint features into the develop branch.

Migrate the current code to the UAT sandbox. Begin new sprint development in the Dev sandbox. Make fixes in the UAT environment and deploy UAT for production after business approval.

A Do not execute any test classes in sandboxes andProduction.

Do not execute test classes in sandboxes and all test classes in Production.

Test classes cannot be executed in sandboxes.

Execute all test classes in sandboxes and selected test classes in Production.

If the username in the source org doesn't exist in the target org, the deployment will continue and Salesforce will automatically create the username in the target org.

User fields are ignored during metadata deployments and all such users need to be manually created in the target org before starting the deployment.

If the username in the source org doesn't exist inthe target org, the deployment will stop until the usernames are resolved or removed.

User Fields are preserved during metadata deployments and Salesforce attempts to locate a matching user in the target org during deployment.

JSTEST

ACCTEST

WebDriver Test

AuraDriver Test

To run a subset of tests, set the Run Specified Tests test level on the DeployOptions objects and pass it as an argument to deploy() call.

run a subset of tests ,setthe RunLocalTests test level on the DeployOptions object and pass it as an argument to deploy() call.

Specify both test classes and individual test methods that are required to be executed as both are supported in DeployOptions.

Specifying the testmethod is supported in DeployOptions, therefore specify only the test classes that are required to be executed.

Leaf-based development

Trunk-based development

GitHub flow

Scratch-org-based development

Use a Change Set to deploy the changes from Production to the sandbox, to ensurethat changes made in production are reflected in the sandbox that the developers are working on

Use Salesforce-to-Salesforce to deploy the changes from Production to the sandbox, to ensure that changes made in production are reflected in the sandbox that the developers are working on

Manually replicate the same changes in the developer sandbox to ensure that changes made in production are reflected in the sandbox that the developers are working on

Refresh the developer sandbox to ensure that changes made in production are reflected in the sandbox that the developers are working on

Develop the functionality in a sandbox and deploy it to both production orgs

Set up Salesforce-to-Salesforce to deploy the functionality from one org to the other

Create a managed package in a sandbox and deploy it to both production orgs

Create a package in a Developer Edition org and deploy it to both production orgs

Perform CRUD operations o manage records in the organization.

Migrate configuration changes between two organizations.

Migrate data changes between two organizations using a csv file.

Export current customization in the organization as an xml file.

The testing of the JavaScript part of the Aura component can be tested in the Jest framework and the Apex controllers can be tested using test classes.

Install the Lightning test service AppExchange package to enable the Aura component testing.

There is a $T test helper object that can be used to create the instance of the Lightning component, and it is promise enabled.

The testing can be viewed inthe lightning.force.com/c/jasminetests.app URL. The page loads and runs Jasmine test and writes pass/fail information to the screen.

Minor changes do not need to be documented and can be made at any time.

Minor changes should be thoroughly documented and follow some type of standard cadence.

Allchanges should still be tested.

CI/CD is required in to successfully manage minor changes.

Downstream environments will not be automatically updated when production changes.

Hirea company specialized in secure code review the current code.

Implement a pull request and secure code review.

Integrate a static code security analysis tool in the CI/CD process.

Use two developers to review and fix current code vulnerabilities.

Install an Aloha certified App

Upgrade to an Enterprise Edition org

Create and install an unmanaged package

Buy more user licenses to increase org limits

UC should spin up a new sandbox to use as a hot fix environment. Once the bug is

corrected, the change should beapplied to production and downstream environments.

The fix should be made in the developer environment where the project work was done.

Once the fix has been made, it should go through a full deployment/testing process and

adhere to the normal projectcadence.

Since the issue was found in production, it should be treated as a change request and go

into the backlog as an enhancement.

Correcting the bug in UAT is ideal. Since UAT is a full copy, it will be the fastest

location to fix and test the resolution.

Create Design standards to require help text on all custom fields and custom objects.

Create Design standards to consistently use thedescription field on custom objects.

Create Design standards with a document to store all custom objects and custom fields

Create Design standards to require all custom fields on all custom object page layouts

Create Design standards to consistently use the description field on custom fields.

Developer Pro Sandbox Org

Partner Developer Edition Org

Production Org with LMA

Developer Edition Org

Store the records in sandboxes and production.

Store the records in a version control system.

Use a third-party product to manage these records.

Attach CSV files to the user stories in a project management system.

Perform code reviews before promoting to a pre -production sandbox

Automatically deploy changes from sandbox to production

Keep a history of changes made by each developer

Create a branching strategy that tracks each feature or change separately

Act as a backup in case of catastrophic data loss

Refresh all non-preview sandboxes during the release preview window.

Refresh all non-preview sandboxes when the release management team has time.

No advice needed, mixing instance types is important for regression testing.

Contact support to rollback the release when Salesforce upgrades the sandboxes,

Deploy unsupported components manually before/after deployment.

Use AppExchange products to deploy unsupported components.

Usechange sets for deploying all the unsupported components.

Use the force.com IDE for deploying the unsupported components.

Require developers to deploy completed code and unit tests directly to production

Deploy all functionality together to ensure all functionality works together without error

Use a spreadsheet to track approved changes that should be released with change sets

Utilize automated source control, test, and build systems to test and deploy to production