Author: Anonymous

Vantage Grid’s team has identified that a cyberattack could disrupt real-time monitoring of a substation. Before writing the actual resilience requirement, they need to define specific limits: how much monitoring degradation is tolerable, how long a total loss of monitoring can last, and how quickly the system must detect and recover from the disruption. Given that Vantage Grid, like most organizations, doesn’t have unlimited engineering resources, what should immediately follow once those limits are defined?

Vantage Grid writes this requirement for a new substation: “The control system shall never allow line voltage to exceed 105% of nominal, regardless of grid conditions, by physically limiting transformer output.” An engineer says this one doesn’t fit the detect-react-recover pattern most of Vantage Grid’s other requirements follow. Which of the four function categories does it actually belong to, and why doesn’t it need detection or reaction first?

Vantage Grid’s engineering team gets excited about a newly published resilience technique and adds it to every substation without checking how it interacts with the substation’s existing failover logic. Weeks later, one substation experiences a longer outage than before the new technique was added, because the new technique and the existing failover logic occasionally worked against each other. What does the source material say this outcome illustrates about resilience techniques?

Examples of how community nutritionists engage in entrepreneurial activities include all of the following EXCEPT:

Vantage Grid classifies a checksum used to verify that sensor data hasn’t been corrupted in transit as one kind of resilience technique, and a dedicated fire-detection-and-suppression system installed in an equipment room as another kind, along the same classification axis. What is that axis, and which category does each technique belong to?

Larkspur Health collects patient email addresses for exactly one stated reason: sending appointment-confirmation messages. Six months later, the marketing team starts sending the same list a promotional newsletter about new clinic services, without asking patients again or offering a way to decline just the newsletter. A manager defends this by pointing out no *new* data was collected — it’s the same email address on file. Which principle does this practice violate, and why doesn’t the manager’s defense hold up?

Larkspur Health’s privacy officer reviews a new feature: patients are never told the portal shares appointment-scheduling data with a third-party reminder service, and there’s no way to opt out of that sharing once an account is created. Which of the following framework principles for fair information practice does this feature violate? (Select all that apply.)

Vantage Grid’s leadership asks its engineers to justify why the company tracks eight named subordinate quality attributes separately, rather than lumping every threat under one generic “resilience” umbrella. For each of the following, does the paired benefit actually match how that attribute helps Vantage Grid handle its own adversities? (Select all that correctly pair the attribute with its actual benefit.)

Vantage Grid runs software that watches a regional power distribution network and keeps electricity flowing to hospitals and homes even when equipment fails or storms knock out lines. A new engineer describes the system as resilient simply because “it keeps the lights on most of the time.” A senior architect says that description captures only the surface of what resilience actually means for this system. True or False: the new engineer’s description captures only the basic-level definition of resilience, leaving out the deeper standard.

Vantage Grid drafts this requirement for a new substation: “While in mode M, the substation-control system shall continue to provide monitoring capability C with an availability of A during the duration of adverse conditions with a probability of at least P.” A reviewer says the requirement is well-formed but, on its own, tells the team nothing about how a disruption would actually be caught or fixed. Which template category does this requirement belong to, and what’s actually missing?