Fligh School 2

Question 1

Differentiate between deployment and release

Answer 1

Deployment: the loading of code onto the servers where it will run
Release: the availability of code changes to users

Question 2

Describe a feature flag and its purpose and value

Answer 2

A feature flag is a software development technique used to enable or disable functionality remotely without changing code. It is a decision point in code with varying behavior based on external input.

Feature flags help separate deployment from release, which lets you manage the full lifecycle of a feature.

Wrapping code with feature flags gives you the safety to test new features and infrastructure in your production environment without impacting end users.

Question 3

Explain flag basics including categories, use cases, naming conventions, and the lifecycle of a flag

Answer 3

There are 4 main categories that best describe flags. Release, experimental, entitlements, and operational.

Flags can be either temporary or permanent.

Question 4

Define LaunchDarkly custom contexts, context kinds, multi-contexts, context instances, associated contexts, and context instance versions

Question 5

Explain context attributes, evaluation contexts, flag variations, and rule evaluation within the LaunchDarkly application

Question 6

Navigate the contexts lists

Question 7

Modify feature flags for a context instance

Question 8

Recognize the contexts list and flag dashboards and differences between each

Question 9

Flag Naming

Answer 9

Flags have two identifiers:

The flag name
The flag key

A good naming convention should convey:

The intended behavior and impact of the application when the flag serves a variation.
The scope and target of the behavior.
The purpose of a feature flag in both the flags list and source code.

Question 10

Release Flags

Answer 10

Release flags are temporary flags that control the progressive release of a new feature or behavior.

Question 11

Configuration Flags

Answer 11

Configuratoin flags are long loved operational flags that control the behavior of an application.

Question 12

Allow Flags

Answer 12

Allow flags are long-lived operational flags that control whether or not an action in allowed.

Question 13

Show Flags

Answer 13

Show flags are a long-lived operational flag that contol the visibility of a component

Question 14

Database Flags

Answer 14

Database flags are long-lived operational flags use to coordinate releases with schema migrations