SEC540 - SANS Cloud Security
Automation – DevSecOps UPDATED
Exam Questions and CORRECT Answers
Continuous Deployment - CORRECT ANSWER - Changes are deployed directly and
automatically to production using the CD pipeline (once all tests/checks pass)
Smoke Test - CORRECT ANSWER - Testing the environment so that no fires are
generated from the smoke
Blue/Green Deployment - CORRECT ANSWER - Deploy and switch between production
environments using load balancing
Self-service - CORRECT ANSWER - Changes are pushed to production by developers
Canaries - CORRECT ANSWER - Incremental deployment, stop and roll back if errors
ex. webfarm, update one node at a time. If any nodes experience failure, then you rollback.
"Fear of commitment rollout"
A/B testing - CORRECT ANSWER - Measuring effect/acceptance of a change or new
feature in production
Dark Launching - CORRECT ANSWER - Protect changes behind "feature switches"
Continuous Integration / Delivery Systems - CORRECT ANSWER - Version control push
events on the develop / main branches trigger workflow pipelines for building, testing, and
deploying the changes
ex.)
CodePipeline
, GitHub Actions
Jenkins
GitLab CI/CD
Azure DevOps
YAML - CORRECT ANSWER - **Learn this.** Update definition later
SARIF - CORRECT ANSWER - Static Analysis Results Interchange Format
Secrets - CORRECT ANSWER - Environment variables that are encrypted
Repository - CORRECT ANSWER - storage location for all of the pr oject's data - history,
files, versions, branches, configuration, data hooks, etc.
AKA the ".git" directory
Branch - CORRECT ANSWER - pointer to a snapshot of your changes
working tree - CORRECT ANSWER - the set of files (a branch at a specific version) ready
to be worked on - the checked-out files
staging area - CORRECT ANSWER - between the working tree and the repository, files
can be staged to mark them as prepared for commit
Git Clone - CORRECT ANSWER - make a local copy of a remote repository
download a project repository from a remote location; check out the most recent commit of the
default branch; track the remote location as the "origin" remote
Git Add - CORRECT ANSWER - snapshot of a changed file from the working tree
Automation – DevSecOps UPDATED
Exam Questions and CORRECT Answers
Continuous Deployment - CORRECT ANSWER - Changes are deployed directly and
automatically to production using the CD pipeline (once all tests/checks pass)
Smoke Test - CORRECT ANSWER - Testing the environment so that no fires are
generated from the smoke
Blue/Green Deployment - CORRECT ANSWER - Deploy and switch between production
environments using load balancing
Self-service - CORRECT ANSWER - Changes are pushed to production by developers
Canaries - CORRECT ANSWER - Incremental deployment, stop and roll back if errors
ex. webfarm, update one node at a time. If any nodes experience failure, then you rollback.
"Fear of commitment rollout"
A/B testing - CORRECT ANSWER - Measuring effect/acceptance of a change or new
feature in production
Dark Launching - CORRECT ANSWER - Protect changes behind "feature switches"
Continuous Integration / Delivery Systems - CORRECT ANSWER - Version control push
events on the develop / main branches trigger workflow pipelines for building, testing, and
deploying the changes
ex.)
CodePipeline
, GitHub Actions
Jenkins
GitLab CI/CD
Azure DevOps
YAML - CORRECT ANSWER - **Learn this.** Update definition later
SARIF - CORRECT ANSWER - Static Analysis Results Interchange Format
Secrets - CORRECT ANSWER - Environment variables that are encrypted
Repository - CORRECT ANSWER - storage location for all of the pr oject's data - history,
files, versions, branches, configuration, data hooks, etc.
AKA the ".git" directory
Branch - CORRECT ANSWER - pointer to a snapshot of your changes
working tree - CORRECT ANSWER - the set of files (a branch at a specific version) ready
to be worked on - the checked-out files
staging area - CORRECT ANSWER - between the working tree and the repository, files
can be staged to mark them as prepared for commit
Git Clone - CORRECT ANSWER - make a local copy of a remote repository
download a project repository from a remote location; check out the most recent commit of the
default branch; track the remote location as the "origin" remote
Git Add - CORRECT ANSWER - snapshot of a changed file from the working tree
