By to What three tools should an architect recommend to support application lifecycle methodology Choose 3 answers
Correct Answer: B,D,E
Explanation To support application lifecycle methodology, you need tools that can help you manage the source code, automate the deployment process, and track the issues and bugs. A version control repository is a tool that allows you to store, track, and collaborate on the source code of your application. A continuous integration tool is a tool that allows you to automate the deployment of your code to different environments, as well as run tests and validations. An issue tracking tool is a tool that allows you to record, monitor, and resolve the issues and bugs that arise during the development and testing phases. A database management system is a tool that allows you to store, manipulate, and query data, but it is not directly related to application lifecycle methodology. A middleware is a software layer that facilitates communication and data exchange between different applications, but it is not directly related to application lifecycle methodology either.
UniversalContainers (UC) is using custom metadata types to control the behavior of a few of the custom functionalities. UC wants to Deploy custom metadata types to production using Metadata API. Which two data types does UC need to include? Choose 2 answers
Correct Answer: B,D
Explanation To deploy custom metadata types to production using Metadata API, you need to include the CustomMetadata and CustomField data types. CustomMetadata represents the custom metadata type definition, and CustomField represents the custom metadata type fields. CustomMetadataType and CustomObject are not valid data types for custom metadata types
In architect is working on a project that relies on functionality that cannot be deployed via the Metadata API. What is the best practice for making sure these components are deployed successfully?
Correct Answer: D
Explanation This is the correct answer because some components, such as custom settings, user permissions, and email templates, cannot be deployed via the Metadata API. Therefore, these components should be documented and manually deployed or configured in the target environment.
Universal Container has multiple departments who use Salesforce and request changes: Sales, Service, Back Office, Marketing, etc. Each of these departments makes independent purchase decisions for AppExchange apps, field requests, and page layouts, resulting in low adoption and under -use of standard Salesforce capabilities. What mechanism should a Technical Architect recommend to increase use of standard Salesforce functionality?
Correct Answer: C
Explanation A Center of Excellence is a mechanism that can help to increase the use of standard Salesforce functionality, by defining and managing best practices, standards, and governance across the organization. A Center of Excellence can also facilitate cross-functional collaboration, knowledge sharing, and alignment of Salesforce initiatives with business goals. A Change Control Board is a group of stakeholders that reviews and approves changes to the system, but does not necessarily promote the use of standard Salesforce functionality. A Requirements Traceability Matrix is a document that links requirements to their sources and test cases, but does not necessarily increase the use of standard Salesforce functionality. A Project Management Office is a group that oversees the execution of projects, but does not necessarily increase the use of standard Salesforce functionality.
Universal Containers is a global organization that maintains regional production instances of Salesforce. One region has created a new custom object to track Shipping Containers. The CIO has requested that this new object be used globally by all Salesforce instances and further maintained and modified regionally by local administrators. Which two deployment tools will support this request? Choose 2 answers
Correct Answer: B,D
Explanation B and D are the correct answers, as Force.com IDE and Force.com Migration Tool are the deployment tools that will support the request of creating a new custom object to track Shipping Containers and making it available globally by all Salesforce instances and further maintained and modified regionally by local administrators. Force.com IDE and Force.com Migration Tool are both tools that use the Metadata API to retrieve and deploy metadata components, such as custom objects, from one org to another. They also allow for selective deployment, meaning that only the components that are needed can be deployed, without affecting the rest of the org. A is incorrect, as Tooling API is not a deployment tool, but an API that provides access to metadata and code, as well as customizing and automating the development process. C is incorrect, as Change sets are not a deployment tool that will support the request, as they are limited to deploying components between connected orgs, and do not allow for selective deployment or regional modifications. You can learn more about these tools in the Deploy Changes with the Force.com Migration Tool and Deploy Changes with the Force.com IDE units on Trailhead.