CompTIA SY0-701 Bundle

Network discovery and inventory reconciliation can reveal devices that were deployed without registration or have unknown network addresses. It helps find shadow hardware and services, but the cloud buckets are already known: the missing information is which accountable team owns remediation. Another discovery scan cannot assign responsibility for fixing public access.

Recording sensitivity labels and data-handling rules is important for deciding how customer records or regulated files should be protected. The scenario does not say the buckets' sensitivity is unknown; security cannot identify who must act on an unsafe public access setting. Classification alone does not establish an accountable owner to accept and close a remediation ticket.

A SaaS service inventory tracks subscriptions and user accounts so offboarding teams can revoke access to unapproved external applications. These known cloud object-storage buckets instead lack assigned internal owner teams. Cataloguing SaaS accounts would not identify who is responsible for bucket access-policy configuration and the public exposure remediation.

Classifying the sensitivity of printer spool data helps establish appropriate encryption, retention, and handling rules. That matters after the organization knows which printers exist and their workloads. The immediate issue is devices appearing on network discovery but not in inventory, so data classification alone would leave those unknown assets unregistered and unmanaged.

Named ownership makes someone accountable for a known device's patching, configuration, and retirement. However, these printers are missing from the official inventory entirely, so the organization must first identify and reconcile the observed devices before assignments can be reliably managed. Ownership is an important next step after establishing inventory completeness, not the direct detection control.

Device assignment and custody linkage help determine which person received a tablet or laptop, improving loss investigation and returns. It does not resolve printers observed on a network but absent from the central inventory. For shared office printers, reconciling asset discovery and identifying their operational service owners is more useful than assigning handheld-device custody.

Chain-of-custody records and destruction certificates demonstrate control over physical media handed to another party for disposal. The NAS is entering service rather than leaving the organization; no disposal vendor or missing drive is described. Destruction documentation cannot tell administrators how to protect the sensitive customer records that will be stored on it.

An accountable owner is useful for approving access policy and responding to issues with the NAS. Yet even a correctly assigned owner could follow the wrong protection baseline if the onboarding record omits the sensitivity of the customer information. The immediate deficiency is missing data classification and handling requirements, not merely the absence of an asset owner.

Retention and sanitization are important at the end of a storage device's life. They prevent deleting records that must be kept and then enable safe reuse or disposal of media. This NAS is newly provisioned and will soon contain sensitive customer data; the first lifecycle decision is documenting information classification and required protections, not end-of-life erasure.

Assigning an accountable business owner ensures that someone approves risk decisions and coordinates remediation. The edge appliance already has such an owner, but its vendor provides no security fixes, so an assigned name does not reduce its continuing exploitability. The question requires a treatment decision for unsupported technology rather than another inventory attribution step.

Requiring patch commitments and secure configuration evidence during procurement helps prevent future devices entering service without support. It is a good control when selecting a replacement. However, the appliance has already reached a state in which vendor updates are unavailable, so revised acquisition documents alone do not handle its current exposure.

Software inventory and license reconciliation identify unauthorized installations, unsupported packages, or license shortfalls. They can document the appliance's installed components but do not manufacture vendor patches for an unsupported platform. The security team must decide whether the device can be isolated with compensating controls or needs urgent replacement rather than merely counting installations.

A legal hold preserves information relevant to litigation or investigation before equipment is retired. If there is such a hold, media must not be destroyed until retention obligations are satisfied. Here the drives are already scheduled for authorized third-party destruction; the auditors' stated concern is tracing each drive across custody transfers and proving completion, not discovering a new legal hold.

Physical destruction can render sensitive information unrecoverable when suitable techniques and verification are used. It is necessary for some unusable high-sensitivity media, but the act of shredding alone does not establish which serial-numbered drives were received, transported, or processed by the contractor. The auditors need traceable evidence as well as sanitization effectiveness.

Retaining required records and sanitizing media afterward is a sound lifecycle sequence when storage can be reused. It addresses legal retention and end-of-life confidentiality. It does not by itself document whether every individual drive shipped to a third-party destruction provider arrived intact and received the agreed service. The specific question is the custody-audit trail.

Custody documentation and destruction certificates record where media went and what a service provider reports completing. Such evidence is useful after selecting an effective sanitization method, but paperwork itself does not render data on a failed disk unrecoverable. The question asks which control directly handles media that cannot be reliably erased, so actual approved destruction takes priority.

Software inventory and license reconciliation help detect unauthorized software, missing entitlements, and systems that require lifecycle attention. The subject here is a physically failed removable drive containing high-sensitivity records, not an installed program or license issue. Inventory alone does not sanitize the device or prevent a person from recovering its client data.

