Identify the Automated Installer's (AI) equivalent to jumpStart's finish scripts and sysidcfg files.

Question

Options

• AManifest files
• BSMF system configuration profile files
• CInstalladm create - client
• DIPS software package repository
• Einstalladm create-service
• Fsvccfg - s application/pkg/server setprop sysidcfg

• B
  89% (47)
• C
  2% (1)
• D
  6% (3)
• F
  4% (2)

Explanation

SMF system configuration profile files serve as AI's unified replacement for both JumpStart's sysidcfg (which configured system identity settings like locale, timezone, root password, and network) and finish scripts (which handled post-installation customization), by defining SMF service properties in XML that are applied automatically during and after installation.

Why the distractors are wrong:

• A (Manifest files): These define what to install - disk layout and packages - making them the equivalent of JumpStart's profile and rules files, not sysidcfg or finish scripts.
• C (installadm create-client): This is an administrative command to register a client with an install service, not a configuration artifact.
• D (IPS repository): This is the package delivery mechanism for Solaris 11 - unrelated to system configuration or post-install scripting.
• E (installadm create-service): Another administrative command, used to set up an AI install service, not to configure the installed system.
• F (svccfg ... sysidcfg): A distractor that uses "sysidcfg" in its syntax - it actually configures the IPS package server property, not system identification.

Memory tip: Think of SMF profiles as "XML finish scripts with system identity built in" - where JumpStart needed two separate files to configure and customize, AI consolidates both jobs into one SMF profile.

No community discussion yet for this question.