At which two stages are backups of the service configuration repository made?

Question

Options

• Aduring boot, after the early-manifest-import service finishes
• Bduring boot, before the manifest-import service starts
• Cduring manifest import, before the manifest-import service finishes
• Dduring manifest import, after the manifest-import service finishes
• Ewhen a service is modified using the svccfg command
• Fafter the last successful boot
• Gwhen the svcadm refresh command is executed

• B
  93% (40)
• F
  2% (1)
• G
  5% (2)

Explanation

In Oracle Solaris SMF (Service Management Facility), the service configuration repository (/etc/svc/repository.db) is automatically backed up at exactly two points: before the manifest-import service runs during boot (capturing the pre-import state), and after the manifest-import service successfully completes (capturing the post-import state). These checkpoints create the boot and manifest_import backup files, allowing recovery from a corrupted repository at either boundary.

Why the distractors are wrong:

• A is wrong because no service called "early-manifest-import" triggers a backup; the backup precedes manifest-import, it doesn't follow a prior stage.
• C is wrong because the post-import backup is made after completion, not before the service finishes.
• E is wrong because svccfg edits write directly to the live repository; they do not trigger automatic backups.
• F is wrong because "after the last successful boot" describes when boot environment snapshots may be referenced, not when repository backups are created.
• G is wrong because svcadm refresh reloads a service's configuration into memory; it does not back up the repository.

Memory tip: Think "bookends around manifest-import" - one backup before it starts, one after it ends. The keyword pair to anchor is before/after the manifest-import service, with "during boot" being the context for the first backup.

No community discussion yet for this question.