You must complete this task on the following cluster/nodes: Cluster | Master node | Worker node KSRS001 | ksrs00101-master | ksrs00101-worker1 You can switch the cluster/configuration context using th

You must complete this task on the following cluster/nodes: Cluster | Master node | Worker node KSRS001 | ksrs00101-master | ksrs00101-worker1 You can switch the cluster/configuration context using the following command: [candidate@cli] $ kubectl config use-context KSRS00101 Two tools are pre-installed on the cluster's worker node: sysdig, falco. Using the tool of your choice (including any non pre-installed tool), analyze the container's behavior for at least 30 seconds, using filters that detect newly spawning and executing processes. Store an incident file at /opt/KSRS00101/alerts/details, containing the detected incidents, one per line, in the following format: timestamp,uid/username,processName The following example shows a properly formatted incident file: 01:40:19.601363716,root,init 01:40:20.60601363716,nobody,bash 01:40:21.137163716,1000,tar Keep the tool's original timestamp-format as-is. Make sure to store the incident file on the cluster's worker node. You may use your browser to open one additional tab to access Falco's documentation.