Free Salesforce Data 360 Consultant Practice Test Questions

Explanation:

This question tests the consultant's understanding of file federation configuration in Data 360, specifically the role of the manifest file when connecting to an external data lake like Azure Blob Storage. File federation allows Data 360 to read data directly from external storage without ingesting it. The manifest file acts as a pointer or catalog that tells Data 360 which files to read and how to interpret them.

✅ Correct Option: C. It defines metadata and paths to identify specific files for the data stream and track updates.
The manifest file serves as a configuration blueprint for file federation. It contains metadata about the source files—including file paths, schemas, formats, and timestamps—allowing Data 360 to locate the correct files in Azure Blob Storage and understand their structure. Additionally, it enables incremental processing by tracking which files have already been read, so only new or updated files are processed on subsequent runs.

❌ Incorrect Option: A. It reduces the file size of the source data before Data 360 attempts to read it.
This is incorrect. The manifest file does not perform any compression or file size reduction. Data size reduction, if needed, would be handled by the source system or via separate ETL processes before files are placed in the data lake.

❌ Incorrect Option: B. It is used to manually map source fields to the Cloud Information Model.
This is incorrect. Field mapping to the Cloud Information Model is handled within the data stream configuration in Data 360, not within the manifest file. The manifest file identifies which files to read, while mapping is a separate configuration step.

❌ Incorrect Option: D. It provides the PGP public key required to decrypt the federated data files.
This is incorrect. Encryption and decryption keys, including PGP keys, are managed through separate security configurations such as key stores or credential management in Data 360. The manifest file does not handle encryption keys.

🔧 Reference:
→ Salesforce Data Cloud File Federation Documentation – Confirms that manifest files define metadata, file paths, and schemas for federated data streams, enabling incremental processing by tracking processed files.

Explanation:

This question tests knowledge of Salesforce Data Cloud's data access patterns for external data sources. The key requirements are handling a large historical Snowflake dataset with heavy analytics queries, high throughput performance, and periodic — not real-time — freshness needs, which directly points to a caching-based federation strategy.

✅ D. Query Federation with Acceleration (Caching)
Query Federation with Acceleration caches query results from the external Snowflake source within Data Cloud, enabling high-throughput analytics without repeatedly hitting the source system. Since real-time freshness is not required, periodic cache refresh aligns perfectly with the use case. This pattern delivers fast query performance at scale while minimizing load on the Snowflake environment.

❌ A. Query Federation Without Acceleration (Live or Direct Access)
Live query federation executes queries directly against Snowflake at runtime without caching. For heavy analytics workloads with high throughput, this creates significant latency and load on the source system. Without acceleration, repeated complex queries against large historical datasets would result in poor performance, making it unsuitable for this scenario.

❌ B. Ingest Data into Data 360 as a Data Lake Object (DLO)
Ingesting the full historical Snowflake dataset as a DLO involves physically moving large volumes of parquet data into Data Cloud storage. This adds unnecessary ingestion overhead, storage costs, and pipeline complexity. Since the data already resides in Snowflake, federation with caching is a more efficient and architecturally appropriate pattern.

❌ C. File Federation
File Federation is designed to query external files stored directly in object stores such as Amazon S3 or Google Cloud Storage. While the data exists as parquet files, the primary access layer here is Snowflake — not the raw object store. File Federation bypasses Snowflake entirely and does not leverage its structure or query optimization capabilities.

🔧 Reference:
→ Query Federation – Salesforce Help
Confirms that Query Federation with Acceleration caches results from external sources like Snowflake, enabling high-throughput periodic analytics without requiring real-time data access or full data ingestion.