Final answer:
The two true statements about Cisco UCS management tools' APIs are that UCS Director's APIs can be XML or JSON-encoded and require an API key for authentication, and UCS Manager's APIs are XML-encoded and require a cookie for authentication.
Step-by-step explanation:
The question pertains to Cisco Unified Computing System (UCS) management tools and their associated API interactions. In regard to the statements provided:
- UCS Manager indeed utilizes XML to encode API interactions. The authentication part is also accurate; however, it involves using a session cookie obtained after logging in, not Base64-encoded credentials directly in the HTTP header.
- Cisco UCS Director API does allow for interactions to be XML- or JSON-encoded. Authentication for the UCS Director API does require an API key in the HTTP header.
- Cisco Intersight APIs interact using only JSON encoding, not XML, and authenticate through an API key and secret key pair techniques, rather than just an API key.
Based on this information, the correct statements about Cisco UCS APIs are:
- UCS Director API interactions can be XML- or JSON-encoded and require an API key in the HTTP header for authentication (Statement B).
- UCS Manager API interactions are XML-encoded and requires a cookie in the method for authentication (Statement D).