CompTIA Security+ SY0-701 Practice Test 36
Question 350
An online claims portal has a contractual requirement to be usable again within three hours of a major outage. The contract allows up to 20 minutes of recent transaction data loss, but the architect is asked specifically for the maximum service-restoration duration. Which objective captures that duration?
- A recovery point objective of three hours, because it measures service downtime
- Mean time between failures of three hours, because it measures allowable outage duration
- Mean time to repair from the last month, because an observed average is automatically a contractual target
- A recovery time objective (RTO) of three hours, distinct from the 20-minute recovery point objective
Explanation
Correct Answer
D:RTO is the target maximum elapsed time to restore a service after disruption. The portal must return to usable operation within three hours, so its RTO is three hours. The separate 20-minute allowance concerns RPO, the maximum acceptable age or amount of transaction data lost relative to the incident. Architecture should support both requirements through tested failover, application recovery, dependencies and appropriately frequent backups or replication. Meeting one objective does not ensure the other. The architect should also define when the outage clock begins and what 'usable' means under the contract so restoration tests evaluate the right outcome.
Incorrect Answers
A:RPO defines acceptable data loss measured in time, not how long the application may remain unavailable. Here the data-loss allowance is 20 minutes, while the service recovery deadline is three hours. Interchanging these targets could lead to a system that restarts quickly but loses too much data, or preserves data yet violates downtime commitments. The request asks for the restoration-duration metric.
B:MTBF is an observed or estimated reliability measure describing average time between failures for a repairable system. It is not a recovery deadline set by a business contract. A portal could have long intervals between failures yet recover too slowly during a rare outage. The three-hour requirement belongs to RTO, not to an equipment reliability statistic.
C:MTTR describes an observed or estimated average repair or recovery duration under a defined measurement approach. A mean from previous incidents can inform design but does not establish the contractual maximum acceptable downtime. If average repair takes three hours, some failures may take longer. The contract's required restoration target is an RTO and should be tested explicitly.
Question 351
A payment system takes a snapshot every fifteen minutes. After a storage failure, operators restore the latest good snapshot and discover that transactions from the preceding eleven minutes cannot be recovered. The business asks which type of recovery objective should be used to judge whether this data-loss interval is tolerable, independently of service-restoration time. What is the answer?
- Recovery time objective, because missing records indicate how quickly the application was restarted
- Mean time to repair, because the snapshot schedule sets the average repair time
- Recovery point objective, which addresses tolerable data loss measured as time before the incident
- Mean time between failures, because snapshots are taken on a repeating schedule
Explanation
Correct Answer
C:RPO concerns how far back recovery must go and how much recent data the organization can tolerate losing, often expressed in minutes or hours. The loss of eleven minutes of transactions illustrates the realized recovery point after the failure. A fifteen-minute snapshot interval may support an RPO near that interval under favorable assumptions, but success depends on snapshot consistency and availability. The actual RPO target must come from business requirements; the observed loss does not automatically establish that the target was met. RTO separately measures how long it takes to restore usable service, which the scenario does not provide.
Incorrect Answers
A:RTO is the amount of time permitted to return a service to operation, not the amount of transaction history missing. Eleven lost minutes of records could occur even if the service restarted immediately or after many hours. The stem does not state the restoration duration. It specifically asks about the interval of unrecoverable data, making RPO the relevant concept.
B:MTTR describes an average time spent repairing or restoring a system over observed events, depending on the organization's definition. The eleven minutes here represent data that was not recovered, not repair labor or downtime. A snapshot schedule alone cannot calculate average repair time. The organization needs event timing data for that reliability metric.
D:MTBF measures average operating time between failures in a repairable system. The frequency of snapshots does not indicate how often the payment service fails. Eleven minutes of transaction loss is unrelated to intervals between breakdowns. The appropriate recovery metric is concerned with the age of restored data, not hardware reliability.
Question 352
Over a quarter, a managed database cluster experienced four repairable outages lasting 20, 35, 25 and 40 minutes from failure detection to restoration. The reliability team wants the mean time to repair (MTTR) for those incidents using these durations. What should it report?
- 120 minutes, because MTTR is the sum of all outage durations
- 4 minutes, because there were four outages in the quarter
- 30 minutes, because the four repair durations total 120 and their arithmetic mean is 30
- 480 minutes, because total repair duration must be multiplied by the number of failures
Explanation
Correct Answer
C:Using the provided incident durations, mean time to repair equals total measured repair time divided by the number of repair events. The sum is 20 plus 35 plus 25 plus 40, which is 120 minutes; dividing by four outages gives 30 minutes. The measurement must use a consistent start and end definition across incidents and report outliers if they matter operationally. MTTR is an average observed performance metric, not a guarantee that the next outage will last exactly 30 minutes. It can inform staffing and recovery targets, but an RTO is a separately defined business requirement.
Incorrect Answers
A:The 120-minute total is useful when reporting cumulative downtime across this reporting quarter, but it is not a mean per incident. MTTR must divide that total by the four restoration events. Reporting only the sum would confuse aggregate outage exposure with typical per-incident repair duration. The question explicitly requests the arithmetic average of the supplied event lengths.
B:Four counts the separate incidents rather than the measured time taken to repair them. The units are failures, not minutes, so returning 'four minutes' is dimensionally incorrect. An average repair duration requires both the sum of durations and the number of outages. The quarterly observation window does not change that arithmetic.
D:Multiplying the total by incident count has no basis in the mean time to repair formula. It exaggerates the observed repair duration and would produce a number unrelated to the individual incident times. To obtain MTTR, add consistent repair intervals and divide by the count. The four durations give 30 minutes, not 480.
Question 353
A fleet of repairable factory controllers accumulates 18,000 operating hours over a reporting period and experiences six qualifying failures. Assuming the organization's MTBF definition uses operating time divided by failure count, what does the resulting metric mean?
- Every controller is guaranteed to run exactly 3,000 hours before its next failure
- The mean time to repair is 3,000 hours because the denominator counts breakdowns
- The controllers will never fail twice during a 3,000-hour interval
- The observed mean time between failures is 3,000 operating hours, not a guaranteed life for any individual unit
Explanation
Correct Answer
D:Under the defined fleet measurement, 18,000 total operating hours divided by six qualifying failures gives an MTBF of 3,000 operating hours. It summarizes average failure spacing for repairable equipment in the observed population and measurement conditions. Individual controllers can fail sooner or later, and a different workload or environment can change reliability. It is not the same as MTTR, which concerns time spent repairing faults, or an RTO set by business requirements. The reliability team should document which hours and failures were included, because comparison across fleets requires consistent definitions and exposure assumptions.
Incorrect Answers
A:MTBF is a statistical average rather than a warranty for each device. Some units may fail earlier, multiple times, or not at all during the observation period. Treating 3,000 hours as a guaranteed operating life would misrepresent uncertainty and risk, particularly for important factory control equipment. Maintenance planning should account for variability and criticality.
B:MTTR is calculated from repair or restoration durations, which the question does not provide. Operating hours between failures do not indicate how long technicians worked to restore a controller. A system can have a long MTBF but a lengthy MTTR, or fail frequently yet be repaired rapidly. The reported 3,000 hours is a failure-spacing measure.
C:An average of 3,000 hours does not exclude clustered or repeat failures. The metric cannot be used to promise zero failures in a particular interval. Reliability analysis should consider variance, failure modes and changing conditions, especially when safety or production continuity depends on these controllers. The question supplies enough data for a mean, not for such an absolute prediction.
Question 354
A risk register assigns moderate likelihood to credential compromise at a customer support portal. New threat intelligence reports active exploitation of a relevant identity weakness in comparable organizations, and access logs show increasing suspicious attempts. What should the risk manager do?
- Reevaluate likelihood and control effectiveness, update the risk entry and escalate treatment if thresholds are exceeded
- Freeze the existing score because risk registers should not change between annual audits
- Lower the risk automatically because more attacks have been detected rather than hidden
- Remove the suspicious login attempts from reporting so the historical baseline remains comparable
Explanation
Correct Answer
A:Risk assessment is iterative when threat conditions or exposure change. The reported campaigns and local login attempts may raise the assessed likelihood or reveal that existing prevention is inadequate. Validate the relevance of intelligence to the portal, review MFA, rate limiting, log evidence and account misuse indicators, then update the risk register with assumptions, owner and treatment needs. Escalate if the revised exposure crosses risk-appetite thresholds and monitor the selected controls. A changed score should not be driven blindly by headline volume alone, but neither should it ignore credible, applicable evidence. The goal is a current decision basis rather than a permanently frozen historical rating.
Incorrect Answers
B:An annual review can provide formal governance, but material new threat evidence may require reassessment immediately. Waiting would leave incident-prevention decisions based on outdated assumptions while attempts increase. The register should preserve previous scores and reasoning as history, then record a justified updated rating. Versioned changes improve traceability rather than undermine consistency.
C:More visible attempts do not necessarily mean that compromise likelihood has fallen. Improved detection may expose activity that previously went unnoticed, but it can also show increasing adversary pressure. The team needs to evaluate attack success, controls and applicability to decide. Automatically lowering risk because alerts exist would confuse telemetry with protection.
D:Suppressing attempts and related audit evidence from the risk report would hide relevant exposure and weaken executive oversight. Consistency can be maintained by documenting methodological changes and comparing like-for-like measures. Removing suspicious evidence cannot make the underlying credential threat disappear. Analysts should retain the data and incorporate it into an accountable reassessment.
Question 355
A university is selecting a payroll SaaS provider that will store staff bank details and allow vendor support personnel remote access. The contract will involve a foreign processing region. What should the procurement and security teams prioritize before signing?
- Accept the vendor's marketing assurance that encryption is always enabled without reviewing access rights
- Perform documented due diligence on security controls, privileged support access, data residency and incident obligations, with accountable risk approval
- Require only a discount clause because payroll information is processed outside the university
- Defer all privacy and supplier reviews until a real breach occurs
Explanation
Correct Answer
B:Due diligence should assess the provider's ability to protect sensitive staff bank records and meet applicable contractual and legal obligations before access is granted. Review evidence of encryption and key management, privileged support authentication, logging, breach notification, subprocessors, data location, deletion and business continuity. Identify whether cross-border processing needs additional safeguards and ensure accountable owners accept any residual gaps. The process should distinguish independently supported assurance from sales claims, and contractual terms must reflect actual data flows and support access. This addresses the specific financial-data and jurisdiction risks while enabling a reasoned procurement decision.
Incorrect Answers
A:Marketing statements are not detailed evidence of implementation, configuration or support access controls. A provider might advertise encryption while granting broad administrator access or using unapproved subprocessors. Procurement should verify relevant documentation and contractually require protections appropriate for staff bank information. Blind acceptance would leave material exposure unexamined before onboarding sensitive data.
C:Price is a commercial concern, but a discount does not resolve unauthorized access, cross-border transfer requirements or incident handling. The institution remains exposed to operational and privacy consequences if payroll records are mishandled. Security due diligence can influence price and contractual terms, but cannot be replaced by a discount clause. Financial data requires explicit protection and accountability.
D:Postbreach review is too late to prevent the first disclosure and may discover that essential safeguards were never negotiated. Supplier assessment, security obligations and data-flow validation belong before contract execution and migration. Ongoing monitoring should follow onboarding, but initial due diligence is necessary to make an informed decision about entrusting the vendor with bank details.
Question 356
A managed security provider offers a glossy self-assessment that claims its monitoring center is fully compliant with the customer's contractual controls. The customer requires evidence suitable for an independent assurance decision. What should the vendor risk assessor request?
- A second copy of the same marketing questionnaire signed by the sales team
- A statement that no customer has reported a breach in the past twelve months
- Relevant independent audit or assessment evidence showing scope, period, exceptions and remediation, plus targeted follow-up as needed
- A demo of the provider's analyst dashboard with no control documentation
Explanation
Correct Answer
C:Independent audit and assessment evidence gives the customer a stronger basis for assessing claimed controls than vendor assertions alone. The assessor should verify who performed the work, the period and systems covered, which control criteria were tested, any qualifications or exceptions, and corrective-action status. Confirm the report addresses the specific monitoring services used by the customer, not a different product or region. Supplement with targeted questions and contractual rights where gaps remain. Independent reports reduce assurance uncertainty but do not guarantee that every possible risk has been eliminated, so continued oversight and scope interpretation are still necessary.
Incorrect Answers
A:A sales-signed duplicate remains a self-attestation for this monitoring service and does not add independent testing. It may describe the provider's intended controls without evidence that they operated during the reporting period. Customer assurance requires validation of implementation and exceptions, particularly for a security operations service that itself protects sensitive incident data.
B:An absence of reported breaches is not evidence that preventive, detective and response controls meet specified requirements. Incidents may have occurred without discovery or disclosure, and a provider can be noncompliant without experiencing a known breach. This statement also omits audit scope and control effectiveness. Independent evidence is needed for the contractual assurance decision.
D:A dashboard demonstration can show user-interface features but cannot establish that monitoring coverage, access controls, incident procedures or evidence retention were tested independently. It is useful operational context, not an assurance report. The assessor should obtain control testing documentation with dates and exceptions rather than relying on what the vendor can show during a sales demonstration.
Question 357
A cloud supplier presents an internal security checklist and a separately issued independent assurance report covering a defined service and review period. The customer asks why the second document generally offers stronger third-party assurance. Which distinction is most accurate?
- Internal self-review automatically has the same external independence as a separately performed assessment
- Any report bearing a logo proves every supplier system is secure indefinitely
- An external attestation transfers all regulatory responsibility to the auditor
- An independent report provides separately performed testing or attestation against stated criteria, subject to its scope, period and exceptions
Explanation
Correct Answer
D:External assurance is stronger because a party independent of the supplier's day-to-day operation evaluates controls against defined criteria or attests to the evidence. Its usefulness depends on the exact service, systems, period, testing approach, findings and qualifications. An internal checklist can support management oversight but generally lacks the same independence. Customers must still assess whether the external report matches their service and review any exceptions, complementary customer responsibilities and periods not covered. Independent does not mean infallible or permanent. The distinction is an objective assurance basis with transparent limits, not a claim that responsibility or risk disappears.
Incorrect Answers
A:An internal checklist is prepared or controlled by the supplier's own personnel. It may contain valuable information but cannot automatically be considered an independent external evaluation. A third party's scope and methodology matter precisely because self-review can miss issues or have conflicts of interest. The two types of evidence are not interchangeable simply because both contain control questions.
B:A logo or audit brand does not prove security for every product and future date. Reports specify criteria, exclusions, dates and exceptions, and some may cover only one facility or service. The customer should check relevance to the purchased environment and understand its own configuration responsibilities. Overgeneralizing an assurance document can create false confidence.
C:An external auditor issues an opinion or attestation but does not assume all the customer's legal and operational obligations across jurisdictions. The supplier and customer remain responsible for their respective controls, contract requirements and data processing activities. Assurance evidence informs due diligence; it is not risk transfer or blanket regulatory immunity.
Question 358
A healthcare client suspects that a billing processor's subcontractor is storing patient records in an unapproved location. The provider refuses to supply detailed evidence voluntarily. The contract includes a negotiated right-to-audit provision with scope and notice rules. What should the client do?
- Treat the provider's refusal as final and close the compliance concern
- Invoke the right-to-audit clause through the approved contractual process, define the evidence scope and protect confidential materials
- Publicly demand unrestricted access to every subcontractor system without observing the contract's notice requirements
- Assume geographic compliance because the provider has a security certification
Explanation
Correct Answer
B:A right-to-audit clause gives the customer a contractual route to obtain agreed evidence or arrange an assessment when supplier claims are disputed. Use the contract's notice, scope, confidentiality and permitted auditor provisions; focus requests on data locations, subcontractor arrangements, access and transfer safeguards relevant to patient records. Coordinate with legal and privacy specialists and document any denied access or noncompliance for remediation or escalation. The provision is not unlimited access to every system, and it must be exercised professionally. This protects the client's legitimate assurance interests while respecting the negotiated boundaries of third-party oversight.
Incorrect Answers
A:A vendor refusal does not resolve the client's concern, especially when patient data may be processed outside approved arrangements. The contract provides a mechanism precisely for evidence disputes. Closing the concern would ignore potentially material privacy and contractual risk. The client should document the issue and invoke the agreed audit process before considering further contractual remedies.
C:Public demands for unrestricted access could breach confidentiality and exceed the carefully negotiated audit rights. Even serious concerns should be addressed under applicable notice, scope and legal procedures unless a lawful emergency exception applies. The customer needs relevant evidence, not uncontrolled access to unrelated systems or another party's sensitive information. Overreach can undermine the enforceability of a legitimate request.
D:A certification may provide general assurance about some controls, but it does not establish the actual geographic location of these specific patient records or every subcontractor's behavior. Certificates have scope and date limits. The suspected deviation calls for targeted evidence under the right-to-audit provision. General supplier assurance cannot replace investigation of a concrete contractual concern.
Question 359
A contracted penetration tester will assess a payment gateway that supports live transactions. The supplier's engineers intend to use scanning and limited exploit validation, but the customer cannot tolerate destructive tests or unannounced service disruption. What must be agreed before production testing?
- The tester's preferred tool list alone, without escalation contacts
- A requirement that all vulnerabilities be exploited fully regardless of production impact
- Permission to test any third-party system reachable from the gateway
- Written rules of engagement defining scope, authorized methods, windows, safety limits, contacts and stop conditions
Explanation
Correct Answer
D:Rules of engagement establish exactly what activities the tester is authorized to perform and how safety and communication will be managed. For a live payment gateway, they should identify target assets, excluded production components, allowed exploit depth, maintenance windows, rate limits, emergency contacts, incident escalation and criteria to halt testing. Include evidence-handling and reporting expectations so sensitive payment data is protected. Testers can then choose appropriate methods within the negotiated boundaries. This reduces the chance that a legitimate assessment causes a service outage or unauthorized third-party access. Written authorization is foundational; a technical scanning plan alone does not establish legal and operational permission.
Incorrect Answers
A:A tool list describes possible methods but does not authorize where, when or how aggressively they may be used. A safe command can still overload a fragile live service if scheduled incorrectly. The customer needs scope restrictions, safety parameters and stop conditions supported by accountable owners. Tool selection should follow agreed engagement rules, not replace them.
B:Full exploitation can produce service interruption, financial impact or access to sensitive customer data, particularly during peak traffic. Demonstrating vulnerability may require only limited non-destructive proof under an approved plan. The client explicitly disallows destructive behavior, so an unrestricted exploitation mandate contradicts operational and legal constraints. Test depth must be proportionate and authorized.
C:Reachability from a gateway does not imply authorization to test another organization's systems. Third-party providers may have separate permission and coordination requirements. Expanding scope without written consent can breach contracts or laws. A proper engagement identifies included assets and explicit exclusions, with a method to approve changes before testing them.
Question 360
A logistics firm outsources its parcel tracking platform. The supplier contract says 'reliable service' but contains no measurable uptime objective, support response target or remedy for repeated failure. Which contractual artifact should procurement add?
- A vendor support-staffing plan that commits to a named escalation contact but sets no uptime measurement or restoration target
- A disaster-recovery runbook shared by the provider but containing no customer-facing service availability commitments
- A monthly availability dashboard produced for marketing but not incorporated into contract measurement or remedies
- A service-level agreement defining uptime, measurement, support targets, escalation and remedies
Explanation
Correct Answer
D:An SLA establishes measurable service outcomes and how the parties will monitor and enforce them. For parcel tracking, define availability calculations, maintenance exclusions, response and resolution priorities, reporting cadence, escalation paths, service credits or remedies, and the relationship to disaster recovery obligations. Without these criteria, the supplier and customer may disagree about what 'reliable' means after an outage. Targets should reflect the business's critical shipping windows and be monitored with evidence accessible to both parties. An SLA does not replace security or privacy requirements, but it provides the measurable operational accountability missing from the current contract.
Incorrect Answers
A:Staffing and escalation contacts can help the buyer reach support during a platform outage, so this is relevant to supplier management. However, the missing contract terms include measurable availability, response targets and consequences when the vendor fails those commitments. A staffing appendix alone does not define what counts as downtime or give the buyer an enforceable service-level commitment. The broader SLA is required.
B:A provider recovery runbook may describe internal restoration steps and alternative systems, and it could support the vendor due-diligence process. However, it does not by itself establish a service-level objective, a measurement window, response targets or customer remedies. The logistics firm specifically lacks enforceable external performance expectations, which should be captured in an SLA rather than only in an internal operating procedure.
C:Historical dashboards may reveal whether the parcel-tracking application has performed reliably, but a marketing report alone is not a binding service commitment. It can also define uptime differently from the buyer’s critical service hours or omit support response times. Procurement needs an SLA specifying agreed measurement, escalation and remedies rather than relying on voluntary retrospective charts with no contractual effect.