The most recent Cortex XDR agents are being installed at a newly acquired company. A list with endpoint types (i.e., OS, hardware, software) is provided to the engineer. What should be cross…

Question

Options

• AContent Compatibility Matrix
• BKernel Module Version Support
• CEnd-of-Life Summary
• DAgent Installer Certificate

• A
  3% (2)
• B
  95% (55)
• C
  2% (1)

Explanation

Kernel Module Version Support (B) is correct because Cortex XDR on Linux relies on kernel modules to function - the agent must be compatible with the specific kernel version running on each Linux system. When onboarding new endpoints, engineers must cross-reference Palo Alto's Kernel Module Version Support document to confirm that the agent can actually load and operate on those Linux kernels.

• A (Content Compatibility Matrix) relates to which threat content updates are compatible with which agent versions - useful for content management, not for verifying OS/kernel support during installation.
• C (End-of-Life Summary) tracks which agent versions are no longer supported by Palo Alto, not whether a specific Linux OS/kernel is compatible with the agent.
• D (Agent Installer Certificate) pertains to certificate signing and authentication of the installer package - irrelevant to OS/kernel compatibility checks.

Memory tip: Think "Linux = Kernel" - unlike Windows where you check OS version broadly, Linux compatibility lives or dies by the kernel, so the Kernel Module Version Support doc is your go-to for Linux endpoint validation.

No community discussion yet for this question.