โ† All CAS Flashcard Decks

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
  1. In a CAS deployment project, which document defines the agreed-upon performance, availability, and support expectations between the application team and stakeholders?

    Answer: Service Level Agreement (SLA)

    An SLA formally documents the measurable targets for uptime, response time, and support response that both parties commit to.

  2. Which deployment strategy minimizes downtime risk by running the old and new application versions simultaneously and shifting traffic gradually?

    Answer: Canary deployment

    Canary deployment routes a small percentage of traffic to the new version first, allowing teams to validate stability before shifting all users over.

  3. What is the primary purpose of a rollback plan in a CAS application deployment?

    Answer: To define steps to revert to the previous stable version if the new deployment fails

    A rollback plan provides a tested, documented procedure to restore the last known-good version quickly when a deployment causes critical issues.

  4. In CAS project management, what does a RACI matrix define?

    Answer: Roles and responsibilities for each task: Responsible, Accountable, Consulted, Informed

    A RACI matrix clarifies who is Responsible for doing work, Accountable for outcomes, Consulted for input, and Informed of results for each task.

  5. Which agile ceremony is specifically designed to identify process improvements at the end of a sprint in a CAS project?

    Answer: Sprint retrospective

    The sprint retrospective focuses the team on reviewing what went well, what didn't, and what process changes to adopt in the next sprint.

  6. What is the key difference between a bug and a feature request in CAS project issue tracking?

    Answer: A bug describes unintended behavior deviating from requirements; a feature request is new desired functionality

    A bug is a defect where the system behaves contrary to its documented requirements, while a feature request asks for new capabilities not previously specified.