Content packages in SAP Build Work Zone, advanced edition, serve as the primary mechanism for lifecycle management. They are used to bundle various configuration and content items, such as apps, roles, catalogs, groups, spaces, and pages, created in a source system (e.g., development). This bundle forms a single, transportable, and deployable unit (an .mtar file) that can be imported into a target system (e.g., quality assurance or production), ensuring consistency across the landscape.

B. Web content artifacts to a single deployable unit (package)

This is too specific. Content packages include structural and authorization artifacts like roles and catalogs, which are not solely "web content artifacts."

C. Development and content artifacts to an archive for optimized storage

The primary purpose is deployment and transport between systems, not long-term archival or optimized storage. The package is a transport container.

---

1. SAP Help Portal: SAP Build Work Zone

Advanced Edition - Administration Guide.

Section: Lifecycle Management > Transporting Your Content

Content: The documentation explicitly states

"You can transport your content items from a source to a target subaccount. To do so

you export the content items from the source subaccount as a package

and then you import this package to the target subaccount." This confirms the function of bundling artifacts into a deployable package for transport. It lists exportable items like apps

catalogs

groups

and roles

which fall under "development and content artifacts."

2. SAP Help Portal: SAP Build Work Zone

Advanced Edition - Administration Guide.

Section: Lifecycle Management > Export a Package

Content: This section details the process of creating a package (.mtar file) from selected content items. This reinforces that the package is a "single deployable unit" containing various artifacts

not just an archive for storage or limited to web content.