先試後買

A. Option B

B. Option E

C. Option A

D. Option D

E. Option C

A. Option B

B. Option E

C. Option A

D. Option D

E. Option C

A. Option B

B. Option E

C. Option A

D. Option D

E. Option C

A. Enabling change tracking on the source table for the Cortex Search Service is optional; the service will still refresh automatically even if change tracking is disabled.

B. Cortex Search automatically handles text chunking and embedding generation for the source data, eliminating the need for manual ETL processes for these steps.

C. The

D. For optimal search results with Cortex Search, source text should be pre-split into chunks of no more than 512 tokens, even when using models with larger context windows like

E. To create a Cortex Search Service, one must explicitly specify an embedding model and manually manage its underlying infrastructure, similar to deploying a custom model via Snowpark Container Services.

A. In a table extraction task, if a specific cell (e.g., 'tablellitem') is empty, the resulting JSON will omit the 'value' key for that cell, but will still provide a 'score' indicating the model's confidence that the cell is empty.

B. If a question for an entity, like 'total_invoice_amount', does not find a corresponding value in a document, the JSON output for will contain a 'value' key with a 'null' string and a 'score' key indicating the model's confidence in the absence of the answer.

C. Processing a legal contract document that is 130 pages long will likely result in a '_processingErrors' message indicating that the document has too many pages.

D. If the extracted answer to a question for a single entity (e.g., is very long, it will be automatically truncated to a maximum of 2048 tokens.

E. A document written entirely in Ukrainian will be processed by Document AI, and the extracted information will be of satisfactory quality due to extensive multilingual support.

A. Option B

B. Option E

C. Option A

D. Option D

E. Option C

A. Option B

B. Option E

C. Option A

D. Option D

E. Option C

A. The role used to create the Cortex Search Service must be granted the 'SNOWFLAKE.CORTEX_USER database role.

B. The 'CREATE CORTEX SEARCH SERVICE command should specify a Snowpark-optimized warehouse for optimal performance, as it is designed for memory-intensive ML workloads.

C. Columns intended to be filterable in search queries must be explicitly listed in the 'ATTRIBUTES' field during service creation and must also be included in the source query for the service.

D. If the service is created using the Snowsight AI & ML Studio, its name will be double-quoted, and thus must be double-quoted when referenced in subsequent SQL queries.

E. To enable continuous updates of the search index as new tickets are added,

A. To optimize performance, queries calling the Cortex AI_PARSE_DOCUMENT function should be executed in a large warehouse (e.g., XL or larger), as bigger warehouses increase processing speed for this function.

B. All documents must be stored in an internal or external stage, but only internal stages support server-side encryption with the SNOWFLAKE_SSE type.

C. For HTML and TXT files, billing for AI_PARSE_DOCUMENT is based on each chunk of 3,000 characters, with the last chunk also being billed even if shorter.

D. Supported file formats for processing include PDF, PPTX, DOCX, JPEG, JPG, PNG, TIFF, TIF, HTML, and TX T, covering a wide range of common document and image types.

E. The maximum file size for any document processed by is AI_PARSE_DOCUMENT 100 MB, and it can handle up to 300 pages per document.

A. It focuses on identifying and returning a direct answer to a specific question contained within the provided source document.

B. It evaluates a text and returns a numeric score indicating the overall positive or negative sentiment.

C. It transforms an input document into a summarized version, reducing its length while preserving key information.

D. It is primarily designed to generate entirely new text based on a given prompt, much like a conversational AI.

E. It classifies an input text into one of several predefined categories provided by the user.

A. Cortex Guard can be configured with a custom message using the argument in the options object for both 'COMPLETE SQL function and the Cortex REST API.

B. Cortex Guard is inherently part of all Cortex LLM functions and does not require explicit enablement via 'guardrails: TRUE for SQL functions or the REST API.

C. When Cortex Guard is enabled and a response is deemed unsafe, the LLM-generated output is replaced with a predefined message, and only the input tokens for Cortex Guard processing ('guard_tokens') are billed, not the potentially unsafe completion tokens.

D. Cortex Guard operates by evaluating responses after the LLM has fully generated its content, and it incurs additional compute cost for both input and output tokens during its processing.

E. The underlying model for Cortex Guard is Meta's Llama Guard 3, and its processing costs are separate from the primary LLM inference costs.

A. Option B

B. Option E

C. Option A

D. Option D

E. Option C

A.

B.

C.

D.

E.

A. Option B

B. Option E

C. Option A

D. Option D

E. Option C