In which scenarios is it appropriate to enable strict updates in an iApp configuration? (Select all that apply)

Question

Options

• AWhen regularly updating the iApp template files
• BWhen deploying critical application services that require high availability
• CWhen needing to prevent manual changes to a deployed application service
• DWhen deploying an iApp on a test or development environment

• A
  78% (42)
• B
  15% (8)
• D
  7% (4)

Explanation

Enabling strict updates in an iApp configuration serves two complementary purposes: enforcing template-driven consistency and protecting configuration integrity. Option A is correct because strict updates ensures that when iApp template files are revised, those updates propagate cleanly without conflicting manual edits already in place - the template remains the single source of truth. Option C is the core use case for strict updates: it explicitly locks the deployed application service so administrators cannot make out-of-band manual changes to objects managed by the iApp, preventing configuration drift.

Option B is a distractor - high availability is achieved through redundancy, failover, and traffic management features, not by locking template updates. Option D is the opposite of correct: test and development environments benefit from the flexibility to make manual adjustments freely, so strict updates would actually hinder experimentation and troubleshooting there.

Memory tip: Think of strict updates as a "configuration padlock" - you use it when you want the template to own the config (A, updating templates) and when you want to stop others from picking the lock (C, blocking manual changes). If you're in dev/test, leave the padlock off so you can tinker freely.

No community discussion yet for this question.