When integrating Cisco ISE with Azure AD using SAML SSO:
B: The Azure AD metadata must be uploaded into ISE to establish trust and allow token validation.
D: External Identity Sources settings must be configured in ISE to recognize and process authentication requests via SAML-based identity providers like Azure AD.
These are mandatory steps for enabling browser-based SSO authentication in ISE as explained in SCAZT Section 2 (User and Device Security, Pages 42-44), which describes federated identity integration.
Note: Option A is already completed as stated in the prompt. Options C and E are not essential to the authentication flow in this SAML context.
Reference: Designing and Implementing Secure Cloud Access for Users and Endpoints (SCAZT), Section 2, Pages 42-44

After Cloudlock is integrated with Salesforce, full visibility into objects and data requires that Cloudlock has the "View All Data" permission enabled on the connected Salesforce account. This permission allows the Cloudlock API connection to access all user data, regardless of individual field-level or sharing rules. Without it, Cloudlock will be limited in its visibility scope.
As per SCAZT (Section 4: Application and Data Security, Pages 86-89), integration with SaaS platforms like Salesforce must include enabling comprehensive data visibility to perform effective risk analysis and policy enforcement.
Reference: Designing and Implementing Secure Cloud Access for Users and Endpoints (SCAZT), Section 4, Pages 86-89