Legal holds and evidence-preservation procedures protect records that must not be deleted during an investigation or retention period. The scenario gives no such outstanding hold; it asks how to treat a failed, sensitive disk that cannot be erased. Preservation would delay destruction if legally required, but absent that condition it does not satisfy secure final disposition.

Replacement or network isolation may be warranted for an unsupported edge appliance that cannot receive security patches. Here the audit found unlicensed installations across engineering workstations rather than hardware whose vendor support has ended. Replacing the computers would be disproportionate and may leave the unauthorized software inventory problem unresolved on new machines.

A SaaS inventory maps subscriptions and user accounts so a departed employee's access can be revoked. That is essential for external services but does not directly identify unlicensed locally installed engineering applications. The case describes software already deployed on managed machines, so endpoint software discovery and license reconciliation are the more precise controls.

Network discovery reconciled with a hardware inventory finds unmanaged printers, servers, and other devices attached to corporate networks. It does not necessarily enumerate installed software or compare licenses to software entitlement. All the engineering machines may already be registered, yet still host unauthorized applications. Use software asset management to resolve this distinct lifecycle issue.

A legal hold prevents deletion of records relevant to litigation or investigation. The scenario does not mention a case requiring preserved evidence; it highlights a departing employee who retains access to a paid external service. Retention controls are important in a dispute but do not inventory shadow SaaS subscriptions or immediately remove live authentication sessions.

Software asset inventory and license reconciliation compare installed packages with approved licenses on company endpoints. A personally provisioned paid cloud service may not appear as locally installed software at all. Even a complete desktop package inventory would not prove whether the departing employee can still sign in to that external SaaS tenant.

Assigning asset ownership improves accountability for systems and helps ensure someone approves access and remediation work. However, naming a person in an inventory does not revoke the departing employee's still-active account in an unrecorded SaaS service. The immediate action requires discovering the subscription and removing credentials or access through the service's administration controls.

A certificate of destruction is documentary evidence that a specified destruction service took place; it is not a substitute for carrying out an approved sanitization method. This leased drive remains physically intact and must be reused, so issuing a certificate without erasing the key would misrepresent the security outcome and leave company data potentially recoverable.

Physical destruction of the drive can be appropriate when media is irreparably failed, very sensitive, or cannot be reliably sanitized. In this scenario, however, the lessor explicitly requires functioning storage to be returned intact for reuse. Shredding would defeat that business requirement and may breach the lease. A verified cryptographic erase is the more appropriate option when the device and key architecture support it.

Deleting the user profile or quick-formatting a filesystem changes directory structures and account access but does not necessarily render underlying encrypted sectors unrecoverable. If the original media key remains accessible through device or recovery infrastructure, residual ciphertext may still be decryptable. The requirement is validated elimination of the decryption capability, not just removal of visible files or user accounts before returning leased hardware.

Replacing or isolating an unsupported controller may be necessary when a device in operation has reached end of vendor support. Here operations is only ordering new controllers and has not obtained evidence of secure defaults or update commitments. The preventive opportunity is at procurement, so an end-of-life replacement decision comes too late to avoid purchasing another unsupported design.

Asset assignment and inventory linkage provide a record of the individual custodian and deployed device, useful after hardware is issued and during loss response. They do not guarantee that a manufacturer will provide security updates or ship secure defaults. The deficient step occurs before controllers are purchased, so vendor security obligations must be checked in procurement and acceptance.

Recording data sensitivity helps determine encryption and handling requirements for customer records or storage platforms. Industrial controllers may also process sensitive operations data, but classification does not establish whether their firmware can be updated securely. The question identifies missing vendor patch and secure-default evidence, requiring purchase specifications and supplier verification rather than data labels.

Naming an accountable service owner makes a business group responsible for an asset's security configuration and lifecycle decisions. A missing tablet, however, also requires knowing which individual held it and what management profile was installed. A generic owner entry could still leave incident responders unable to identify the last custodian or assess the exposed data.

Security requirements in acquisition can specify encryption, management enrollment, support, and warranty controls for tablets. Those safeguards are useful before purchase, but the reported failure is an inventory that cannot connect one missing device to its assigned holder and installed profile. Procurement standards alone do not reconstruct its custody or current management state.

Network discovery can find a tablet while it is attached to an observed subnet and reveal an otherwise unregistered endpoint. Once the tablet is missing, it may be offline or outside the organization entirely. Discovery also does not reliably establish the assigned human custodian or work profile. Asset assignment integrated with management inventory addresses the actual loss-investigation gap.