Allowing employees to access corporate resources through personally owned devices without mandatory VPN or Mobile Device Management (MDM) introduces significant security visibility, evidence-preservation, and endpoint-governance challenges.
Option A identifies the potential impact on electronic discovery and legal-hold processes. Without centralized device management, the organization may lack the technical authority or capabilities necessary to preserve relevant files, communication records, browser artifacts, and locally stored corporate information.
This can complicate forensic acquisition, regulatory investigations, and litigation-related preservation requirements.
Option C reflects the limitations of endpoint and network visibility under this architecture. The organization may retain monitoring capabilities for company-managed infrastructure, cloud applications, and centralized identity services, but it will have reduced visibility into activities performed directly on unmanaged personal devices.
The statement is somewhat simplified: unmanaged devices can still generate observable activity at application gateways, identity providers, and other monitored corporate services.
Option B is incorrect because comprehensive patch orchestration generally requires management enrollment, compatible tooling, or another enforceable endpoint-management mechanism.
Option D is incorrect because the architecture explicitly permits remote access without requiring VPN connectivity.
A stronger design would incorporate conditional access, device posture evaluation, browser isolation where appropriate, managed application controls, and comprehensive identity logging.
These measures can reduce exposure while preserving supported bring-your-own-device workflows.
Official reference / study topic: Splunk security capability architecture: BYOD, unmanaged endpoint coverage and forensic readiness.
===============
Submit