Kubernetes deployment of HCL Workload Automation 10.2 containers fails pod scheduling with "Insufficient cpu/memory" despite node allocatable 32CPU/128Gi. Helm chart requests 8CPU/32Gi for wa-server StatefulSet. Cluster autoscaler inactive. Which container deployment resource configuration using precise Kubernetes quantities optimizes scheduling for production workloads?

• A.resources: requests: cpu: 4 memory: 16Gi limits: cpu: 8 memory: 32Gi nodeSelector: workload: production
• B.helm install --set resources.requests.cpu=2 --set resources.requests.memory=8Gi --set replicaCount=3
• C.resources: limits: cpu: "8" memory: 32Gi requests: {} affinity: podAntiAffinity for wa-server replicas
• D.statefulSet.spec.template.spec.containers.resources.requests.cpu: 4000m memory: 16Gib

Comment: *

Name: *

Email: *

Verification: *

To uninstall an agent silently in HCL Workload Automation 10.2 on UNIX, which twsinst flag is used?

• A.-silent yes
• B.-quiet
• C.-unattended
• D.-noninteractive
• E.--prompt no

Comment: *

Name: *

Email: *

Verification: *

A DevOps team automating HCL Workload Automation 10.2 deployment uses composer templates to standardize job stream definitions across 10 engines, but template expansion fails with "unresolved global variable GLOBAL_ENV=prod". To configure templates that inherit global options and resolve environment-specific variables during plan generation, which template configuration integrates with Global Options carry forward mechanism?

• A.#GLOBAL VAR GLOBAL_ENV="${@global.option('environment')}"; @CARRY
• B.@DEFINE TEMPLATE vars="@global('GLOBAL_ENV')" carry.global=true
• C.TEMPLATE JSTREAM_STD @GLOBAL(GLOBAL_ENV) @OPTION(carryforward=yes)
• D.USE TEMPLATE WITH @GLOBAL.resolvedVars() option inherit=true

Comment: *

Name: *

Email: *

Verification: *

Scenario: HCL HWA 10.2 production MDM Netman process PID 12345 shows 100% CPU via top -p 12345. conman "displaymgr" shows all engines running normally. What precise command sequence stops Netman gracefully preserving database connections?

• A.monstop; db2 "db2stop"; ./tws_shutdown
• B.conman stopmon; conman end; kill -TERM 12345
• C.kill -QUIT 12345; tail -f $TWA_HOME/Netman.log
• D.conman "shutdn @;end"; sleep 30; pkill -f netman

Comment: *

Name: *

Email: *

Verification: *

Scenario: Critical jobs lost on rollover despite carryforward. Root cause likely?

• A.enCarryForward = no
• B.All of the above possible
• C.Global carryforward = none
• D.planman nocarryforward used
• E.Jobs lack carryforward attribute and not in qualifying cycles

Comment: *

Name: *

Email: *

Verification: *