A.  

Generate a destructivechanges.xml file and deploy the package via the Force.com Migration Tool

B.  

Perform deletes manually in a sandbox and then deploy a Change Set to production

C.  

Assign business analysts to perform the deletes and split up the work between them

D.  

Delete the components in production and then refresh all sandboxes to receive the changes

A.  

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

B.  

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

C.  

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

D.  

Contact support to roll back the release when Salesforce upgrades the sandboxes,

A.  

Make all code/configuration changes directly in the production org.

B.  

Allow no code/configuration changes directly in the production.org

C.  

Use the Force.com IDE to automate deployment to the production.org

D.  

Use Metadata API to automate deployment to the production.org

A.  

Using Lightning Web Components for every user interface.

B.  

Adopting user centered design to understand user needs before building the solution.

C.  

Stop development until current features start being used.

D.  

Sending weekly communication emails reporting on least engaged users

A.  

Present the feature requests at a Center of Excellence meeting.

B.  

Create design standards around the new features being requested.

C.  

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

D.  

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

E.  

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

A.  

Unit Test

B.  

Stress Test

C.  

Load Test

D.  

Performance Test

A.  

Include automated sample data during deployment.

B.  

Advise the project manager to assign more users to create test data.

C.  

Test data creation is outside the scope of continuous integration.

D.  

Train business users to create test data more efficiently.

A.  

Spin off a partial copy sandbox using a sandbox template with all the objects required for testing the integration.

B.  

Spin off a Developer pro sandbox, migrate the metadata and load the data using data loader.

C.  

Spin off a full copy sandbox with all the objects that are required for testing the integration.

D.  

Spin off a Development sandbox, migrate the metadata and load the data using data loader.

A.  

Improving team development and collaboration.

B.  

Eliminating the need of using change set, which should no longer be used as it can get messy working with package development models.

C.  

Facilitating automated testing and continuous integration.

D.  

Significantly reducing the need for manually tracking changes.

E.  

Providing its own source control, so the source can be deployed In any sandbox orgs.

A.  

Identify metadata dependencies, create logical groupings, and deploy in the right order.

B.  

Use a continuous integration tool such as Jenkins to deploy in the right order.

C.  

Sort and group the metadata alphabetically and deploy them in the same order.

D.  

Use a combination of the Ant migration tool and change sets for deployment.

A.  

Requesting feedback for outstanding architectural questions

B.  

Consistent communication to a pre -defined list of stakeholders

C.  

Reporting project status, timelines, and impacts

D.  

Communication to stakeholders on a "need -to -know" basis

A.  

Script the deployment of all functionality via the Force.com Migration Tool

B.  

Manually deploy and populate custom settings in production using a change set

C.  

Create a custom metadata type and include this in your deployment to production

D.  

Manually deploy and populate the custom settings in production prior to theApex Class deployment

A.  

Install an Aloha certified App

B.  

Upgrade to an Enterprise Edition org

C.  

Create and install an unmanaged package

D.  

Buy more user licenses to increase org limits

A.  

Utilize Heroku Connect to provide test class data.

B.  

Host a mock endpoint to produce sample information from an endpoint.

C.  

Reference data from middleware directly within your test class.

D.  

Load a CSV as a static resource and reference it in a test class.

A.  

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.

B.  

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

C.  

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

D.  

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

A.  

Deploy up to 10,000 files, but retrieve more than 10,000 files.

B.  

Maximum size of deployed .zip file is 400M

B.  

C.  

Maximum Size of deployed .zip file is 39MB.

D.  

Deploy and retrieve up to 10,000 files at once.

A.  

Partial copy Sandbox.

B.  

Developer Sandbox.

C.  

Full Sandbox

D.  

Developer Pro Sandbox.

A.  

Force.com Migration Tool

B.  

Full Sandbox Environment

C.  

Source Control Tool

D.  

Project Management Tool

E.  

Continuous Integration Build Tool

A.  

All changes including hotfixes should be reviewed against security principles.

B.  

Any production change should have explicit stakeholder approval.

C.  

No manual steps should be carried out.

D.  

After deployment, the development team should test and verify functionality in production.

A.  

Apex Settings to allow the access to metadata is not switched on.

B.  

UC needs to turn on Apex Settings within the custom metadata type.

C.  

The solution is flawed. UC should utilize the Tooling API from a web service call to modify the layouts.

D.  

UC needs to get the managed package certified by the Salesforce security review.

A.  

No manual tracking required. All changes are automatically tracked.

B.  

All metadata changes for the release.

C.  

Changes to components not yet supported by source tracking.

D.  

Only the changes made via the Setup UI.

A.  

Developer Edition

B.  

Partner Developer Edition

C.  

Developer sandbox

D.  

Developer Pro sandbox

A.  

Create a change set in each sandbox and download the package.xml file for the release management team

B.  

Provide a spreadsheet of all components and utilize the metadata API's read Metadata call

C.  

Provide the Release Management team a copy of the audit trail from the sandbox you wish to deploy from

D.  

Send a package.xml file with associated metadata in a .zip file to the Release Management team

