Fundamentals 1 Definition as question Flashcards

(89 cards)

1
Q

A text file that tells Git about the files and folders that should be ignored from the repository.

A

.gitignore

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

Agile is a collaborative approach to software development based on incremental and iterative developments.

A

Agile

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

Agile is a collaborative approach to software development based on incremental and iterative developments.

A

Agile

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

An API key is a unique code passed into an API to identify the application or user requesting the API.

A

API Key

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

An API key is a unique code passed into an API to identify the application or user requesting the API.

A

API Key

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

An application is a program designed to create value for a group of customers.

A

Application

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

An application is a program designed to create value for a group of customers.

A

Application

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

Automation is a set of automatic tasks, tests, or flows that will run as part of a continuous delivery process to ensure quality during deployment. With automations, you can automate the parts of software development related to building, testing, and deploying, increasing predictability and efficiency and minimizing human manual intervention and costs.

A

Automation

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

Automation is a set of automatic tasks, tests, or flows that will run as part of a continuous delivery process to ensure quality during deployment. With automations, you can automate the parts of software development related to building, testing, and deploying, increasing predictability and efficiency and minimizing human manual intervention and costs.

A

Automation

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

A reusable template that contains a set of steps that can be executed in the future.

A

Automation Template

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

A reusable template that contains a set of steps that can be executed in the future.

A

Automation Template

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

A back promotion is a process that allows you to promote user stories from higher environments to lower environments.

A

Back Promotion

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

A back promotion is a process that allows you to promote user stories from higher environments to lower environments.

A

Back Promotion

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

A burndown chart is a graphical view that compares the current progress of the items in a sprint with the planned progress.

A

Burndown Chart

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

A burndown chart is a graphical view that compares the current progress of the items in a sprint with the planned progress.

A

Burndown Chart

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

A testing metric that helps you determine the quality of the code that you want to test.

A

Code Coverage

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

A testing metric that helps you determine the quality of the code that you want to test.

A

Code Coverage

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

A compliance rule contains the criteria relevant to an organization that Copado’s scanner uses to query and analyze your org’s metadata and match when a metadata item is out of compliance.

A

Compliance Rule

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

A compliance rule contains the criteria relevant to an organization that Copado’s scanner uses to query and analyze your org’s metadata and match when a metadata item is out of compliance.

A

Compliance Rule

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

Compilation of compliance rules that can be assigned to an environment.

A

Compliance Rule Group

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

Compilation of compliance rules that can be assigned to an environment.

A

Compliance Rule Group

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

Copado Compliance Hub’s analysis is performed to monitor metadata changes in your environments or Git branches.

A

Compliance Scan

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

Copado Compliance Hub’s analysis is performed to monitor metadata changes in your environments or Git branches.

A

Compliance Scan

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

A template used to define the promotion, back-promotion behaviors, automation, and quality gates that are applied throughout your DevOps process.

A

