Development Lifecycle 13% Flashcards

1
Q

What is the Force.com migration tool?

A

A Java/ANT-based command line utility for moving metadata between a local directory and a SFDC organization.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

True/False: The following scenario can be done using the Force.com migration tool?
You want to change the contents of a file between organisations - I.E. retrieve a file from Org. A, make a change, and then deploy to Org B.

A

True.

Note, not possible with the Force.com IDE, as you would need to save the change to Org A, before deploying to Org. B.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

True/False: The Force.com migration tool is not useful for development projects where you need to populate a test environment with lots of data,

A

False.

Note, making changes with an automated script is far faster than entering them by hand.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

True/False: The Force.com migration tool can be utilized in Multi-stage release processes? - I.E. iterative building, testing, staging, deployment.

A

True.

Note, Scripted retrieval and deployment of components can make the process much more efficient.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

True/False: The Force.com migration tool can be used with advantage in the following scenarios:

  1. Populating a test environment with data
  2. Change contents of files between organisations
  3. Multi-stage release processes
  4. Repetitive deployments using the same parameters
  5. Migrating from staging to production
A

True.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the Bulk API?

A

A RESTful API that is optimal for loading or deleting large sets of data.
Note, used to query, insert, update, upsert, or delete a large number of records asynchronously by submitting batches that Salesforce processes in the background.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the Metadata API

A

The Metadata API is used to retrieve, deploy, create, update or delete customization information, such as custom object definitions and page layouts.
Note, this API is intended for managing customizations and for building tools that can manage the metadata model, not the data itself.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

True/False: To create, retrieve, update or delete records, such as accounts or leads, use the Metadata API.

A

False.

Note, to change data use data SOAP, REST or BULK API.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Order the following to get a typical development lifecycle:

  1. Develop
  2. Create testing environments (incl. UAT & Integration)
  3. Create development environments
  4. Test
  5. Schedule release
  6. Migrate changes from UAT environment to staging
  7. Perform UAT
  8. Migrate changes from integration environment to UAT
  9. Migrate changes from development environment to integration
  10. Replicate production changes
A
  1. Create development environments
  2. Develop
  3. Create testing environments (incl. UAT & Integration)
  4. Migrate changes from development environment to integration
  5. Test
  6. Migrate changes from integration environment to UAT
  7. Perform UAT
  8. Migrate changes from UAT environment to staging
  9. Replicate production changes
  10. Schedule release
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

List the three types of Sandboxes and the difference between them.

A
  1. Partial Copy Sandbox - Metadata
  2. Developer Sandbox - Metadata and a subset of Data
  3. Full Sandbox - Metadata and Data
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Describe unmanaged packages.

A

Unmanaged packages are typically used to distribute open-source projects or application templates to provide developers with the basic building blocks for an application.
Once the components are installed from an unmanaged package, the components can be edited in the organization they are installed in.
Note, unmanaged packages should not be used to migrate components from a sandbox to production organization.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Describe managed packages.

A

Managed packages are typically used by Salesforce partners to distribute and sell applications to customers. Note, these packages must be created from a Developer Edition organization. - Managed packages are also fully upgradeable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Order the following to get the general procedure when using the Force.com migration tool to copy metadata from one SFDC Org. to another.

  1. Construct a project manifest in package.xml
  2. Enter credentials and connection information for the Source Org in build.properties
  3. Run the tool to deploy metadata files or deletions to SFDC
  4. Create retrieve targets in build.xml
  5. Enter credentials and connection information for the Destination Org in build.properties
  6. Run the tool to retrieve metadata files
A
  1. Enter credentials and connection information for the Source Org in build.properties
  2. Create retrieve targets in build.xml
  3. Construct a project manifest in package.xml
  4. Run the tool to retrieve metadata files
  5. Enter credentials and connection information for the Destination Org in build.properties
  6. Run the tool to deploy metadata files or deletions to SFDC
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

True/False: Unmanaged packages can be useful for distributing initial components to multiple organisations

A

True.

Note, You cannot make further changes to those files using the same method.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Common Metadata Issues: What is the issue around retrieving custom fields on standard objects?

A

When we use the wildcard symbol in package.xml, to retrieve all objects, we don’t retrieve custom fields on standard objects.
Note, this can instead be set up in the project manifest.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Common Metadata Issues: What is the issue around profiles and field level security?

A

The contents of a retrieved profile depend on the other contents of the retrieve request.
I.E. a profile will only include field-level security for fields included in custom objects returned at the same time as the profile.

17
Q

Common Metadata Issues: What is the issue around retrieving or deploying components that depend on an object definition?

A

The following metadata components are dependent on a particular object: Custom field, Picklist, RecordType, Weblink, Validation rule. This means you must dot.qualify the component name with the object name in package.xml and may not use the wildcard symbol.
Note, this can instead be set up in the project manifest.

18
Q

Common Metadata Issues: What is the issue around personal folders?

A

Users personal folders, for both reports and documents, are not exposed in the metadata API. To migrate reports and documents they must be in the public folder.