A.  

Sandboxes should be refreshed on the day when the refresh is allowed for that type of sandbox.

B.  

Production is the only pristine environment.

C.  

Integration sandboxes should be refreshed rarely because of the burden of maintaining the various API.

D.  

Development environments should generally be refreshed after each working feature has been successfully migrated.

A.  

Escalate and communicate to stakeholders the risk and mitigate it by allocating additional resources to support the new requirement based on stakeholders’ input.

B.  

Have a discussion with the business subject Matter Expert and communicate that the Salesforce has limitations in supporting such a feature to mitigate the risk.

C.  

Escalate and communicate to stakeholders the risk and mitigate it by extending the timeline of the project to support the new requirement based on stakeholders’ input.

D.  

Have a discussion with the business subject Matter Expert and communicate that anew developer environment will be needed to mitigate the risk.

A.  

Change Sets cannot be automated.

B.  

Change Sets cannot be validated before deployment

C.  

Change Sets cannot be used for orgs affiliated with same production org.

D.  

Change Sets cannot be rolled back.

E.  

Change Sets cannot be reused between Production Salesforce orgs.

A.  

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.

B.  

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

C.  

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

D.  

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

A.  

Execute test classes under various profiles

B.  

Test classes should not create custom setting data.

C.  

Test classes must use existing data in the environment.

D.  

Test data must have positive as well as negative data.

A.  

Request a partial Sandbox copy after the next Salesforce release.

B.  

Generate mock data that mimics production data shape and volume.

C.  

Perform data masking on full sandbox after a refresh.

D.  

Use Query Analyzer in production.

A.  

Automated loads can be done with no human oversight.

B.  

FRED Automated loads are reliable in their results.

C.  

Automated loads cannot be scripted by CICD tools.

D.  

Automated loads will increase costs.

A.  

Recommend using the Continues integration and the Continues deployment tool and build the pipeline to deploy to sandboxes and production.

B.  

Recommend using SFDX and documents the deployment commands with steps to be executed for each environment.

C.  

Recommend using the ANT script and build a custom application to run the script and use change sets to deploy supported metadata.

D.  

Recommend using an AppExchange solution that packages the deployment components and you can run the deployment wizard to track deployment result.

A.  

Use test.startTest() and test.stop Test() methods to reset governor limits.

B.  

Use an AppExchange product which can temporarily increase the governor limits.

C.  

Use the auto reset property to automatically reset governor limits during off-hours.

D.  

Use test.setLimit() and test.resetLimit() methods to reset governor limits.

A.  

Executive Leadership

B.  

Requirements Traceability Matrix

C.  

Business Continuity Plan

D.  

Agile Methodology

A.  

A Do not execute any test classes in sandboxes and production.

B.  

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

C.  

Test classes cannot be executed in sandboxes.

D.  

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

A.  

Cross-site scripting

B.  

CRUD/FLS (field level security)

C.  

Session hacking

D.  

SOQL injection

A.  

Create two second generation managed packages with the same namespace and set the methods that should be shared with the @namespaceAccessible annotation.

B.  

Create two managed packages with Sales and service namespaces. Set the methods to be shared with the ©salesAccessible annotation

C.  

Create a managed package with both products and create a code review process with an approver from each team.

D.  

Create two managed packages. Create an authentication function in the Service package that will return a token if a Sales user is authorized to call the exposed function. Validate the token in the Service functions.

A.  

Create separate branches for current development and production bug fixes and deploy the fix with current development when ready

B.  

Utilize one branch for both development and production bug fixes to avoid out-of-sync branches and simplify deployment

C.  

Utilize a source control system to allow separate branches for current development and production bug fixes

D.  

Refresh a sandbox for replication of the issue and testing the use -case scenarios once the code is fixed

A.  

Use a third-party data warehouse.

B.  

Remove the executive’s ability to change reports, and only allow developers to do that.

C.  

Ensure report metadata is exported daily and that it is merged into the developer branches before the next release.

D.  

Back up all the reports just before the release, then reimport them after the release,

A.  

Introduce manual code review before deployment to the testing sandbox.

B.  

Introduce manual code review before deployment to the production org.

C.  

Increase the size of the testing team assigned to the project.

D.  

Introduce static code analysis before deployment to the testing sandbox.

A.  

Existing Apex test classes may start falling in Production.

B.  

Implement the change in the sandbox, validate, and release to Production.

C.  

The change can be performed in Production, as it is a configuration change.

D.  

Integration with the ERP system may not function as expected.

A.  

Opt for Multi-org strategy, standardized sales process, common rules, and same locale across orgs.

B.  

Opt for Single-org strategy, standardized sales process, common rules, and same locale for all business units.

C.  

Opt for Single-org strategy, standardized sales process, common rules, and business unit-specific locale

D.  

Opt for Multi-org strategy, each org have its own sales process, and common rules and operate in locale

A.  

Deny the suggestion and explain to everyone that the risk is too high and the next release window is on the weekend.

B.  

Pair with the administrator, and review each change as it happens

C.  

Explain that only developers are certified to make changes directly in production.

