nerdexam
CompTIA

CAS-003 · Question #7

A security engineer has implemented an internal user access review tool so service teams can baseline user accounts and group memberships. The tool is functional and popular among its initial set of…

The correct answer is B. Latency C. Availability E. Recoverability. The three prioritized requirements map to latency (responsiveness for automated actions), availability (resilience to outages for SLA adherence), and recoverability (continuity of the lifecycle system-of-record during disruptions).

Enterprise Security Architecture

Question

A security engineer has implemented an internal user access review tool so service teams can baseline user accounts and group memberships. The tool is functional and popular among its initial set of onboarded teams. However, the tool has not been built to cater to a broader set of internal teams yet. The engineer has sought feedback from internal stakeholders, and a list of summarized requirements is as follows:

The tool needs to be responsive so service teams can query it, and then perform an automated response action. The tool needs to be resilient to outages so service teams can perform the user access review at any point in time and meet their own SLAs. The tool will become the system-of-record for approval, reapproval, and removal life cycles of group memberships and must allow for data retrieval after failure. Which of the following need specific attention to meet the requirements listed above? (Choose three.)

Options

  • AScalability
  • BLatency
  • CAvailability
  • DUsability
  • ERecoverability
  • FMaintainability

How the community answered

(22 responses)
  • A
    5% (1)
  • B
    68% (15)
  • D
    9% (2)
  • F
    18% (4)

Why each option

The three prioritized requirements map to latency (responsiveness for automated actions), availability (resilience to outages for SLA adherence), and recoverability (continuity of the lifecycle system-of-record during disruptions).

AScalability

Scalability relates to handling increased load, which is not explicitly called out as a stated requirement in the summarized list.

BLatencyCorrect

Latency addresses the requirement that the tool must be responsive so service teams can query it and trigger automated response actions quickly - high latency would break time-sensitive automation.

CAvailabilityCorrect

Availability directly addresses the requirement that the tool must be resilient to outages so teams can perform access reviews at any point in time and meet their own SLAs.

DUsability

Usability relates to user experience design, which is not among the three requirements described in the question.

ERecoverabilityCorrect

Recoverability addresses the system-of-record requirement - as the authoritative source for group membership lifecycle decisions, the tool must be able to recover its state and data integrity after any outage without data loss.

FMaintainability

Maintainability relates to ease of updating and managing the tool over time, which is not among the stated requirements.

Concept tested: Mapping system requirements to availability, latency, and recoverability properties

Source: https://learn.microsoft.com/en-us/azure/well-architected/reliability/principles

Topics

#availability#latency#recoverability#system resilience requirements

Community Discussion

No community discussion yet for this question.

Full CAS-003 Practice