CompTIA Security+ SY0-701 Practice Test 58
Question 570
A firm models the billing portal and customer service portal as two independent, low-probability outage risks. During an architecture review, staff discover that both portals rely on the same regional identity cluster, and no alternate identity path has been tested. A failure of that cluster could stop both services simultaneously. How should enterprise risk analysis change?
- Add the two historical independent-outage probabilities without revisiting their shared infrastructure assumptions
- Remove one portal from the risk register because both applications share the same identity provider
- Model common-cause identity failure and correlated business impact instead of assuming independent portal outages
- Assume the identity supplier's cloud contract guarantees successful regional failover without testing it
Explanation
Correct Answer
C:A common identity-provider cluster creates a single failure mode capable of disabling both portals together. Revise likelihood assumptions, combined outage consequences, recovery dependencies and treatment choices around that shared component. Test alternate authentication paths or regional failover rather than relying on assumed redundancy. Maintain visibility of service-specific impacts while recording the common-cause scenario and its owner. This prevents portfolio reporting from understating simultaneous disruption merely because two applications were assessed by different teams. Quantification may still be uncertain, but the essential correction is recognizing correlated exposure and selecting controls that reduce the shared failure's blast radius.
Incorrect Answers
A:Adding probabilities derived under an independence assumption can substantially misstate combined exposure when both services depend on the same component. A shared outage scenario has different likelihood and impact characteristics from unrelated single-service failures. The dependency needs explicit modeling rather than blindly combining independent forecasts. A single federation outage can disable both portals at once, invalidating the independent-event assumption.
B:The portals still deliver different business functions, so removing one risk entry hides its distinct operational and customer impacts. The register can record both service consequences while also capturing the shared identity dependency or an aggregate scenario. Correlation changes the risk model; it does not make one application disappear. Both portals retain distinct customer impact even when they depend on the same authentication infrastructure.
D:Cloud or SaaS contracts can specify commitments, but they do not prove that this customer's exact integration has a working alternate identity route. Without end-to-end failover tests, configuration and dependency failures remain plausible. Supplier assurances can inform assessment but do not replace verifying the organization's own authentication continuity design. An untested secondary region may share precisely the same failing federation dependency.
Question 571
The board of an online retailer accepts moderate technology risk in order to enter new markets. Its operations committee separately approved a maximum customer-checkout interruption of thirty minutes per incident. A proposed cost-saving architecture has a known single failure that may leave payment processing unavailable for six hours. The sponsor says the board's growth-oriented risk appetite makes the design acceptable. Which response is correct?
- Treat the broad willingness to take strategic risk as automatic cancellation of every detailed service availability limit
- Interpret the thirty-minute tolerance as an annual average and therefore allow any individual six-hour outage
- Recognize that strategic risk appetite does not override the approved thirty-minute operational outage tolerance
- State that risk appetite and operational risk tolerance always use identical measurements and authorization processes
Explanation
Correct Answer
C:Risk appetite is a broad strategic expression of acceptable risk taking, while risk tolerance translates it into more specific operating limits such as thirty minutes of downtime for checkout. A design with plausible six-hour unavailability breaches that service threshold even if the company tolerates moderate strategic innovation risk. The team should add resilience, reduce dependency or escalate for an expressly authorized exception with business impact documented. Risk tolerance is not automatically immutable, but changing it requires the proper governance decision. This distinction ensures that general strategic language does not become permission to disregard specific operational commitments.
Incorrect Answers
A:A high-level appetite statement expresses the kinds and degree of risk leadership is willing to pursue. It does not by itself repeal separately approved constraints for a critical payment gateway. Specific limits guide concrete design and escalation. The proposed architecture should be evaluated against those limits, not justified by an unrelated general preference for growth.
B:The stated operational limit concerns an individual incident, not a cumulative annual average. Reinterpreting it without the approving body's authority would hide a clear breach of service tolerance. If a business case requires different availability, leaders must formally consider and revise the documented limit rather than silently changing the unit of measurement.
D:Appetite and tolerance are related but not identical. One may describe an enterprise-wide qualitative direction, while the other can set a measurable threshold for a service, loss or exposure. Equating them prevents meaningful escalation when a concrete technical proposal exceeds the authorized operational boundary. The board could tolerate strategic investment risk while rejecting even a brief customer checkout interruption.
Question 572
A business risk register identifies potential customer-order losses if the online store's edge firewall is bypassed. An infrastructure ticket assigns an engineer to fix one firewall rule, but the root risk also involves supplier availability and incident recovery planning. The register currently lists the ticket assignee as the person authorized to accept all remaining financial exposure. Who should actually own the risk?
- The firewall technician, solely because the person has a change ticket and can update a rule
- The analyst who triages edge firewall alerts, solely because the analyst observes related security events
- A business decision maker accountable for the store's exposure and authorized to decide treatment or acceptance
- The generic help-desk queue that records whether the firewall ticket is closed
Explanation
Correct Answer
C:Assign a named business risk owner with authority and accountability for the online store's potential loss. That owner considers likelihood, financial and customer effects, selects or approves treatment and accepts residual exposure within delegated limits. Security advisers assess the threat and engineers carry out specific remediation tasks, with progress linked to the risk register. The owner must revisit exposure when the patch closes or when supplier and recovery weaknesses persist. This separates management of a broad risk decision from accountability for one technical work item, avoiding the mistaken conclusion that ticket closure alone retires the business risk.
Incorrect Answers
A:A technical assignee is responsible for implementing a defined control change, not necessarily for deciding whether the business can tolerate all consequences of remaining exposure. The broader scenario spans revenue and recovery commitments beyond the one rule. A maintenance ticket should identify execution responsibility without replacing an accountable risk owner.
B:A monitoring analyst can supply evidence about attempted attacks and control performance, yet that role may not have authority over sales revenue, downtime or risk treatment budgets. Knowing when a firewall alert occurs is not the same as deciding whether residual enterprise exposure should be accepted. Monitoring and ownership should be linked but distinguished.
D:A service-desk queue can track deadlines, tickets and handoffs but lacks an identifiable person with decision rights over business losses. Assigning risk to a queue obscures accountability and usually produces a false sense of closure when one task is finished. The register requires an authorized owner and documented treatment decisions, not just a workflow inbox.
Question 573
A factory's risk team records three observations: an exposed VPN gateway is missing a security update, criminals are using a related exploit technique against peer manufacturers, and successful compromise could stop production for two days. One manager describes all three observations as 'the vulnerability.' How should the analyst distinguish the elements?
- The two-day production stoppage is the software weakness that an attacker can exploit
- The unpatched gateway is the vulnerability, criminal exploitation is the threat scenario, and downtime is the business impact
- The criminals' ongoing activity is an actual realized financial loss for this factory before any attack succeeds
- The VPN software version alone fully defines risk without considering exploitation or consequences
Explanation
Correct Answer
B:The missing VPN patch creates an exploitable weakness; the observed malicious activity demonstrates a plausible threat event or actor capability. Two days of lost production represents potential impact if that event succeeds against the company's exposure. Risk assessment combines these elements with likelihood, existing controls and uncertainty. Identifying them separately helps target remediation, detection and resilience measures appropriately. The criminals' activity at other companies does not automatically prove this factory has been breached, and the vulnerable firmware alone cannot specify the amount of resulting business harm. A well-formed risk scenario connects the weakness, threat path and relevant consequence.
Incorrect Answers
A:An outage is a potential consequence of exploitation, not a flaw in the VPN's software or configuration. Risk statements should link a specific weakness to an actor or event and the resulting business harm. Mislabeling impact as vulnerability obscures which technical issue should be fixed and how the business should prioritize it.
C:Threat activity against peer organizations is evidence that an exploit path is being used, not proof that this manufacturer already incurred an outage or monetary damage. The analyst may raise likelihood based on that intelligence but should not record hypothetical consequences as realized losses without incident evidence. Distinguishing observed threat from local impact prevents inaccurate reporting.
D:A firmware version can identify an affected asset or vulnerability candidate but cannot tell whether the gateway is reachable, what attackers might do or how much downtime would result. A useful enterprise risk description requires threat, exposure, control context and business consequences. Version information is one component of that analysis, not the entire scenario.
Question 574
A payments business defined a monthly key risk indicator threshold of ten verified privileged-access policy violations. This month the metric rises to thirty-four, across several service teams. A reporting analyst suggests suppressing excess records so executive dashboards remain green. What response follows the approved governance framework?
- Hide all violation records above ten so the reported value matches the tolerated threshold
- Treat the alert threshold only as a cosmetic reporting target and defer action until the next annual review
- Raise the permitted threshold retroactively to thirty-four without reviewing the underlying incidents
- Escalate the exceeded indicator to the accountable risk owner for analysis, treatment and documented decision
Explanation
Correct Answer
D:A key risk indicator provides an early signal that exposure may exceed accepted bounds. Verified violations above the approved threshold should trigger an escalation identifying affected privileges, repeat patterns, control failures and potential business consequences. The authorized risk owner decides whether to improve controls, initiate targeted investigations, accept a properly documented exception or seek a formally revised appetite limit. Record the decision, responsibility and follow-up metric so the dashboard continues to reflect reality. A threshold breach alone does not prove a breach of customer data, but it does require the defined governance response rather than suppression or silent reclassification.
Incorrect Answers
A:Suppressing data changes the report, not the underlying privileged-access behavior. It undermines trust in the key risk indicator and may conceal repeat violations that require investigation. Accurate counts and clear threshold breaches are essential for risk owners to decide whether current controls and behavior remain within approved limits. Suppressing observations corrupts the indicator and hides the very breaches that require management attention.
B:An established monthly trigger is intended to prompt timely attention. Waiting for an annual review while the indicator materially exceeds tolerance defeats the monitoring purpose and may permit continuing misuse. The organization should analyze and escalate now, with proportionate urgent controls where necessary, not treat a verified threshold breach as ordinary historical reporting.
C:A risk threshold can be revised through formal governance when conditions or strategy genuinely change, but retroactive adjustment solely to make the latest score look compliant is not a risk treatment. Investigate whether behavior, controls or detection coverage changed first. The exception and approval trail should remain visible rather than rewriting the benchmark after a bad month.
Question 575
A nonprofit already uses a documented five-level qualitative likelihood-and-impact matrix for cybersecurity risks. Two scenarios receive the same High category: ransomware affecting donor services has several relevant near misses, while an outsourced payment interruption has little direct incident history but could jeopardize payroll timing. The board needs a defensible funding order without pretending it knows exact annual dollar losses. What should the risk team do next?
- Assign an invented annual dollar loss to each High rating and present the larger fabricated figure as a statistically measured priority
- Document evidence confidence and assumptions, compare mission consequences and existing safeguards under the calibrated matrix, and test whether reasonable rating changes alter the ranking
- Treat every risk with the same matrix color as identical priority, without considering uncertainty or different business dependencies
- Wait for several years of precisely measured loss events before giving the board any comparative funding advice
Explanation
Correct Answer
B:Calibrated qualitative ratings make different business scenarios comparable, but identical category labels do not erase differences in evidence quality, business timing or control strength. The team should state why each scenario received its category, disclose the poorer evidence supporting the supplier estimate, and examine mission-critical impacts and current mitigating controls. It can use defined tie-breaking criteria and sensitivity checks to see whether reasonable alternative judgments change the funding order. This makes a provisional recommendation without claiming unsupported actuarial precision and gives the board explicit review triggers as evidence improves. Unlike simply identifying a qualitative matrix, the question tests how to adjudicate tied ordinal risks.
Incorrect Answers
A:The purpose of the qualitative matrix is disciplined prioritization when exact probabilistic loss information is unavailable. Assigning precise dollars by arbitrarily multiplying ordinal labels does not create measured loss frequency or severity. The exercise also has differing confidence: ransomware near misses provide more direct evidence than the sparse supplier history. Any numerical scenarios must identify assumptions and uncertainty rather than being presented as observed annual losses.
C:A color or rating groups threats into broad risk categories, not a fixed priority order for every case within that category. The donor service and payroll dependency have different mission consequences, control coverage and levels of evidence. Treating them as interchangeable would hide those distinctions and could misallocate limited mitigation funds. The organization should document a defensible tie-breaking process and uncertainty, not pretend the heat-map cell makes every relevant decision.
D:Waiting for exact historical data would leave material exposures untreated and can be unrealistic for low-frequency, high-impact supplier failures. The nonprofit already has a consistent qualitative framework and can refine its assumptions, consult responsible service owners and make transparent interim tradeoffs. Sensitivity analysis and explicit uncertainty provide a more accountable decision than indefinitely postponing funding while awaiting statistically conclusive loss histories.
Question 576
An enterprise introduced conditional MFA for privileged cloud operations. A governance reviewer has the written policy and screenshots showing that the access rule exists, but the team needs evidence that approved sign-ins succeed and prohibited sign-ins actually fail. Which activity measures control effectiveness rather than identifying a threat or checking paperwork?
- List new attacker techniques targeting privileged accounts and enter them into the risk register
- Read the published MFA requirement and assume it operates correctly because its approval date is recent
- Inspect the current policy configuration without performing an access attempt under representative conditions
- Test legitimate and prohibited privileged sign-ins and record whether the enforcement matches the specified rule
Explanation
Correct Answer
D:Control effectiveness concerns whether the configured safeguard produces the intended security outcome in operation. Use authorized test accounts and representative contexts to attempt permitted and forbidden privileged sign-ins, verifying MFA challenge behavior, denials and associated logs. Test exemptions and failure conditions so the review does not rely on a single happy path. Record setup, observed results and discrepancies, then remediate and retest failed cases. This distinguishes assurance of functioning enforcement from risk identification or policy existence. Production tests must be coordinated to avoid disrupting privileged operations or triggering unnecessary containment, but they provide stronger evidence than screenshots alone.
Incorrect Answers
A:Threat discovery and risk identification are valuable upstream activities but do not demonstrate that the deployed MFA rule blocks or permits any real sign-in. They describe what might happen, not whether this control performs as intended. Effectiveness assessment needs observed results from representative use or attack paths. Threat intelligence is useful context, but it does not demonstrate whether the deployed MFA rule blocks disallowed logins.
B:An approved policy provides governance direction, not evidence that the technology is correctly configured, deployed or integrated with all target applications. An unnoticed exception or legacy authentication path could permit a prohibited login. Date of publication adds no proof of actual enforcement and should not replace controlled testing. The team should verify actual allow and deny behavior using scoped test accounts and preserved outcomes.
C:Configuration inspection can detect obvious errors, but it may miss bypasses caused by application integrations, trusted locations or conditional access evaluation. A displayed rule does not prove that a specified user, device and operation encounter it as expected. Representative end-to-end tests can reveal such implementation gaps while retaining the configuration evidence as context.
Question 577
A conglomerate asks two divisions to rate the likelihood of a significant service outage. Both use the words 'High' and 'Low,' but one division calls an event expected once in ten years High, whereas the other reserves High for several events in a single year. Their ratings are being combined into one board-level risk portfolio. What must the risk team do first?
- Convert High to three and Low to one and average the divisions without specifying what those numbers mean
- Declare the division assigning Low incorrect merely because its counterpart used the word High
- Translate both verbal ratings directly into precise annual financial losses using the labels alone
- Standardize likelihood definitions, time horizons and scoring criteria before comparing or aggregating the assessments
Explanation
Correct Answer
D:Risk scales must define what each likelihood category means, over which time period and with what evidence threshold. Agree on common terms for exposure, controls and confidence before requesting ratings from the divisions again. Only then aggregate comparable scenarios and disclose remaining judgment uncertainty. The board can still see legitimate business differences, but those differences should arise from facts rather than incompatible meanings of High and Low. Standardization makes cross-division prioritization more defensible without pretending qualitative ratings are actuarially precise measurements. Record how each department applies the revised criteria to a sample scenario and resolve material discrepancies before aggregation.
Incorrect Answers
A:Assigning numeric codes to undefined categories does not make the underlying judgments comparable. The same label describes materially different time frequencies in the two divisions. Averaging ordinal codes could produce a mathematically neat but meaningless enterprise score, hiding inconsistent assumptions. One department may call an event likely within a month while another uses a five-year horizon.
B:Disagreement is not necessarily an error until both teams use the same definition and evidence basis. One may be considering different exposure or a different period. The risk team should clarify scope and shared criteria, then re-rate where needed rather than forcing consensus based solely on which label sounds more conservative.
C:Qualitative terms alone cannot establish financial consequences or an exact annual probability. A precise loss estimate requires impact data, likelihood assumptions, control effects and exposure characteristics. Converting undefined labels straight into currency would compound the original inconsistency with unwarranted numeric certainty. Neither division supplied a calibrated loss distribution, so the resulting annual totals would be invented.
Question 578
An employer has already identified the three subcontractors supporting its proposed payroll SaaS service and mapped their processing regions. However the prime vendor offers a generic confidentiality promise; the overseas support processor has no evidenced privileged-access controls, documented breach-notification flow-down or assurance coverage, and the customer has not authorized its handling of salary records. What must be demonstrated before approving this downstream processing?
- Accept the existing subprocessor inventory alone because naming every subcontractor proves that their operational safeguards are effective
- Treat the prime vendor’s internal checklist as automatically extending its independent audit opinion to all untested subcontractors
- Verify enforceable flow-down obligations, restricted processor access, applicable transfer safeguards and scoped assurance for the named downstream parties, resolving gaps before approval
- Rely on the payroll service’s contractual uptime objective to prove that subcontractor confidentiality and incident-response requirements are satisfied
Explanation
Correct Answer
C:Subprocessor due diligence continues after identifying names and jurisdictions. The customer needs evidence that the prime vendor imposes enforceable confidentiality, access, incident-notification, deletion and audit obligations on the actual downstream support organization, with appropriate transfer safeguards where applicable. Review processor permissions, scoped assessments and exception remediation before approving sensitive payroll handling; where direct evidence cannot be shared, arrange a contractually suitable independent examination. This decision tests whether the identified chain is verifiably governed, rather than merely mapping which fourth parties exist. Document accountable approval and mechanisms for notice of material subprocessor changes.
Incorrect Answers
A:Knowing which subcontractors participate is a necessary first step, but their names and processing locations do not prove that privileged support access is restricted, activity is logged or incidents will be reported. Here inventory work has already been performed. The customer still needs evidence that security and privacy obligations actually bind and govern each downstream handler of employee salary records.
B:An internal vendor checklist and a report covering only the prime service cannot establish independent assurance for an excluded offshore support team. Reports are bounded by named systems, tested controls and review periods. The supplier must show contractual flow-down and relevant evidence for the actual parties receiving payroll data. An unexamined subcontractor does not inherit positive audit conclusions simply because it serves the same customer.
D:An uptime objective describes service availability, which is important for payroll deadlines but not proof of confidentiality or governance of offshore support access. A provider may meet every availability target while a subcontractor improperly views salary statements or delays a required incident report. The identified assurance gap concerns processor authority, downstream security controls and legally required data handling, not the number of minutes the software stays online.
Question 579
A hospital network negotiates with an outsourced payroll processor. The service fee is modest, but the proposed contract caps the supplier's liability for security incidents at one month's payment. The network estimates that a serious employee-data exposure could create much larger forensics, notification and remediation costs. Which vendor-risk action addresses the contractual gap?
- Assume outsourcing transfers all consequences of a data breach to the payroll supplier regardless of contractual language
- Review liability caps, indemnification, cyber insurance and the customer's retained loss exposure in proportion to the processing risk
- Evaluate only the supplier's uptime performance because availability is the main service metric
- Delete incident notification contacts from the agreement to avoid triggering unnecessary response costs
Explanation
Correct Answer
B:A liability cap equal to one month's fees may bear little relationship to losses caused by a payroll data breach. Assess plausible forensics, notification, litigation, recovery and business-interruption costs, then negotiate appropriate caps, indemnities, required insurance and incident cooperation duties. Confirm what exclusions and sublimits apply, and document whatever residual exposure the customer retains. The service fee alone should not determine acceptance of a high-impact supplier risk. Contract terms are only part of treatment: the vendor's actual security controls, financial capacity and response readiness also matter. The goal is proportionate, explicit risk allocation rather than an unsupported belief that a low price justifies a nearly complete limitation of accountability.
Incorrect Answers
A:Outsourcing processing does not automatically transfer every legal, financial or reputational obligation. The customer may remain responsible for employee notification, regulatory compliance or continuity of payroll, regardless of vendor fault. Liability allocation is governed by contractual terms and applicable law, so implicit assumptions are dangerous. The customer may retain notification, regulatory and reputational exposure even if the vendor caused the breach.
C:Uptime is important to payroll continuity but says little about financial responsibility for confidential employee data disclosure. A vendor can meet availability targets yet suffer an information breach with large notification costs. Review must cover confidentiality and incident response obligations as well as service reliability, with residual exposure documented for decision makers.
D:Removing notification procedures would make coordination harder and could cause the hospital to miss required legal deadlines. Well-defined incident contacts, reporting timeframes, evidence preservation and cooperation terms are essential controls. The contract should clarify obligations and loss allocation rather than concealing potential incidents to reduce apparent administrative cost. Delayed coordination would also worsen investigation costs, evidence preservation and statutory notification risk.
Question 580
A company is about to purchase an outsourced payroll module. The provider supplies an unqualified assurance report for its general HR portal, but the report's system description expressly excludes the payroll module and its batch-processing subcontractor. Sales says both services share a logo and infrastructure, so the same report must count. What should third-party risk reviewers conclude?
- Accept the report as payroll evidence because both products carry the same vendor brand
- Infer that an untested payroll component passed merely because the tested HR portal had no findings
- Rely only on the provider's verbal similarity claim without obtaining relevant scoped assurance
- Treat the excluded payroll module as outside the report's assurance scope and obtain appropriate evidence before relying on it
Explanation
Correct Answer
D:Assurance reports define which services, controls and periods were examined. If the intended payroll module and its subprocessor are carved out, the report does not substantiate security claims about those components. Obtain specifically scoped assurance, targeted testing, architectural evidence or contractual safeguards with residual risk documented, depending on the transaction's sensitivity. The existing HR portal report may still inform background diligence, but it cannot be presented as direct evidence that the untested module passed. Explicitly reading boundaries and carve-outs prevents a misleading approval that ignores the exact product handling confidential salary and banking records.
Incorrect Answers
A:A corporate brand does not expand the testing boundaries of an assurance engagement. Different modules may have separate data stores, administrators, subcontractors and deployment controls. The report can be useful context about the vendor but cannot establish the security condition of explicitly excluded payroll operations. Payroll data processing introduces separate sensitive fields and privileged functions that need specifically scoped evidence.
B:No findings for one system do not establish effective controls in a second system the auditor did not test. Its design, operating evidence and risks may differ. Assessments are only evidence for defined time periods, criteria and system boundaries; extrapolating beyond those limits creates an unsupported assurance claim. An absence of findings is meaningful only for controls the auditors actually examined.
C:Management assertions can guide follow-up questions but cannot replace evidence covering the purchased service's actual processing environment and obligations. An excluded module may have distinct sensitive-data flows and external operators. Request control mappings, relevant audits or independent testing rather than treating verbal similarity as tested operational effectiveness. The buyer needs records of the batch subprocessors and the payroll module’s own access controls.