Development-Lifecycle-and-Deployment-Designer Salesforce Certified Development Lifecycle and Deployment Architect (WI23) Questions and Answers

Org development model, because the acquired company's team is already using it, and it is better than the change set development model.

Package development model, because it allows packages to be created and deployed using declarative (point-and-click) development tools, without writing code.

Package development model, so teams can build release artifacts that can be tested and released independently from artifacts for other projects.

Change set development model,because UC is already using it, so it will face less resistance.

It appears the org is using more sandboxes than the license permits. The Partial Copy sandbox shouldn't be used.

Create a Salesforce support case, someone shouldknow what is wrong.

Contact the Salesforce Account Team to do a sandbox License Count.

Delete the full sandbox used for performance testing.

Developer Pro Sandbox

Partial Copy Sandbox

Developer Sandbox

Full Sandbox

Utilize the major release process to create the report directly in production bypassing the full sandbox.

Utilize the minor release process to create the report directly in production bypassing the full sandbox.

Utilize the major release process to create the report in a full sandbox and then deploy it to production.

Utilize the daily release process to create the report directly in a full sandbox and then deploy it to production.

Zip file deployable by Force.Com Migration Tool.

Unmanaged Package.

Change Sets.

Managed Package.

Refresh the full sandbox after every deployment in production.

Create a daily process of copying new and changed data in production to the full

sandbox.

Before any deployment in production, the same process must be performed in this

sandbox.

Perform a Refresh Data in the full sandbox.

Minor releases use Partial copy and Major releases use Full copy

Minor and Major releases use separate Developer pro

Minor releases use Developer and Major releases Full copy

Minor and Major releases use same Full copy.

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

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

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

Refresh the common sandbox, develop changes, refresh the developersandbox, deploy to the common sandbox, test changes

Change sets

Unmanaged package

Managed package

Zip file deployable by SFDX or ANT

Introduce manual code review before deployment to the testing sandbox.

Introducemanual code review before deployment to the production org.

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

Introduce static code analysis before deployment to the testing sandbox.

Mock can also be used on the classes that extendthe batchable interface to bypass the batch jobs.

Using a Mock allows the test class to bypass the dependencies of other objects, methods, state, or behaviors. Therefore, the developer has total control of his own code.

Some methods are invoking long running processes, using Mock is a shortcut of bypassing the long executions.

A Mock is needed whenever the code makes an HTTP callout.

CustomMetadataType

CustomMetadata

CustomObject

Custom Field

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

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

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

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

Continuous Integration

Develop

Build Release

Test

Change Sets

The deadline is scheduled during a Salesforce release

The project team has decided to use the Waterfall methodology

The legacy system team is using an Agile methodology

Multiple work -streams with dependencies could impact the go-live

Implement a Complete Graphmulti-org strategy by allowing each org to connect directly to every other, reading and writing customer data

from the orgs where it has been originally created.

Migrate from multi-org to single-org strategy, consolidating customer data in the process.

Implement a Single Package multi-org strategy by developing and deploying to all orgs a managed package which reads and consolidates

customer 360-degree view from the different orgs.

Implement a Hub-and-Spoke multi-org strategy by consolidating customer data In a single org, which will be the master of customer data,

and using integration strategies to let the LOBs orgs read and write from it.

Ask the second work stream team to work on the same DevProl sandbox.

Clone the DevPro1 sandbox and name It DevPro2 for the second work stream to work on the Service Cloud requirements.

Push back on the requirements becauseadding another work stream will bring some risks with it.

DevPro1 cannot be cloned because it is on a different version from Production. Just create a new DevPro2, and migrate metadata from DevPro1.

Change set performance is independent of included components.

Manually createnew custom objects and new custom fields.

Manually apply the field type changes.

Manually validate change sets before deployment.

The test script should be used to define the test classes.

The code coverage should be increased to 95%.

The test analyst who creates thetest plan must also create the test classes.

The acceptance criteria should have more details.

Export all data from objects/fields of the managed package, uninstall it, install the

unlocked package with the same namespace as the Managed package and restore all data.

Export all data from objects/fields of the managed package, uninstall it, install the

unlocked package without namespace and restore all data.

Do not change to unlocked package as it is possible to perform all CI/CD processes with

the managed package.

Migrate all classes, Visualforce, and components from the managed package to the

unlocked package. Install the new version of the managed package (objects/fields only)

and the unlocked package with the other components.

Salesforce must be informed at least 7 days before starting performance tests.

Salesforce will monitor test activity to ensure there are no issues with Salesforce

Services.

Performance tests must be run in a sandbox.

A business justification must be provided to Salesforce inorder to run performance

testing.

Performance tests may be run without advanced notice, but Salesforce will not store

performance logs.

Design theright sandbox strategy for the release.

Release sign-off is only required for Production.

Regression testing is mandatory for each release.

Maintain a pre/post deployment checklist for each release.

Publish a release calendar for each phase ofthe release.

Add the service centers to a hierarchical custom settings.

Add the service centers to a list custom settings.

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

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

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

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

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

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

Changes late in the process are expected and can be handled by integrating them into the requirements specs.

Complex processes that will need to be built are thoroughly understood and documentedbefore coding begins.

Milestones, timelines and estimates tend to be more accurate and predictable due to the upfront due diligence.

The costs of starting the project are low since much of the design work is pushed to later stages of the process.

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.

Provide the ability for distributed teams to work in isolation.

Provides automated code/configuration deployments.

Provides the ability to backup code/configuration changes.

Provides the ability to automatically identify issuesin code/configuration.

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

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

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

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

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

The team uses Scrum, Kanban, and Extreme Programming.

The team has biweekly sprints to ensure on-time delivery.

The team delivers new releases on dates defined in the beginning of the project, following a project plan

The team improves and evolves its processes and frequently delivers value to the endusers.