Databricks Certified Data Analyst Associate Exam 온라인 연습
최종 업데이트 시간: 2026년06월29일
당신은 온라인 연습 문제를 통해 Databricks Databricks Certified Data Analyst Associate 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Databricks Certified Data Analyst Associate 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 45개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Option E is correct. A major benefit of open source technologies and open data formats is avoiding vendor lock-in. Databricks supports open formats and interfaces so data can be used across tools and systems rather than being locked into a proprietary platform. Cloud integrations, governance, and workload scalability are Databricks benefits, but the specific benefit of embracing open source is avoiding vendor lock-in. Official Databricks extract: “Using open data formats and interfaces helps to avoid” vendor lock-in, and Databricks states that no proprietary data formats are used because Delta Lake and Iceberg are open source.
정답:
Explanation:
Option A is correct. Silver tables are cleaned, validated, and enriched versions of data, often still retaining detailed records. Gold tables are typically business-ready, analytics-focused, and more likely to contain aggregations, dimensional models, and reporting-ready metrics. Official Databricks extract: Silver is associated with “Data cleaning and validation,” while Gold is associated with “Dimensional modeling and aggregation.” Databricks also states that Gold data is often highly aggregated and tailored for analytics and reporting.
정답:
Explanation:
Option D is correct. ACID-compliant transactions improve reliability and data quality because writes are consistent and atomic rather than leaving partially written or corrupted states. Open formats and SQL access are important lakehouse capabilities, but the feature most directly tied to improved data quality over a traditional data lake is ACID transactions. Official Databricks extract: Delta Lake extends Parquet with a transaction log for “ACID transactions,” and Databricks states that Delta Lake adds ACID transactions and schema evolution for reliable, high-quality data.
정답:
Explanation:
Option D is correct. Cluster resizing caused by autoscaling is recorded as a cluster activity event, so the administrator should review the Cluster Event Log. Driver and executor logs are useful for application/runtime troubleshooting, not for the cluster resizing timeline. Ganglia shows metrics but is not the event timeline. Official Databricks documentation identifies cluster activity events as the place to retrieve cluster activity, and Databricks autoscaling documentation describes resize events such as “Cluster resize request started.”
정답:
Explanation:
Option B is correct. PIVOT rotates unique values from rows into separate columns, which is exactly the process of converting long-format data into wide-format data. UNPIVOT does the reverse. SUM is an aggregate function, WHERE filters rows, and TRANSFORM is not the SQL keyword used for this reshaping task. Official Databricks extract: the PIVOT clause “rotat[es] unique values from a column into separate columns.”
정답:
Explanation:
Option C is correct. DESCRIBE DATABASE customer360 returns metadata for the database/schema, including its filesystem location. DESCRIBE LOCATION is for external locations, not databases. DROP DATABASE deletes a database, ALTER DATABASE changes metadata/properties, and USE DATABASE changes the current database context. Official Databricks extract: DESCRIBE DATABASE is an alias for DESCRIBE SCHEMA, and DESCRIBE SCHEMA returns metadata including the schema’s “location on the filesystem.”
정답:
Explanation:
Option D is correct. Customer data is stored in the customer’s cloud account, such as object storage controlled by the customer. Databricks control-plane services manage platform components, while the customer’s data resides in the customer-controlled storage layer .
Official Databricks extract:
“Databricks doesn’t store your primary customer data. That lives in Amazon S3 or other systems you control.”
정답:
Explanation:
Option C is correct. To retrieve changes from a remote central Git repository into a local Databricks Git folder/Repo, the correct Git operation is Pull. Push sends local commits to the remote repository. Commit records local changes. Clone creates a new local copy. Merge combines branches but is not the operation described here. Official Databricks extract: “To pull changes from the remote Git repository, click Pull.”
정답:
Explanation:
Option D is correct. A temporary view is session-scoped and does not store physical data. It is suitable when the relational object is only needed in the current session or query context and should not be available to others in other sessions. A regular view also avoids copying physical data, but it is persistent and can be shared beyond the current session. Official Databricks extract: a view is a “virtual table that has no physical data,” and temporary views are scoped to the notebook/script or query level and cannot be referenced outside that scope.
정답: D
Explanation:
Option D is correct. The phrase “rank products within region by the sales” means each region must be ranked separately, so the window must use PARTITION BY region. The ranking must be based on highest sales first, so the window must use ORDER BY sales DESC.
Option A ranks across all regions together.
Option B ranks within product, not within region.
Option C does not specify the sales ordering. Official Databricks extract: rank() “returns the rank of a value compared to all values in the partition,” and its OVER clause must include ORDER BY.
정답:
Explanation:
Option E is correct. In the current Databricks UI, Data Explorer is known as Catalog Explorer. It is the location used to browse catalogs, schemas, tables, and views, review object metadata, and request or inspect access-related information. DBFS, Jobs, Dashboards, and Repos are not the table-permission review location. Official Databricks extract: users can navigate the catalog tree, open an object’s page, and request additional privileges from Catalog Explorer.
정답:
Explanation:
Option D is correct. Gold tables are refined, business-ready datasets used for analytics, dashboards, reporting, and other downstream consumption. A workload that queries aggregated data designed to feed a dashboard is therefore using Gold-layer data. Raw streaming ingestion belongs to Bronze, cleaning malformed records belongs to Silver, and aggregating uncleaned data is not the recommended Gold pattern. Official Databricks extract: the Gold layer “consists of aggregated data tailored for analytics and reporting” and is optimized for “queries and dashboards.”
정답:
Explanation:
Option A is correct. The user is not a member of the auditing group, so is_member("auditing") evaluates to false and the ELSE age >= 18 branch controls the filter. Rows with age >= 18 are returned; rows under 18 are omitted. “Age greater than 17” is equivalent to age >= 18 for integer ages. Official Databricks extract: is_member() “returns TRUE if the current user is a member” of the specified group, and Databricks describes dynamic views as views that can filter rows based on group membership.
정답:
Explanation:
Option B is correct. The problem is many users running small queries simultaneously, which is a concurrency issue. Increasing the maximum number of clusters lets the SQL warehouse scale out to serve more concurrent queries. Increasing cluster size is more useful for complex or resource-heavy queries, not necessarily many small simultaneous queries. Auto Stop reduces cost but does not improve active-query latency. Official Databricks extract: “You can increase the maximum clusters if you want to handle more concurrent users,” and Databricks recommends monitoring queued queries and adjusting maximum clusters.
정답:
Explanation:
Option D is correct. Databricks SQL alerts run a query on a schedule, evaluate a condition, and notify destinations when the condition is met. Since the requirement is notification through a messaging webhook, the alert should use a webhook alert destination. Official Databricks extract: alerts “run queries on a schedule and notify you when a condition that you define is met.” Databricks notification documentation also states that admins can configure alternate notification destinations using webhooks.