CAS Project Management and Deployment Flashcards
6 cards from real CAS practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 CAS Project Management and Deployment flashcards as text
In a CAS continuous integration pipeline, what is the main purpose of automated regression testing after each code commit?
Answer: To detect newly introduced defects that break previously working functionality
Regression tests verify that code changes have not broken existing functionality, catching defects at the earliest possible point in the pipeline.
Which project management technique helps CAS teams identify which tasks must be completed before others can begin?
Answer: Critical path method (CPM)
The critical path method maps task dependencies to find the longest sequence of dependent tasks, identifying which must finish on time to avoid delaying the project.
What is infrastructure as code (IaC) and why is it valued in CAS application deployments?
Answer: Defining and provisioning infrastructure through version-controlled configuration files for repeatability
IaC treats infrastructure definitions as versioned code, enabling consistent, repeatable environment provisioning and eliminating configuration drift.
In CAS project risk management, what is the difference between risk mitigation and risk acceptance?
Answer: Mitigation takes action to reduce likelihood or impact; acceptance acknowledges the risk and prepares a contingency if it occurs
Mitigation proactively reduces a risk's probability or impact through planned actions, while acceptance acknowledges the risk and plans a response only if it materializes.
Which deployment metric measures the average time from a code commit to a successful production deployment in a CAS project?
Answer: Lead time for changes
Lead time for changes tracks the elapsed time from when code is committed to when it runs in production, measuring the speed and efficiency of the delivery pipeline.
What is the purpose of a post-mortem (incident retrospective) following a production outage in a CAS application project?
Answer: To conduct a blameless analysis of root causes and define preventive actions to avoid recurrence
A blameless post-mortem focuses on systemic root causes and actionable improvements rather than individual fault, building a learning culture that prevents repeat incidents.