VCAP Storage Conceptual Model

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/72

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 10:59 PM on 10/19/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

73 Terms

1
New cards

What are Business Requirements?

The core goals, outcomes, and business drivers requested by stakeholders that the solution must support.

2
New cards

Why are Business Requirements important?

They define why the project exists and provide the basis for technical design decisions.

3
New cards

Give examples of Business Requirements.

Reduce deployment time, support multi-region availability, improve scalability, meet compliance requirements, or reduce operational costs.

4
New cards

What stakeholder concern is addressed by Business Requirements?

Desired business outcomes and organizational objectives.

5
New cards

What should every design decision map back to?

A documented business requirement.

6
New cards

What does RCAR stand for?

Requirements, Constraints, Assumptions, and Risks.

7
New cards

Why is the RCAR framework important?

It documents key design considerations and helps justify architecture decisions.

8
New cards

What is a Requirement in RCAR?

A statement describing what the solution must achieve.

9
New cards

What are functional requirements?

Requirements describing specific capabilities or services the solution must provide.

10
New cards

What are non-functional requirements?

Requirements defining quality attributes such as performance, availability, security, or scalability.

11
New cards

Give an example of a functional requirement.

The solution must support 5,000 virtual machines.

12
New cards

Give an example of a non-functional requirement.

The solution must maintain 99.99% uptime.

13
New cards

What is a Constraint in RCAR?

A fixed limitation or restriction that cannot be changed by the design team.

14
New cards

Why are constraints important?

They define the boundaries within which the solution must be designed.

15
New cards

Give examples of constraints.

Fixed budget, existing hardware requirements, compliance regulations, licensing restrictions, or datacenter space limitations.

16
New cards

Can architects change constraints?

No. Constraints must be accommodated within the design.

17
New cards

What is an Assumption in RCAR?

A condition accepted as true without complete verification during the design phase.

18
New cards

Why are assumptions documented?

To identify dependencies that may require later validation.

19
New cards

Give an example of an infrastructure assumption.

The network team will provide 10GbE connectivity before deployment.

20
New cards

What risk is associated with assumptions?

If an assumption is incorrect, the design may require changes or remediation.

21
New cards

What is a Risk in RCAR?

A potential event that may negatively affect project success.

22
New cards

Why identify risks early?

To allow mitigation planning before issues occur.

23
New cards

Give an example of a project risk.

A storage vendor may not deliver hardware before the deployment deadline.

24
New cards

What should accompany every identified risk?

A mitigation strategy or contingency plan.

25
New cards

Which RCAR component describes what the solution must achieve?

Requirements.

26
New cards

Which RCAR component describes fixed limitations?

Constraints.

27
New cards

Which RCAR component describes expected conditions not yet verified?

Assumptions.

28
New cards

Which RCAR component describes potential future problems?

Risks.

29
New cards

What does AMPRS stand for?

Availability, Manageability, Performance, Recoverability, and Security.

30
New cards

What is the purpose of AMPRS?

To evaluate and document key design quality attributes.

31
New cards

What is Availability in AMPRS?

The ability of a system to remain operational and accessible.

32
New cards

How is availability commonly measured?

Uptime percentage or service-level agreements (SLAs).

33
New cards

What design features improve availability?

Redundancy, clustering, load balancing, and fault tolerance.

34
New cards

Give an example of an availability requirement.

The solution must provide 99.99% uptime.

35
New cards

What is Manageability in AMPRS?

The ease of operating, monitoring, maintaining, and supporting the environment.

36
New cards

Why is manageability important?

It reduces administrative effort and operational complexity.

37
New cards

What design characteristics improve manageability?

Automation, centralized management, monitoring, and standardization.

38
New cards

Give an example of a manageability requirement.

Administrators must manage all clusters from a single interface.

39
New cards

What is Performance in AMPRS?

The ability of the solution to meet latency, throughput, and responsiveness requirements.

40
New cards

How is storage performance commonly measured?

IOPS, throughput, and latency.

41
New cards

How is compute performance commonly measured?

CPU utilization, response time, and workload capacity.

42
New cards

Give an example of a performance requirement.

Database storage latency must remain below 5 ms.

43
New cards

What is Recoverability in AMPRS?

The ability to restore services and data after a failure.

44
New cards

Which metrics are commonly associated with recoverability?

RPO and RTO.

45
New cards

What does RPO stand for?

Recovery Point Objective.

46
New cards

What does RPO measure?

The maximum acceptable amount of data loss.

47
New cards

What does RTO stand for?

Recovery Time Objective.

48
New cards

What does RTO measure?

The maximum acceptable service restoration time.

49
New cards

Which technologies support recoverability?

Backups, replication, snapshots, and disaster recovery solutions.

50
New cards

Give an example of a recoverability requirement.

The environment must achieve a 15-minute RPO and 1-hour RTO.

51
New cards

What is Security in AMPRS?

The protection of systems, applications, and data from unauthorized access or threats.

52
New cards

Which design areas are included in security?

Authentication, authorization, encryption, auditing, and compliance.

53
New cards

Why should security be considered early in design?

Security requirements often affect architecture, operations, and compliance decisions.

54
New cards

Give an example of a security requirement.

All sensitive data must be encrypted at rest and in transit.

55
New cards

Which AMPRS category relates to uptime?

Availability.

56
New cards

Which AMPRS category focuses on operational simplicity?

Manageability.

57
New cards

Which AMPRS category focuses on latency and throughput?

Performance.

58
New cards

Which AMPRS category focuses on backups and disaster recovery?

Recoverability.

59
New cards

Which AMPRS category focuses on protecting data and systems?

Security.

60
New cards

What is the relationship between RCAR and AMPRS?

RCAR identifies design inputs and constraints, while AMPRS evaluates the quality of the resulting solution.

61
New cards

Which framework helps identify stakeholder requirements and project assumptions?

RCAR.

62
New cards

Which framework is used to validate architecture quality attributes?

AMPRS.

63
New cards

When documenting a design, what should requirements map to?

Business requirements and stakeholder objectives.

64
New cards

Which is more difficult to change: a requirement or a constraint?

A constraint because it represents a fixed limitation.

65
New cards

True or False: Assumptions should be validated during the project lifecycle.

True.

66
New cards

True or False: Every risk should have a mitigation strategy.

True.

67
New cards

True or False: Availability and Recoverability are the same thing.

False. Availability focuses on keeping services running, while Recoverability focuses on restoring services after failure.

68
New cards

What is a tradeoff between Availability and Cost?

Higher availability typically requires additional hardware, redundancy, and operational expense.

69
New cards

What is a tradeoff between Performance and Cost?

Higher performance generally requires more powerful hardware and increased investment.

70
New cards

What is a tradeoff between Security and Manageability?

Additional security controls may increase administrative complexity.

71
New cards

What is a tradeoff between Availability and Manageability?

Highly available solutions may be more complex to manage.

72
New cards

What should drive all infrastructure design decisions?

Documented business requirements.

73
New cards

What is the first step of good architecture design?

Understand the business requirements and stakeholder objectives.