What are two main features of enabling Cloudlock in a customers environment? (Choose two)

Question

Options

• ACloudlock connects via Oauth
• BCloud App security works on plug-in
• CEasily creates network lags for different users
• DIt takes less than five minutes to enable per platform
• EProtects against cloud-native malware

• A
  2% (1)
• B
  2% (1)
• C
  4% (2)
• D
  91% (43)

Explanation

Enabling Cloudlock in a customer environment stands out for its rapid, agentless deployment - each platform can be activated in under five minutes (D) because Cloudlock is cloud-native and requires no hardware or software installation. It also actively protects against cloud-native malware (E) through its Apps Firewall, which detects and blocks malicious third-party cloud applications targeting the environment.

Why the distractors are wrong:

• A - While Cloudlock does use OAuth to connect to cloud platforms, OAuth connectivity is the mechanism, not a promoted feature benefit; it's also incomplete as a standalone answer.
• B - Cloudlock is agentless and API-based, not plug-in based; plug-in architecture describes other tools (e.g., older proxy-based CASBs).
• C - Network lags are a drawback, never a feature; Cloudlock's cloud-native model is specifically designed to avoid introducing latency.

Memory tip: Think of Cloudlock's two selling points as "Fast + Safe" - Fast to deploy (under 5 minutes per platform) and Safe from cloud-native threats (malware protection). If an answer sounds like a flaw (lags) or describes a mechanism rather than a benefit (OAuth), eliminate it.

No community discussion yet for this question.