Had something like this in a mock. It's A, just one node has to be listed in the SRV record for XMPP federation to work technically. Optional to include more for redundancy but not required. Anyone pick something else?

Yeah, this wording always gets me on Cisco. Option A is the only one that deals directly with how SAML messages are actually transported, like via SOAP or HTTP POST. Profiles (C) are more about application-specific use cases. Seen similar Qs in practice sets. Think it's A unless Cisco changed something up.

I don't think it's B, pretty sure D is right here. AXL is used after install to verify the UCM version matches what's specified, not just checking device status. B sounds like a distractor from previous versions. Anyone see this worded differently?

C or D? Bindings does define how SAML messages get transported (like HTTP POST), but profiles sometimes trip me up with use-case stuff. I’m leaning D since it’s about delivery, not behavior. Not 100% sure though-someone double check?

Yeah, it's D here. Bindings specify the actual transport method used to send SAML messages, like HTTP POST or Redirect. Profiles are more about how the SAML protocol is applied in specific use cases, and metadata just describes config info for parties. I think D is the only one that fits, but let me know if I'm missing something.

I thought it starts with B, since the user is usually sent to the IdP to authenticate before anything happens. But actually now that I think about it, if the initial step is always user action, then redirect (B) only happens after they try to access something. Really depends on whether you count hitting the protected site as part of the flow. So I went with B here-someone correct me if I’m missing something?

I get why some are saying B, since the SSO protocol technically starts at the redirect to the IdP. But I think D is still right here, since web-based SSO always begins with the user requesting access to the protected service-the app/resource has to trigger the whole flow first. Cisco wording can be vague sometimes though. Anyone else see practice questions ask it this way?

D is right, but does the question assume the user starts on the protected app or are they already at the IdP? If they begin at IdP, B might make sense, but usually it kicks off when accessing the service first.

Going with B and D for this one. The UCM should be set as the registration server, and config files come from the TFTP at 10.11.20.201, so those two snippets fit. Pretty sure, but I'd double-check if any special Jabber config applies.

Had something like this in a mock, it's B and D. The IPs match the roles for UCM softphone and config file server. Seen that combo more than once.

I don't think it's C. D makes more sense if we're talking about the DNS record Jabber would use to find the TFTP server for config files, especially when service discovery isn't being used or for fallback. Anyone else seeing this as a possible trap with C vs D?