Scenario: Running jobs continue after plan change, but their job stream is not carried forward. Where are they placed in the new plan?

• A.Original job stream name with suffix
• B.USERJOBS dedicated job stream
• C.Lost, require manual rerun
• D.CARRIEDJOBS system stream
• E.ORPHANEDJOBS

Comment: *

Name: *

Email: *

Verification: *

Managing HCL HWA 10.2 plan: 1000 shadow jobs from merged jobstreams conflict. conman "delp shadow*" fails wildcard syntax. Correct shadow job cleanup?

• A.conman "purge shadows"
• B.conman "delp @/SHADOW_"
• C.conman "cleanshadows"
• D.conman "deljob shadow"

Comment: *

Name: *

Email: *

Verification: *

Conman HCL HWA 10.2 batch processing 5000 dependency changes hangs on circular reference detection. Script: "deldep job JOB123@; adddep job JOB456@ JOB123".
What command line parameter accelerates dependency resolution?

• A.conman -timeout 1800 -novalidate "script.txt"
• B.conman -batch-nolock script.txt
• C.conman -depcheck=off "commands"
• D.conman -fastdep "deldep job JOB123@; adddep job JOB456@ JOB123"

Comment: *

Name: *

Email: *

Verification: *

Which workstation type in HCL Workload Automation 10.2 supports decentralized event rule monitoring?

• A.Z-centric exclusively
• B.Agents with monman process enabled
• C.Dynamic pools
• D.Standard agents
• E.Only master domain manager

Comment: *

Name: *

Email: *

Verification: *

AWS EKS HCL HWA 10.2 active-active HA certificate rotation fails; new wa-waserver certificates deployed but workstations report "SSL certificate verify failed". Old secrets remain. EKS IAM Roles for Service Accounts active. What certificate rollout ensures zero-downtime rotation?

• A.kubectl rollout restart statefulset wa-waserver-mdm1,wa-waserver-mdm2; kubectl rollout status
• B.Helm upgrade --reuse-values --wait --timeout=600s
• C.oc patch secret wa-pwd-secret --type merge -p '{"data.cert":"newvalue"}'
• D.Delete old PVC data-hwa-waserver; force recreation

Comment: *

Name: *

Email: *

Verification: *