doc: update questionnaire

Author: iru

use-cases/_questionnaire.md

@@ -42,22 +42,33 @@ In what [Sysdig For Cloud Features](https://docs.sysdig.com/en/docs/sysdig-secur
   - Note: Sysdig offers many other ways of performing scanning, and we recommend you to [Check all Scanning options in the Vulnerability Management](https://docs.sysdig.com/en/docs/sysdig-secure/vulnerabilities/)
 
 
+<br/><br/>
 
 ## Example Selection
 
-|                   | Single                                                            |  Organizational |
+
+|                   | Single  `single-`                                                          |  Organizational `organizational-` |
 | --| -- | -- |
-| Deployment Type   | All Sysdig resources will be deployed within the selected account |  Most Sysdig resources will be deployed within the selected account, but some require to be deployed on member-accounts (for Compliance and Image Scanning) and one role is needed on the management account for cloudtrail event access |
-| Benefits          | Will only analyse current account                                 |  Handles all accounts (managed and member)
-| Drawbacks         | Cannot re-use another account Cloudtrail data (unless its deployed on the same account where the sns/s3 bucket is) | for scanning, a per-member-account access role is required
+| Deployment Type   | all Sysdig resources will be deployed within the selected account |  most Sysdig resources will be deployed within the selected account, but some require to be deployed on member-accounts (for Compliance and Image Scanning) and one role is needed on the management account for cloudtrail event access |
+| Target          | will only analyse current account                                 |  handles all accounts (managed and member)
+| Drawbacks         | cannot re-use another account Cloudtrail data (unless its deployed on the same account where the sns/s3 bucket is) | for scanning, a per-member-account access role is required
 
 With both examples `single` and `org`, you can customize the desired features to de deployed with the `deploy_*` input vars to avoid deploying more than wanted.
 
+### Compute Workload Type
+
+| Cloud | Example Options |
+| - | - | 
+| AWS | K8S `-k8s`, ECS `-ecs`, AppRunner `-apprunner` | 
+| GCP | K8S `-k8s`, CloudRun |
+| Azure | K8S `-k8s`, AzureContainerInstances |
+
+<br/><br/>
 ## Available Optionals
 
 We enable following optionals, to allow user to re-use their pre-existing / configured resources.
 
-|  Cloud |  Optioals | Related Input Vars | Other |
+|  Cloud |  Optionals | Related Input Vars | Other |
 | -- | --| -- | -- | 
 | AWS  | Cloudtrail-SNS | `cloudtrail_sns_arn`, (org only) `cloudtrail_s3_arn` | - |
 | | ECS, VPC, Subnet | `ecs_cluster_name`, `ecs_vpc_id`, `ecs_vpc_subnets_private_ids` | if used, the three are mandatory  |