Which two statements about the maintenance policy configurations available from the Cisco UCS Manager GUI are true? (Choose two.)
A. A maintenance policy can be defined for the service profile associated to a server and for updating a service profile bound to one or more service profiles.
B. A maintenance policy is used to configure a nondisruptive upgrade of the Cisco UCS Fabric Interconnects.
C. A maintenance policy can defer the direct deployment of firmware images for components that use neither the host firmware nor the management firmware packages available in the Cisco UCS Manager, such as fabric interconnects and IOMs.
D. A maintenance policy can deploy service profile changes immediately, when acknowledged by an admin user or automatically at the time specified in the schedule.
E. A maintenance policy can be used only to apply nondisruptive service profile changes to servers.
Brand, u r right with ur 1st answer – A,D
A maintenance policy determines how Cisco UCS Manager reacts when a change that requires a server reboot is made to a service profile associated with a server or to an updating service profile bound to one or more service profiles
I don’t think answer B is relevant to the maintenance policy because the policy simply controls the behavior of servers and not Fabric Interconnects. I think it’s A and D because it’s true that we can define a maintenance policy for a service profile or service profiles created from a template by assigning it to an updating template.
I think it’s A and D for this question
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-2/b_UCSM_GUI_Configuration_Guide_2_2/deferring_deployment_of_service_profile_updates.html#concept_3735BFD6DA5A49CF90B1B4EEE6BCBF25
but I guess I missed the “and for updating a service profile bound to one or more service profiles.” in answer A which makes it a wrong answer. And in this case, I believe answer D and E is the correct ones. It’s possible to create a maintenance policy that enforces user acknowledgment to reboot a server that helps to apply disruptive changes to servers without rebooting until an administrator acknowledges these changes.