Scenario: Hardware sizing for HCL Workload Automation 10.2 master with large plans. Beyond minimum, what is referenced for scaling?

• A.Fixed 16 GB RAM
• B.Liberty version dictates
• C.No scaling needed
• D.Container limits only
• E.Supported Hardware document for deployment unit specifics

Comment: *

Name: *

Email: *

Verification: *

In a complex scenario involving security file updates for global options access, carry forward customization, and console advanced settings: After setting enCarryForward=all, adding carryforward no to select job streams, enabling enRoleBasedSecurityFileCreation, and customizing TdwcGlobalSettings.xml for timeouts, which actions are required for full effect? (Select All that Apply)

• A.Clear browser cache for console changes
• B.Restart console server for advanced settings
• C.Propagate security file if centralized
• D.Run JnextPlan for carry forward changes
• E.Update optman for domain activation

Comment: *

Name: *

Email: *

Verification: *

In carry forward scenarios, what does the global carryStates option control precisely?

• A.External stream states
• B.Job stream states eligible for carry
• C.Dependency resolution states
• D.Resource quantities carried
• E.Job states included in carried forward job streams

Comment: *

Name: *

Email: *

Verification: *

Customizing e-commerce workload in HCL Workload Automation 10.2, VT.PEAK.DISCOUNT=25% carries forward incorrectly post-Black Friday, inflating discounts. To implement peak-season variable table with automatic reset post-event, which VT control prevents carry forward pollution?

• A.#VT PEAK DISC="25%" carry=event reset=blackfriday
• B.@VAR PEAK @CARRYLIMIT(event)
• C.VT PEAK.DISCOUNT="25%" @CARRY(event) @RESET(post)
• D.TABLE PEAK DISC="25%" CARRY=PEAKONLY RESET=AUTOMATIC

Comment: *

Name: *

Email: *

Verification: *

Configuring authentication HCL HWA 10.2 with custom JAAS module fails password complexity enforcement. Liberty auth_basicRegistry accepts 8-char passwords but policy requires 15+ chars. Required custom login module?

• A.securityUtility encode enforces complexity automatically
• B.basicRegistry password policy configured in server.xml
• C.LDAP handles password complexity validation
• D.Implement javax.security.auth.spi.LoginModule validatePassword() returning Status.SUCCESS only for compliant passwords

Comment: *

Name: *

Email: *

Verification: *