CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Scaled Agile
  5. SAFe-DevOps

Free SAFe-DevOps Exam Braindumps (page: 4)

Page 3 of 25
PDF with 98 Questions

Which technical practice incorporates build-time identification of security vulnerabilities in the code?

  1. Dynamic code analysis
  2. Penetration testing
  3. Application security
  4. Threat modeling

Answer(s): A

Explanation:

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, dynamic code analysis is a technical practice that incorporates build-time identification of security vulnerabilities in the code. This means that the code is scanned for potential security risks during the compilation or execution phase, rather than during the testing phase. The handbook states that "Dynamic code analysis is a technique that identifies security vulnerabilities in the code during compilation or execution."1 Therefore, dynamic code analysis helps teams detect and fix security issues early in the development process.



What is one aspect of the Continuous Delivery Pipeline?

  1. Continuous Security
  2. Continuous Integration
  3. Continuous Experimentation
  4. Continuous Delivery

Answer(s): B

Explanation:

One aspect of the Continuous Delivery Pipeline is Continuous Integration. Continuous Integration (CI) is the practice of merging all development versions of a code base several times a day and verifying them with automated tests. CI helps to improve the quality and consistency of the code, and to accelerate the delivery and deployment of new functionality. CI is the second aspect in the four-part Continuous Delivery Pipeline of Continuous Exploration (CE), Continuous Integration (CI),

Continuous Deployment (CD), and Release on Demand. CI consists of four activities: develop, build, test end-to-end, and stage12



What is one reason for test data management?

  1. To automate provisioning data to an application in order to set it to a known state before testing begins
  2. To track the results of automated test cases for use by corporate audit
  3. To provide a viable option for disaster-recovery management
  4. To truncate data from the database to enable fast-forward recovery

Answer(s): A

Explanation:

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, test data management is one reason for test data management. This means that test data management helps teams ensure that the application under test has a consistent and reliable state, by automating the provisioning of data from various sources and formats. The handbook states that "Test data management is the process of automating provisioning of data to an application in order to set it to a known state before testing begins."1 Therefore, test data management enables teams to perform end-to-end testing with confidence and accuracy.



Where do features go after Continuous Exploration?

  1. Into Continuous Integration, where they are deployed with feature toggles
  2. Into Continuous Development, where they are implemented in small batches
  3. Into the Portfolio Backlog, where they are then prioritized
  4. Into Continuous Integration, where they are then split into Stories

Answer(s): D

Explanation:

In the Scaled Agile Framework (SAFe), after features are defined and designed during Continuous

Exploration, they move into Continuous Integration. Here, they are further broken down into smaller, implementable parts known as user stories. These stories are then developed, tested, and integrated into the existing codebase. This process ensures that new features are developed in a systematic and efficient manner, with regular integration and testing to maintain quality and readiness for release.






Post your Comments and Discuss Scaled Agile SAFe-DevOps exam with other Community members:

SAFe-DevOps Discussions & Posts