Connection Behavior

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
A template used to define the promotion, back-promotion behaviors, automation, and quality gates that are applied throughout your DevOps process.
Connection Behavior
26
A feature-based license that enables a connection between two orgs in a pipeline for Copado to create feature branches and execute Git-based promotions between the orgs.
Copado Branch Management
27
A feature-based license that enables a connection between two orgs in a pipeline for Copado to create feature branches and execute Git-based promotions between the orgs.
Copado Branch Management
28
A user-based license that allows you to monitor and enforce compliance rules on your business for all metadata changes made within your environments.
Copado Compliance Hub
29
A user-based license that allows you to monitor and enforce compliance rules on your business for all metadata changes made within your environments.
Copado Compliance Hub
30
A user-based license that allows you to configure a data set deployment by using point-and-click data templates.
Copado Data Deploy
31
A user-based license that allows you to configure a data set deployment by using point-and-click data templates.
Copado Data Deploy
32
The Copado Permissioner is an application that allows you to have better control of permission set assignments to users.
Copado Permissioner
33
The Copado Permissioner is an application that allows you to have better control of permission set assignments to users.
Copado Permissioner
34
A license that gives you access to manage planning records such as user stories, sprints, epics, etc., and functionality such as Kanban Boards, Sprint Wall, and Work Manager.
Copado Plan
35
A license that gives you access to manage planning records such as user stories, sprints, epics, etc., and functionality such as Kanban Boards, Sprint Wall, and Work Manager.
Copado Plan
36
A user-based license designed to help you better manage the release management process of requirements from one or multiple sandboxes to production.
Copado User
37
A user-based license designed to help you better manage the release management process of requirements from one or multiple sandboxes to production.
Copado User
38
A credential is a connection between a user and an environment.
Credential
39
Data commits allow you to keep a version history of the changes to be committed in a data set via CSV files and easily move them to upper environments (or lower, in case of back-promotions) within your pipeline.
Data Commit
40
A data set is a container that stores, in CSV files, a snapshot of the data included in a particular environment for use in the future.
Data Set
41
A data template is a configuration file that defines a data structure you want to migrate between Salesforce orgs.
Data Template
42
Deployment is a process of moving one or multiple changes from one environment to another.
Deployment
43
A deployment step is an action that is performed during a deployment.
Deployment Step
44
A destination branch is a copy of the content included in the destination environment.
Destination Branch
45
Set of predefined variables that can be used in a Salesforce Flow deployment step.
Dynamic Variables
46
An environment in Copado is a representation of a Salesforce organization or instance of an application in other clouds such as Heroku or MuleSoft.
Environment
47
Environment Variables is a feature that allows you to make commits, deployments, branch validation environment agnostic.
Environment Variables
48
An epic is a large user story that needs to be split up into smaller user stories prior to its implementation.
Epic
49
A feature is an Agile and scrum element that can be described as a large piece of work that delivers some type of business value.
Feature
50
A feature branch is an auxiliary branch that Copado creates when you commit changes to a user story.
Feature Branch
51
A function is a script that contains a series of commands and can be executed from Copado.
Function
52
A Git repository is a storage location where the versions of your files are stored. This may be a hosted location or your own Git server.
Git Repository
53
A Git snapshot in Copado is a connection between a Salesforce org and a Git repository branch.
Git Snapshot
54
A job execution is a representation of a job template execution at a given point in time.
Job Execution
55
A job step is a task that is performed as a result of a job template execution.
Job Step
56
A job template is a reusable template with a list of steps that can be executed as part of different processes such as a commit, a promotion or a deployment.
Job Template
57
Kanban is an Agile framework based on a JIT (Just-In-Time) approach and incremental improvements, where all the work is organized on a Kanban board.
Kanban
58
A Kanban board is a tool that helps you visualize Salesforce records distributed among different columns as well as filter them to fit your needs.
Kanban Board
59
Elements of the metadata grid in the Salesforce Metadata Pipelines User Story Commit page (in the Copado DevOps Platform User Story Commit page, the metadata components are called files).
Metadata Component
60
A metadata group is a collection of metadata items to which you can apply different automation or quality gates.
Metadata Group
61
A metadata item is a representation of a Salesforce metadata type.
Metadata Item
62
An org difference is a comparison between two Salesforce orgs.
Org Difference
63
A persona represents a group of users clustered based on shared behavior, motivations, goals, pain points, or other characteristics.
Persona
64
A unidirectional flow that defines the order in which changes will be migrated, starting with the development orgs and finishing in the production org.
Pipeline
65
A proposed or planned undertaking of changes that are going to be made in Salesforce.
Project
66
A container used to deploy one or multiple user stories from one environment to another following a designated pipeline.
Promotion
67
A promotion branch is a branch created by Copado’s backend that combines the content in the feature branch with the content in the destination environment.
Promotion Branch
68
A single input or instruction given to an AI system to generate a response.
Prompt
69
A mechanism that allows you to let your team know about the changes you have pushed to a branch in a repository so that you all can discuss them.
Pull Request
70
A release is a feature that allows you to group user stories to promote them together as well as to keep track of the version of changes that your application experiences after every deployment.
Release
71
A field on the Environment Variable record that specifies where a particular variable will be applied.
Scope
72
Scrum is an Agile methodology used in software development that helps teams work together using iterations called sprints.
Scrum
73
A snapshot difference compares two Salesforce orgs, two Git commits, or a Salesforce org and a Git commit.
Snapshot Difference
74
A Salesforce org that carries all your changes to be promoted to the next environment (or to a previous one, in case of back-promotions). For example, if you want to promote your changes from Dev1 to UAT, Dev1 will be your source environment.
Source Environment
75
A sprint (or iteration) is a time-boxed period during which a team needs to complete a certain amount of work. The duration of the sprint is set in advance and usually ranges from one week to a month, a two-week period being the most common.
Sprint
76
A sprint wall is a view that shows the sprint's status and a whole picture of its content.
Sprint Wall
77
An action that is provided by Copado out-of-the-box, e.g., commit. System Property A system property is a value that is stored in Copado and can be referenced in a function.
Standard Action
78
A team is a group of people who work together on the same project.
Team
79
A test script is a list of predefined steps you need to follow to test the specifications of a system.
Test Script
80
A theme is a group of user stories contributing to a common goal. It is the highest level in the user story hierarchy.
Theme
81
A user story is the smallest unit of work in an Agile framework. It’s an informal, general explanation of a software feature written from the perspective of the end-user or customer. Hence, a user story can be called an end goal, not a feature. In Copado, a User Story is also used as a container object to develop, commit, promote, and deploy development work (Metadata, Apex code, etc.). It also helps to link and track additional functionalities like Use Cases, Test Runs, and Quality Gates.
User Story
82
A user story can be broken into multiple tasks, which are used to enable the development team to better understand what needs to be done and chalk out the roadmap to the completion of the user story. Tasks are usually defined by the people doing the work (Developers, QA, etc.). They contain a detailed explanation of the job to be completed.
User Story Task
83
A data-oriented language that is used to create a configuration and provide a human-readable file format.
YAML
84
It records a change or a contribution.
Git Commit
85
It represents an independent line of work. Branches can be created out of other branches and fed with contributions from other branches via a merge.
Git Branch
86
It is the way to move a change (commit) from one branch to another. You can use merges during the release process to move your modifications from the branch you are working on up into production.
Git Merge
87
The place where file versions, branches, and commits are stored.
Git Repository
88
What is is a set of tools and features provided by Salesforce to improve the development experience on their platform. It allows developers to create short-term Salesforce environments called Scratch Orgs, which can be quickly set up and configured with specific metadata. This enables developers to work on specific features or projects in isolation, making the development and testing process more efficient.
SFDX: Salesforce DX (SFDX)
89
Acronym for Lightning Experience, which is the modern and user-friendly interface provided by Salesforce. It is a complete redesign of the classic Salesforce interface (known as Salesforce Classic) and offers a more intuitive and visually appealing user experience.
LEX