
Explanation:
The proposed solution creates:
Let's evaluate this against the requirements:
Requirement: Individual clusters that terminate after 120 minutes of inactivity, supporting Scala and R.
Issue: High Concurrency clusters do not support Scala. According to Azure Databricks documentation, High Concurrency clusters only support SQL, Python, and R workloads. Since data scientists need to use Scala, High Concurrency clusters are unsuitable for this workload.
Correct Approach: Data scientists should use Standard clusters, which:
Requirement: Shared cluster using Python and SQL.
Analysis: High Concurrency clusters are appropriate here because:
Requirement: Job cluster supporting Python, Scala, and SQL.
Issue: While Standard clusters do support Scala (unlike High Concurrency), the proposed solution incorrectly assigns the Standard cluster to jobs when it should be assigned to data scientists. Additionally, jobs typically benefit from High Concurrency clusters for better resource utilization and management.
The solution fails because:
Correct Answer: No, this solution does not meet the goal.
Ultimate access to all questions.
You need to create Azure Databricks clusters for three workloads with the following requirements:
Proposed Solution: You create a High Concurrency cluster for each data scientist, a High Concurrency cluster for the data engineers, and a Standard cluster for the jobs.
Does this solution meet the goal?
A
Yes
B
No
No comments yet.