Refer to the exhibit. An engineer must enable access to Salesforce using Cisco Umbrella and Cisco Cloudlock. These actions were performed: From Salesforce, add the Cloudlock IP address to the allow…

Question

Exhibit

Options

• AFrom the Salesforce admin page, grant API access to Cloudlock.
• BFrom the Salesforce admin page, grant network access to Cloudlock
• CFrom the Cloudlock dashboard, grant API access to Salesforce.
• DFrom the Cloudlock dashboard, grant network access to Salesforce.

• A
  84% (41)
• B
  2% (1)
• C
  4% (2)
• D
  10% (5)

Explanation

Granting API access from the Salesforce admin page is the missing step because Cisco Cloudlock integrates with Salesforce through its API (via OAuth), not just at the network layer - without explicit API access granted in Salesforce, Cloudlock cannot inspect or enforce policies on Salesforce data, regardless of IP allow-listing or Cloudlock-side authorization.

Why the distractors are wrong:

• B is wrong because network access (adding the Cloudlock IP to the allow list) was already completed in the steps described - that's a network-level permission, not an API-level one.
• C is wrong because the Cloudlock side already authorized Salesforce - the remaining gap is on the Salesforce side, not in Cloudlock.
• D is wrong because "granting network access to Salesforce from the Cloudlock dashboard" is not how the integration works - Cloudlock doesn't control Salesforce's network permissions.

Memory tip: Think of it as a two-key lock - Cloudlock holds one key (authorization from the Cloudlock side, already done), but Salesforce must also turn its key by granting API access. Network access = "I know where you live," API access = "I trust you to read my data."

No community discussion yet for this question.