Free DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT Exam Braindumps (page: 7)

Page 6 of 57

Universal Containers (UC) has integrated with their on-premise billing system using Salesforce Connect. The data is configured using an External Object in sandbox. UC wants to deploy the external object to production using the Metadata API and would like to know what Metadata types to choose for deployments to production.
Which two options are valid metadata types related to deployment of external objects? Choose 2 answers.

  1. In change sets, external objects are included in the custom object component.
  2. In the Metadata API, the External Object metadata type represents external objects.
  3. In change sets, external objects are included in the External Object component.
  4. In the Metadata API, the Custom Object metadata type represents external objects.

Answer(s): A,D



Universal Containers (UC) has a huge volume of metadata that cannot be deployed at once.
What is the recommended strategy for UC to be successful with the deployment?

  1. Identify metadata dependencies, create logical groupings, and deploy in the right order.
  2. Use a continuous integration tool such as Jenkins to deploy in the right order.
  3. Sort and group the metadata alphabetically and deploy them in the same order.
  4. Use a combination of the Ant migration tool and change sets for deployment.

Answer(s): A



Universal Containers wants to implement a release strategy with major releases every four weeks and minor releases every week. Major releases follow Development, System Testing (SIT), User Acceptance Testing (UAT) and Training Minor releases follow Development and User Acceptance Testing (UAT) stages.
What represents a valid environment strategy consideration for UAT?

  1. Minor releases use Partial copy and Major releases use Full copy
  2. Minor and Major releases use separate Developer pro
  3. Minor releases use Developer and Major releases Full copy
  4. Minor and Major releases use same Full copy.

Answer(s): A



Which are two key benefits of fully integrating an agile issue tracker with software testing and continuous integration tools? Choose 2 answers?

  1. Developers can see automated test statuses post code commit on a specific user story.
  2. Developers can collaborate and communicate effectively on specific user stories.
  3. Developers can observe their team velocity on the burn chart report in the agile tool.
  4. Developers can use the committed code's build status directly on the user story record.

Answer(s): A,D






Post your Comments and Discuss Salesforce DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT exam with other Community members:

DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT Discussions & Posts