D.  

Call the security team and begin organizing d penetration test.

A.  

Facilitate the design of a prioritization model with the stakeholders.

B.  

Organize a sprint planning meeting with the Scrum team.

C.  

Take over prioritization for the stakeholders.

D.  

Allow the delivery teams to pick the best work for the business.

A.  

Deploy unsupported components manually before/after deployment.

B.  

Use AppExchange products to deploy unsupported components.

C.  

Use change sets for deploying all the unsupported components.

D.  

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

A.  

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.

B.  

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.

C.  

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.

D.  

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.  

Whether to create a new Salesforce object or override an existing object using a new Record Type

B.  

Whether to utilize the Waterfall or Agile methodology on the project

C.  

What testing tools should be used to track integration testing requirements

D.  

Whether to implement Single Sign -On with SAML or delegated authentication

A.  

Eclipse IDE

B.  

Unmanaged Package

C.  

Change Sets.

D.  

Managed Package

A.  

Choose the most senior developer to help the technical lead in the code review.

B.  

Create development standards and train teams in those standards.

C.  

Skip the code review and focus on functional tests and UAT.

D.  

Use static code analysis tool in the pipeline before manual code review.

A.  

Let UAT point to production integrations and rollback each transaction after it finishes.

B.  

Delete all the data and use an Automated testing tool to create new data across all the systems in UAT.

C.  

Mask the External Id so nobody can see the production value.

D.  

In the post refresh plan, modify external ids to a known valid set of values for UAT.

A.  

How to test existing functionality to ensure no regressions are introduced.

B.  

Whether Salesforce will wait to upgrade the pod until after a UC release is complete.

C.  

How to roll back to the previous Salesforce release if there are issues.

D.  

When to test a new UC feature release if there are issues.

A.  

Provide the ability for distributed teams to work in isolation.

B.  

Provides automated code/configuration deployments.

C.  

Provides the ability to backup code/configuration changes.

D.  

Provides the ability to automatically identify issues in code/configuration.

A.  

There is no problem, this is expected behavior.

B.  

UAT is on a preview release and SIT is not.

C.  

SIT is on a preview release and UAT is not.

D.  

Use the DX command line instead.

A.  

Ensure all code that is being deployed is checked into source control

B.  

Validate the final deployment package against production prior to go-live

C.  

Create a new sandbox and perform a test deployment to that environment

D.  

Upload a change set from sandbox to production as early as possible

A.  

Communicate project status

B.  

Determine project methodology

C.  

Design executive dashboards

D.  

Approve changes to project scope

A.  

Courage, because the teams should be transparent about progress and speak up when they need help.

B.  

Openness, because the team is not open to a new methodology.

C.  

Focus, because the teams are not focusing in the agile process expected activities.

D.  

Commitment, because the team is not committed to follow the Agile methodology.

A.  

Design the right sandbox strategy for the release.

B.  

Release sign-off is only required for Production.

C.  

Regression testing is mandatory for each release.

D.  

Maintain a pre/post deployment checklist for each release.

E.  

Publish a release calendar for each phase of the release.

A.  

Workbench

B.  

Force.com Migration Tool

C.  

Change Sets

D.  

Force.com IDE

A.  

Ensure that Record Type IDs match both Production and Sandbox orgs

B.  

Ensure executed Apex test run as valid users

C.  

Ensure unit tests generate their own test data

D.  

Ensure unit tests execute with see AllData=true

A.  

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

B.  

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

C.  

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

D.  

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

A.  

Add the service centers to a hierarchical custom settings.

B.  

Add the service centers to a list custom settings.

C.  

Define a brand-new custom object with a picklist field to host all of the service centers.

D.  

Add all of the service centers to a custom metadata type.

A.  

Have all developers build new functionality in new branches, but fix bugs in the HEAD

B.  

Have all developers work in the same branch, continuously testing for regressions

C.  

Have developers work in separate branches and merge their changes in a common branch for testing

D.  

Don't use source control. Rely on Salesforce's built-in conflict detection mechanism

A.  

Refresh the developer's sandbox, develop changes, refresh the common sandbox, deploy to the common sandbox, test changes

B.  

Refresh the developer's sandbox, develop changes, test changes, refresh thedeveloper's sandbox, deploy to the common sandbox

C.  

Refresh the developer's sandbox, develop changes, refresh the developer's sandbox, deploy to the common sandbox, test changes

D.  

Refresh the common sandbox, develop changes, refresh the developers and box, deploy to the common sandbox, test changes

A.  

Authorize to the Full sandbox org; Validate with sfdx:source:deploy; On successful validation, deploy with sfdx:source:deploy

B.  

Authorize to the Fullsandbox org; Validate with sfdximdapi:deploy; On successful validation, deploy with sfdx:mdapi:deploy

C.  

Authorize to the Full sandbox; validate with sfdx: source: deploy; On successful validation, deploy with sfdx;mdapi;deploy

D.  

Authorize to the Full sandbox org; Validate with sfdx:mdapi:deploy; On successful validation, deploy with sfdx:source:deploy