An engineer mistakenly deleted three service profiles in Cisco UCS during a service window and...

A logical-configuration backup is the most targeted choice because Cisco UCS classifies service profiles as logical configuration objects. Cisco states that this XML backup includes service profiles together with related logical constructs such as VLANs, VSANs, pools, policies, and templates. It can be imported into the original fabric interconnect, allowing the administrator to recover the deleted profiles through a configuration import instead of restoring the entire UCS domain. The import should still be reviewed carefully: dependencies referenced by a service profile must exist or be included, and changes to an interface associated with a server can be disruptive. This makes a maintenance window and a preview of the import changes prudent.

Option A is broader than necessary. An all-configuration backup contains both system and logical settings, so it could contain the profiles, but it is not the most specific backup for this requirement. Option C is incorrect because a system-configuration backup contains administrative and global settings such as local users, roles, and locales; it does not target service profiles. Option D is intended for full-state disaster recovery. A full-state backup is a binary snapshot used to restore the complete UCS Manager domain and is inappropriate when only three logical objects must be recovered without disturbing unrelated fabric configuration. Therefore, importing the relevant logical-configuration backup provides the narrowest recovery scope and best aligns with the stated rollback objective. Cisco UCS Manager Administration Management Guide—Backup and Restore

================