In which situations should you enable strict updates for an iApp? (Select all that apply)

Question

Options

• AWhen the iApp template is being modified
• BWhen deploying an iApp on a test environment
• CWhen making manual changes to a deployed application service
• DWhen deploying critical application services that should not be altered

• A
  74% (39)
• B
  17% (9)
• C
  9% (5)

Explanation

Strict updates should be enabled when modifying an iApp template (A) because it enforces that all configuration changes flow through the template itself, preventing drift between the template definition and deployed objects. It should also be enabled for critical production services (D) because it locks down manually managed objects, ensuring no one accidentally or unauthorized alters the iApp-controlled configuration outside of the template. Option B is wrong - test environments are precisely where you'd disable strict updates to freely experiment with manual tweaks. Option C is the opposite of correct: strict updates block manual changes to deployed services; you must disable it first if direct edits are needed. Memory tip: Think "strict = template controls everything" - enable it when you want the template to be the single source of truth (modifying it or protecting it), disable it when humans need to touch things directly.

No community discussion yet for this question.