When making manual changes to a deployed application service that uses an iApp, what should you do to ensure the changes are preserved during future updates?

Question

Options

• AEdit the iApp template directly to include the changes.
• BUse the "force" option when applying updates to the iApp.
• CDisable strict updates temporarily and save the changes in the configuration.
• DBackup the BIG-IP device configuration after making the changes.

• A
  12% (3)
• B
  4% (1)
• C
  80% (20)
• D
  4% (1)

Explanation

Option C is correct because F5 BIG-IP iApps enforce strict updates by default, which means any manual changes to iApp-managed objects are automatically overwritten whenever the iApp is re-applied or updated. Disabling strict updates tells the iApp to stop enforcing exclusive control over its managed objects, allowing your manual changes to coexist and survive future iApp updates.

Why the distractors are wrong:

• A - Editing the iApp template affects the template itself (all future deployments), not the specific deployed instance where you made changes; it also risks breaking the template's logic.
• B - There is no "force" option in iApp updates that preserves manual changes; forcing an update would still overwrite them.
• D - A backup captures the current state but does nothing to prevent the iApp from overwriting your changes on the next update; you'd have to manually restore after every update.

Memory tip: Think of strict updates as a "lock" - the iApp locks its objects so nothing outside it can touch them. Disabling strict updates unlocks the objects, letting your manual edits live alongside the iApp's configuration. Unlock before you edit, or your changes will be overwritten.

No community discussion yet for this question.