{"id":21916,"date":"2026-09-25T10:04:45","date_gmt":"2026-09-25T10:04:45","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21916"},"modified":"2026-09-25T10:04:45","modified_gmt":"2026-09-25T10:04:45","slug":"snowflake-snowpro-advanced-data-engineer-practice-test-questions-and-exam-dumps-part7-q121-140","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/snowflake-snowpro-advanced-data-engineer-practice-test-questions-and-exam-dumps-part7-q121-140\/","title":{"rendered":"Snowflake SnowPro Advanced Data Engineer Practice Test Questions and Exam Dumps Part7 Q121-140"},"content":{"rendered":"

View Full <\/b>Snowflake SnowPro Advanced Data Engineer Exam Dumps<\/b><\/a> and Practice Test Dumps<\/b><\/h2>\n

 <\/p>\n

Question 121<\/b><\/h3>\n

Which command removes a table while preserving its recoverability?<\/b><\/p>\n

    \n
  1. DROP TABLE<\/span><\/li>\n
  2. DELETE TABLE<\/span><\/li>\n
  3. REMOVE TABLE<\/span><\/li>\n
  4. PURGE TABLE<\/span><\/li>\n<\/ol>\n

    Correct Answer: 1<\/b><\/p>\n

    Explanation:<\/b><\/p>\n

    DROP TABLE<\/span> removes the table object while allowing recovery through Snowflake’s retention mechanisms when the object remains within the applicable recovery period. This differs from operations that delete individual rows because the table object itself is removed. Data engineers should distinguish between dropping an object and permanently eliminating recoverable data. Understanding Snowflake’s retention behavior helps teams design safer operational procedures and provides an opportunity to recover accidentally dropped objects when the necessary retention conditions are still available.<\/span><\/p>\n

    Question 122<\/b><\/h3>\n

    Which statement permanently removes a table without Time Travel recovery?<\/b><\/p>\n

      \n
    1. DROP TABLE<\/span><\/li>\n
    2. DROP TABLE … PURGE<\/span><\/li>\n
    3. DELETE FROM<\/span><\/li>\n
    4. TRUNCATE TABLE<\/span><\/li>\n<\/ol>\n

      Correct Answer: 2<\/b><\/p>\n

      Explanation:<\/b><\/p>\n

      DROP TABLE … PURGE<\/span> permanently removes a supported table and bypasses the normal Time Travel recovery capability for that object. This makes it substantially different from a regular <\/span>DROP TABLE<\/span>, where the object may remain recoverable during the applicable retention period. Engineers should use permanent removal carefully because the ability to recover accidentally deleted data is reduced or eliminated. Before performing irreversible cleanup, teams should verify dependencies, retention requirements, and any organizational recovery policies associated with the data.<\/span><\/p>\n

      Question 123<\/b><\/h3>\n

      Which Snowflake capability supports restoring dropped objects within retention?<\/b><\/p>\n

        \n
      1. Fail-safe<\/span><\/li>\n
      2. Time Travel<\/span><\/li>\n
      3. Data Exchange<\/span><\/li>\n
      4. Query Acceleration<\/span><\/li>\n<\/ol>\n

        Correct Answer: 2<\/b><\/p>\n

        Explanation:<\/b><\/p>\n

        Time Travel preserves historical data and object states for supported recovery operations during the configured retention period. It enables capabilities such as querying earlier versions of data and recovering certain dropped objects. Data engineers can use Time Travel to investigate accidental changes, compare historical states, or restore objects when recovery conditions are satisfied. Time Travel should not be confused with Fail-safe, which serves a different recovery purpose and is not intended as a normal user-controlled historical query mechanism.<\/span><\/p>\n

        Question 124<\/b><\/h3>\n

        Which clause queries a table at an earlier historical point?<\/b><\/p>\n

          \n
        1. HISTORY AT<\/span><\/li>\n
        2. AS OF<\/span><\/li>\n
        3. PREVIOUS VERSION<\/span><\/li>\n
        4. TIMEPOINT<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2<\/b><\/p>\n

          Explanation:<\/b><\/p>\n

          Snowflake’s <\/span>AT<\/span> clause is used with Time Travel syntax to reference historical data at a specified timestamp, offset, or statement-related point. It allows engineers to inspect an earlier state of a table without modifying the current table contents. Historical queries are valuable for investigating data changes, recovering information, and validating pipeline behavior. The requested historical point must remain within the applicable retention period. Data engineers should choose the appropriate timestamp or statement reference based on the incident or analytical requirement being investigated.<\/span><\/p>\n

          Question 125<\/b><\/h3>\n

          Which clause identifies a point immediately before a specified statement?<\/b><\/p>\n

            \n
          1. BEFORE<\/span><\/li>\n
          2. PRIOR<\/span><\/li>\n
          3. EARLIER<\/span><\/li>\n
          4. PREVIOUS<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1<\/b><\/p>\n

            Explanation:<\/b><\/p>\n

            The <\/span>BEFORE<\/span> clause can be used with Snowflake Time Travel to reference data as it existed before a specified statement or timestamp-related point. This is useful when engineers need to inspect the state of a table immediately preceding a particular operation. Historical access can support troubleshooting, validation, and recovery workflows without altering the current object. When investigating an incident, selecting the correct statement identifier or timestamp is important because the historical result must correspond precisely to the state the engineer wants to examine.<\/span><\/p>\n

            Question 126<\/b><\/h3>\n

            Which feature provides historical access to changed table data?<\/b><\/p>\n

              \n
            1. Fail-safe<\/span><\/li>\n
            2. Time Travel<\/span><\/li>\n
            3. Secure Data Share<\/span><\/li>\n
            4. Search Optimization<\/span><\/li>\n<\/ol>\n

              Correct Answer: 2<\/b><\/p>\n

              Explanation:<\/b><\/p>\n

              Time Travel provides access to historical versions of supported Snowflake data within the applicable retention period. It can help engineers investigate accidental updates, deletions, or other changes by allowing historical queries against earlier table states. This capability is valuable for data engineering because pipelines can sometimes produce unexpected transformations or load results. Rather than modifying the current dataset immediately, engineers can inspect historical information first. Retention configuration determines how far back historical data can be accessed, so appropriate settings should reflect operational recovery requirements.<\/span><\/p>\n

              Question 127<\/b><\/h3>\n

              Which object is designed to expose queryable data from external files?<\/b><\/p>\n

                \n
              1. External table<\/span><\/li>\n
              2. Dynamic table<\/span><\/li>\n
              3. Temporary table<\/span><\/li>\n
              4. Materialized view<\/span><\/li>\n<\/ol>\n

                Correct Answer: 1<\/b><\/p>\n

                Explanation:<\/b><\/p>\n

                An external table represents data stored outside Snowflake while providing metadata that allows the external data to be queried from Snowflake. It is commonly used with data stored in supported cloud storage locations. Unlike a standard Snowflake table, the underlying records remain in the external storage system. External tables are useful in architectures where data should remain in a data lake while still being accessible through Snowflake SQL. Engineers should account for metadata refresh and external storage organization when designing these pipelines.<\/span><\/p>\n

                Question 128<\/b><\/h3>\n

                Which command refreshes metadata for an external table?<\/b><\/p>\n

                  \n
                1. ALTER EXTERNAL TABLE … REFRESH<\/span><\/li>\n
                2. REFRESH EXTERNAL TABLE<\/span><\/li>\n
                3. UPDATE EXTERNAL METADATA<\/span><\/li>\n
                4. SYNC EXTERNAL TABLE<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 1<\/b><\/p>\n

                  Explanation:<\/b><\/p>\n

                  ALTER EXTERNAL TABLE … REFRESH<\/span> can refresh the metadata associated with an external table so Snowflake can recognize applicable changes in the referenced external storage. This is important when new files are added or the external data layout changes. External tables rely on metadata describing files rather than loading all underlying records into native Snowflake storage. Data engineers should establish an appropriate refresh strategy so newly available source files become visible to queries without unnecessary metadata operations.<\/span><\/p>\n

                  Question 129<\/b><\/h3>\n

                  Which stage type is managed internally by Snowflake?<\/b><\/p>\n

                    \n
                  1. External stage<\/span><\/li>\n
                  2. Internal stage<\/span><\/li>\n
                  3. Cloud stage<\/span><\/li>\n
                  4. Remote stage<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 2<\/b><\/p>\n

                    Explanation:<\/b><\/p>\n

                    An internal stage is storage managed within Snowflake for staging files before loading or after unloading data. Internal stages can simplify data movement because engineers do not need to configure an external cloud-storage location for every staging workflow. External stages, by comparison, reference supported cloud storage locations outside Snowflake. Choosing between stage types depends on architecture, data-transfer requirements, governance, and integration needs. Internal stages are especially convenient for workflows where files need to be temporarily or directly staged within the Snowflake environment.<\/span><\/p>\n

                    Question 130<\/b><\/h3>\n

                    Which stage type references storage outside Snowflake?<\/b><\/p>\n

                      \n
                    1. User stage<\/span><\/li>\n
                    2. Table stage<\/span><\/li>\n
                    3. External stage<\/span><\/li>\n
                    4. Named internal stage<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 3<\/b><\/p>\n

                      Explanation:<\/b><\/p>\n

                      An external stage points to data stored in an external cloud-storage location supported by Snowflake. It can centralize connection details and file-location configuration for repeated loading or unloading operations. External stages are common in modern data-lake architectures because source files can remain in object storage while Snowflake accesses them through configured integrations or credentials. Engineers should secure external-stage access carefully and ensure storage permissions, integration settings, and file paths are aligned with the intended ingestion workflow.<\/span><\/p>\n

                      Question 131<\/b><\/h3>\n

                      Which identifier refers to files within a stage during COPY operations?<\/b><\/p>\n

                        \n
                      1. FILES<\/span><\/li>\n
                      2. OBJECTS<\/span><\/li>\n
                      3. SOURCES<\/span><\/li>\n
                      4. INPUT_SET<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1<\/b><\/p>\n

                        Explanation:<\/b><\/p>\n

                        The <\/span>FILES<\/span> option in <\/span>COPY INTO<\/span> allows engineers to specify particular staged files for processing. This can be useful when a pipeline needs to load a controlled subset of files rather than everything matching a broader stage selection. Explicit file selection can support targeted reprocessing, troubleshooting, or controlled ingestion. Engineers should understand that file-selection behavior interacts with Snowflake’s load metadata and duplicate-file tracking. Careful file management helps prevent unintended reloads while allowing legitimate recovery or replay operations.<\/span><\/p>\n

                        Question 132<\/b><\/h3>\n

                        Which COPY option uses a regular expression to select files?<\/b><\/p>\n

                          \n
                        1. FILTER<\/span><\/li>\n
                        2. PATTERN<\/span><\/li>\n
                        3. REGEX_FILES<\/span><\/li>\n
                        4. MATCH_FILES<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2<\/b><\/p>\n

                          Explanation:<\/b><\/p>\n

                          The <\/span>PATTERN<\/span> option in <\/span>COPY INTO<\/span> uses a regular expression to identify staged files that should be processed. This is useful when files follow predictable naming conventions such as dates, source identifiers, or data domains. Engineers can use patterns to narrow ingestion without manually listing every file. However, regular expressions should be tested carefully because an overly broad expression may include unwanted files, while an overly restrictive expression may exclude valid input. Good naming conventions make pattern-based ingestion easier to maintain.<\/span><\/p>\n

                          Question 133<\/b><\/h3>\n

                          Which COPY option removes successfully loaded files from a stage?<\/b><\/p>\n

                            \n
                          1. DELETE_AFTER_LOAD<\/span><\/li>\n
                          2. CLEANUP<\/span><\/li>\n
                          3. PURGE<\/span><\/li>\n
                          4. REMOVE_LOADED<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3<\/b><\/p>\n

                            Explanation:<\/b><\/p>\n

                            The <\/span>PURGE<\/span> option can remove successfully loaded files from the stage after a <\/span>COPY INTO<\/span> operation. This can help manage staged-file storage when source files no longer need to remain available after successful ingestion. Engineers should use this behavior carefully because deleting staged files can affect replay, auditing, or troubleshooting workflows. It is particularly important to establish whether another process or downstream recovery procedure depends on the original files before enabling automatic cleanup.<\/span><\/p>\n

                            Question 134<\/b><\/h3>\n

                            Which COPY option validates data without loading it into the target table?<\/b><\/p>\n

                              \n
                            1. VALIDATION_MODE<\/span><\/li>\n
                            2. CHECK_ONLY<\/span><\/li>\n
                            3. DRY_RUN<\/span><\/li>\n
                            4. LOAD_VALIDATE<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1<\/b><\/p>\n

                              Explanation:<\/b><\/p>\n

                              VALIDATION_MODE<\/span> allows engineers to validate files for loading-related errors without actually loading the data into the target table. This is useful when assessing source quality before committing a batch to production tables. Depending on the selected validation behavior, Snowflake can return information about records or files that would cause errors. Validation is valuable in ingestion pipelines because it can identify malformed input before it affects downstream data. Engineers should choose an appropriate validation strategy based on file volume and operational requirements.<\/span><\/p>\n

                              Question 135<\/b><\/h3>\n

                              Which load-history view records COPY activity for recent table loads?<\/b><\/p>\n

                                \n
                              1. LOAD_HISTORY<\/span><\/li>\n
                              2. TABLE_LOAD_LOG<\/span><\/li>\n
                              3. COPY_EVENTS<\/span><\/li>\n
                              4. INGESTION_HISTORY<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1<\/b><\/p>\n

                                Explanation:<\/b><\/p>\n

                                LOAD_HISTORY<\/span> provides information about loading activity for tables within the applicable information scope and retention behavior. It can help data engineers determine which files were processed, when loading occurred, and whether records were loaded successfully. Load-history information is valuable for troubleshooting ingestion failures, auditing pipeline activity, and investigating unexpected duplicates or missing data. Engineers should select the appropriate Snowflake metadata source based on the required scope, retention period, and operational reporting needs.<\/span><\/p>\n

                                Question 136<\/b><\/h3>\n

                                Which metadata field identifies when a scanned file began processing?<\/b><\/p>\n

                                  \n
                                1. METADATA$SCAN_TIME<\/span><\/li>\n
                                2. METADATA$START_SCAN_TIME<\/span><\/li>\n
                                3. METADATA$BEGIN_TIME<\/span><\/li>\n
                                4. METADATA$FILE_START<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2<\/b><\/p>\n

                                  Explanation:<\/b><\/p>\n

                                  METADATA$START_SCAN_TIME<\/span> provides metadata associated with when Snowflake began scanning the source file for the relevant operation. Such metadata can help with source tracing, diagnostics, and ingestion analysis when querying supported staged files. Combining scan-time information with filename and row metadata can provide useful context for understanding how records entered a pipeline. Engineers should remember that metadata columns are associated with supported file-querying scenarios and should not assume every metadata field is available in every Snowflake operation.<\/span><\/p>\n

                                  Question 137<\/b><\/h3>\n

                                  Which object coordinates SQL actions according to dependencies?<\/b><\/p>\n

                                    \n
                                  1. Stream<\/span><\/li>\n
                                  2. Task graph<\/span><\/li>\n
                                  3. File format<\/span><\/li>\n
                                  4. External table<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 2<\/b><\/p>\n

                                    Explanation:<\/b><\/p>\n

                                    A task graph coordinates multiple Snowflake tasks through defined predecessor and successor relationships. This allows data engineers to organize multi-step workflows such as ingestion, validation, transformation, aggregation, and downstream publishing. Dependencies ensure that a later task does not execute until its required upstream task has completed according to the graph’s orchestration rules. Task graphs are useful for complex pipelines because they provide structured execution relationships rather than requiring every transformation to run independently on unrelated schedules.<\/span><\/p>\n

                                    Question 138<\/b><\/h3>\n

                                    Which task property permits overlapping scheduled executions?<\/b><\/p>\n

                                      \n
                                    1. ALLOW_OVERLAPPING_EXECUTION<\/span><\/li>\n
                                    2. ENABLE_PARALLEL_RUNS<\/span><\/li>\n
                                    3. OVERLAP_TASKS<\/span><\/li>\n
                                    4. CONCURRENT_SCHEDULE<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 1<\/b><\/p>\n

                                      Explanation:<\/b><\/p>\n

                                      ALLOW_OVERLAPPING_EXECUTION<\/span> controls whether scheduled executions of a task can overlap under the supported task behavior. This setting matters when a task may take longer to complete than the interval between scheduled runs. Allowing overlap can increase concurrency, while preventing overlap can ensure that a new execution does not begin while an earlier execution remains active. Engineers should evaluate workload characteristics carefully because overlapping executions can introduce competing writes, duplicate processing, resource contention, or other pipeline-coordination concerns.<\/span><\/p>\n

                                      Question 139<\/b><\/h3>\n

                                      Which command suspends a running task schedule?<\/b><\/p>\n

                                        \n
                                      1. DISABLE TASK<\/span><\/li>\n
                                      2. ALTER TASK … SUSPEND<\/span><\/li>\n
                                      3. STOP TASK<\/span><\/li>\n
                                      4. PAUSE TASK<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 2<\/b><\/p>\n

                                        Explanation:<\/b><\/p>\n

                                        ALTER TASK … SUSPEND<\/span> changes a task so that its scheduled execution is suspended. This is useful when engineers need to temporarily stop automated processing during maintenance, incident investigation, deployment changes, or dependency updates. Suspending a task does not mean that the task definition itself is removed. After required work is completed, the task can be resumed using the corresponding task-management operation. Engineers should consider downstream and upstream dependencies before suspending production orchestration components.<\/span><\/p>\n

                                        Question 140<\/b><\/h3>\n

                                        Which Snowflake feature enables cross-region database replication?<\/b><\/p>\n

                                          \n
                                        1. Data Marketplace<\/span><\/li>\n
                                        2. Replication<\/span><\/li>\n
                                        3. Search Optimization<\/span><\/li>\n
                                        4. Dynamic Tables<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 2<\/b><\/p>\n

                                          Explanation:<\/b><\/p>\n

                                          Snowflake replication supports copying supported databases and related objects between Snowflake accounts and regions according to configured replication architecture. It can be used to support business continuity, disaster-recovery, and geographically distributed data-access requirements. Replication differs from data sharing because sharing provides governed access to data without the same objective of maintaining a replicated database copy. Data engineers designing cross-region architectures should evaluate supported objects, replication schedules, failover requirements, and consistency expectations before implementing the solution.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Snowflake SnowPro Advanced Data Engineer Exam Dumps and Practice Test Dumps   Question 121 Which command removes a table while preserving its recoverability? DROP TABLE DELETE TABLE REMOVE TABLE PURGE TABLE Correct Answer: 1 Explanation: DROP TABLE removes the table object while allowing recovery through Snowflake’s retention mechanisms when the object remains within […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21916"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=21916"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21916\/revisions"}],"predecessor-version":[{"id":21917,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21916\/revisions\/21917"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}