WGU C706 Test Questions and Answers Latest Updated 2024/2025 (100% Solved)

WGU C706 Test Questions and Answers Latest Updated 2024/2025 (100% Solved) AGILE 1. Short releases 2. Delayed design 3. Involve users along the way 4. Minimal documentation 5. Informal/frequent documentation 6. Constant change Why AGILE? 1. shorten development cycles 2. adaptability 3. more efficient; less duplication AGILE Methodologies 1. Extreme Programming (XP) 2. Crystal 3. Unified Process 4. Scrum 5. Open Source Extreme Programming (XP) Core Values 1. Frequent communication between team and customer 2. Simplicity in design and code 3. Small iterations 4. Continuous unit testing 5. Courage Extreme Programming (XP) Key Pieces 1. Pair programmers 2. Coding standards WGU C706 Test Questions and Answers Latest Updated 2024/2025 100% Solved 3. Sustainable pace = 40hrs. / week 4. Collective ownership Extreme Programming (XP) Planning Business = Scope, priorities, release scope/date Techies = Estimates, consequences, process *Done with story cards Crystal Creator Alistair Cockburn XP Creator Kent Beck Crystal Project Basics 1. Project size = # of devs 2. Criticality = $ from malfunction 3. Priority = time pressure Crystal Methodologies 1. Crystal clear 2. Crystal orange 3. Crystal orange web Crystal Clear 1. Non-critical 2. Discretionary $ 3. 6-8 devs 4. Max 2 months Crystal Orange 1. Critical, but not life threatening 2. $$ 3. up to 40 devs 4. Up to 4 months Rational Unified Process Heavier of the Agile methodologies. More iterative requiring all requirements to be obtained in beginning. Scrum Creator Takeuchi and Nonaka (1986) Scrum Framework Must have: 1. Team roles 2. Events 3. Artifacts 4. Rules Scrum Methods Iterative using sprints (1 month or less dev effort) Scrum Roles 1. Product owner: voice of customer 2. Dev team: 3-10 devs 3. Scrum Master: dev coach keeps them on track Scrum Events 1. Sprint planning meeting: product owner and devs decide what is in sprint 2. Daily Scrum: short 15 min mtg. daily track 3. Sprint review: inspect products and backlog 4. Sprint retrospective: lessons learned on last day of sprint Scrum Aritfacts 1. Product backlog 2. Sprint backlog 3. Increment: the current project of all sprints 4. Burn down chart: log in current spring backlog SOAR State of the Art Report Assurance of security as a property in software. A snapshot of software security assurance discipline. CNSS - Software Assurance Level of confidence that software is free from vulnerabilities and functions in intended manner DoD - Software Assurance The level of confidence that software functions as intended and is free of vulnerabilities, either intentionally or unintentionally designed or inserted as part of the software NASA - Software Assurance The planned and systematic set of activities that ensure that software processes and products conform to requirements, standards, and procedures. MITRE's Plover Preliminary List of Vulnerabilities Examples for Researchers AVDL Application Vulnerability Description Language OVAL Works with CVE using XML and SQL. Language that tool can use to query CVE to look for vulnerabilities Threat Categories 1. Sabotage 2. Subversion 3. Interception 4. Disclosure Threat Tree Top Down model for identifying vulnerabilities. Top attacker goal at top of tree then work down to smaller goals to analyze attack structure. FMEA Failure Modes Effects Analysis is a bottom up approach for analyzing possible security failures