{"id":16367,"date":"2026-09-19T06:44:43","date_gmt":"2026-09-19T06:44:43","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=16367"},"modified":"2026-09-19T06:44:43","modified_gmt":"2026-09-19T06:44:43","slug":"snowflake-snowpro-advanced-architect-practice-test-questions-and-exam-dumps-part14-q261-280","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/snowflake-snowpro-advanced-architect-practice-test-questions-and-exam-dumps-part14-q261-280\/","title":{"rendered":"Snowflake SnowPro Advanced Architect Practice Test Questions and Exam Dumps Part14 Q261-280"},"content":{"rendered":"<h1><\/h1>\n<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/snowpro-advanced-architect-exam-dumps\"><b>Snowflake SnowPro Advanced Architect Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<h3><b>Question 261<\/b><\/h3>\n<p><b>What type of retrieval does Cortex Search combine?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Batch and streaming retrieval<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Relational and transactional retrieval<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Local and remote retrieval<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Vector and keyword retrieval<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Cortex Search uses a hybrid retrieval approach that combines vector search with keyword search. Vector retrieval helps identify content that is semantically similar to a query, while keyword retrieval is useful for exact terms, names, identifiers, and other literal matches. The combination provides a broader retrieval strategy than relying on only one technique. Cortex Search can then use semantic reranking to improve the relevance of returned results. For an architect, this hybrid model is useful when an application needs both conceptual matching and precise textual matching. The other options describe unrelated retrieval architectures and are not the retrieval model used by Cortex Search.<\/span><\/p>\n<h3><b>Question 262<\/b><\/h3>\n<p><b>What does Cortex Search primarily serve?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Text search experiences<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse billing reports<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role inheritance trees<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database backup catalogs<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Cortex Search is designed primarily for search experiences over Snowflake data, especially text-oriented content. It can support enterprise search applications and retrieval-augmented generation workflows where relevant information must be located before an AI model generates a response. The service provides a managed search layer instead of requiring organizations to build an independent search infrastructure for every use case. Warehouse billing, role inheritance, and backup management are separate administrative or governance concerns. Therefore, architects designing an enterprise search or RAG application can consider Cortex Search as the retrieval component responsible for locating relevant information from governed Snowflake data.<\/span><\/p>\n<h3><b>Question 263<\/b><\/h3>\n<p><b>What component provides compute for Snowpark Container Services?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Virtual warehouse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Compute pool<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database schema<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search index<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snowpark Container Services uses compute pools to provide the infrastructure required for containerized workloads. A compute pool consists of virtual machine nodes that host containerized applications and services. This makes compute pools different from virtual warehouses, which primarily provide compute for SQL query processing and related Snowflake workloads. A database schema organizes database objects, while a search index supports retrieval operations. When designing a container-based application architecture, the architect must therefore account for the appropriate compute pool configuration, including the available resources and scaling requirements needed by the deployed container workloads.<\/span><\/p>\n<h3><b>Question 264<\/b><\/h3>\n<p><b>What can Cortex Search provide to an RAG application?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse resizing instructions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database ownership metadata<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Relevant retrieved context<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Authentication certificates<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">In a retrieval-augmented generation architecture, Cortex Search can retrieve relevant information that is then supplied to an AI model as contextual input. This creates a separation between retrieval and generation. The search service locates information from organizational data, while the language model uses the retrieved context to formulate an answer. This approach can help ground AI responses in enterprise-specific information rather than depending only on the model&#8217;s general knowledge. Warehouse resizing instructions, ownership metadata, and authentication certificates do not perform the retrieval role. Therefore, relevant retrieved context is the architectural output that Cortex Search can provide to an RAG application.<\/span><\/p>\n<h3><b>Question 265<\/b><\/h3>\n<p><b>Which environment supports managed Snowflake notebook development?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Workspaces Notebooks<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource Monitors<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Network Policies<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Account Replication<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Workspaces Notebooks provide a managed environment for notebook-based development inside Snowflake. They are designed for data science, machine learning, and analytical development while remaining integrated with Snowflake data and governance capabilities. The notebook environment can use container-based infrastructure for workloads that require additional packages or specialized compute. Resource monitors instead focus on consumption controls, network policies govern network access, and account replication addresses data availability across environments. For architects designing a centralized data-science environment, Workspaces Notebooks can reduce the need to move governed data into a completely separate development platform.<\/span><\/p>\n<h3><b>Question 266<\/b><\/h3>\n<p><b>What enables exact textual matching in Cortex Search?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Vector-only indexing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Keyword search<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Container scheduling<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Notebook kernels<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Keyword search provides lexical matching in Cortex Search. This is especially valuable when a query contains exact names, identifiers, product codes, phrases, or other terms where literal matching is important. Vector retrieval serves a complementary purpose by identifying semantically similar content even when the wording differs. Cortex Search combines these retrieval methods to support a broader range of search requirements. Container scheduling and notebook kernels are execution concepts and do not determine how text is matched within Cortex Search. Therefore, keyword search is the component responsible for exact or lexical matching in a Cortex Search architecture.<\/span><\/p>\n<h3><b>Question 267<\/b><\/h3>\n<p><b>What is a compute pool composed of?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database objects<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search attributes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Virtual machine nodes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SQL procedures<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A compute pool is composed of virtual machine nodes that provide infrastructure for Snowpark Container Services. These nodes supply the compute resources required to execute containerized applications. Depending on the workload, the compute pool can provide different resource configurations suitable for the applications being deployed. Database objects organize data, search attributes support filtering or search behavior, and SQL procedures contain executable database logic. Understanding the composition of a compute pool is important because container workloads use this infrastructure instead of relying on the same compute model as ordinary SQL queries. Therefore, virtual machine nodes are the fundamental infrastructure units within a compute pool.<\/span><\/p>\n<h3><b>Question 268<\/b><\/h3>\n<p><b>Which runtime can provide GPU resources for Streamlit applications?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse runtime<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SQL runtime<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Container runtime<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Metadata runtime<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Streamlit container runtime can provide access to GPU resources through Snowpark Container Services infrastructure. This makes it suitable for applications requiring specialized computation, advanced machine learning libraries, or workloads that benefit from GPU acceleration. The container runtime also supports broader Python package requirements and other capabilities that can be useful for more sophisticated applications. A warehouse runtime follows a different compute model, while SQL and metadata runtimes are not the relevant Streamlit execution environments. Therefore, architects designing GPU-enabled Streamlit applications should consider the container runtime and its associated compute-pool architecture.<\/span><\/p>\n<h3><b>Question 269<\/b><\/h3>\n<p><b>What is the purpose of Cortex Search attributes?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Defining warehouse sizes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Filtering search results<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Assigning account roles<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Creating database replicas<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Cortex Search attributes can be used to filter search results based on structured information associated with indexed content. For example, an enterprise search application could allow users to narrow results according to department, language, document type, region, or another supported attribute. This complements the service&#8217;s semantic and keyword retrieval capabilities by adding structured filtering. Warehouse sizing is a compute concern, role assignment belongs to authorization, and database replicas address availability or data distribution. Therefore, attributes are useful when an architect wants to provide users with additional controls for narrowing the results returned by a Cortex Search service.<\/span><\/p>\n<h3><b>Question 270<\/b><\/h3>\n<p><b>What can happen when a long-running container stops?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snowflake can restart the container<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The database is automatically deleted<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">All roles are revoked<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search indexes are permanently removed<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Long-running services in Snowpark Container Services are designed to remain available over time. If a container within such a service stops unexpectedly, Snowflake can restart the container as part of the managed service lifecycle. This behavior helps maintain application availability without requiring an administrator to manually recreate the service after every unexpected container termination. The event does not inherently delete databases, revoke roles, or permanently remove search structures. Architects should distinguish long-running services from job services because their lifecycle behavior is different. A long-running service is therefore appropriate when the application needs an ongoing endpoint or continuously available containerized process.<\/span><\/p>\n<h3><b>Question 271<\/b><\/h3>\n<p><b>Which Cortex Search method supports semantic similarity?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Keyword-only matching<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Vector retrieval<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse queuing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role traversal<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Vector retrieval enables semantic similarity by representing content and queries in a form that allows conceptually related information to be identified even when the exact wording differs. This is particularly useful for natural-language questions, where users may express an idea differently from the language used in source documents. Cortex Search combines vector retrieval with keyword retrieval, allowing both semantic and lexical signals to contribute to search results. Warehouse queuing and role traversal have no role in semantic search. Therefore, vector retrieval is the capability that allows Cortex Search to identify content based on conceptual similarity rather than requiring exact textual overlap.<\/span><\/p>\n<h3><b>Question 272<\/b><\/h3>\n<p><b>What can the Streamlit container runtime provide?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Broader Python package support<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Automatic database cloning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Mandatory cross-region replication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Elimination of application secrets<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Streamlit container runtime can provide broader Python package support than a more restricted execution environment. This is important for applications that depend on specialized libraries, frameworks, or runtime dependencies that are not easily accommodated by a conventional Streamlit environment. The container runtime can also support capabilities such as GPU resources, long-running applications, and secure secrets handling. It does not automatically clone databases, require cross-region replication, or eliminate secrets. For architects, the broader package environment can be a significant reason to choose the container runtime when application dependencies exceed the capabilities of a simpler runtime model.<\/span><\/p>\n<h3><b>Question 273<\/b><\/h3>\n<p><b>Which service type ends after its workload exits?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Long-running service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Interactive search service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Job service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Notebook service<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A job service is intended for finite container workloads that complete and then terminate. When the workload finishes execution, the job service does not remain available as a continuously running application endpoint. This makes it appropriate for bounded processing tasks such as batch-style computation or one-time containerized operations. Long-running services have a different lifecycle because they are intended to stay active and can be managed for continued availability. Search and notebook environments have separate purposes and lifecycle models. Therefore, when an architect needs a container workload to execute and finish rather than remain continuously available, a job service is the appropriate service type.<\/span><\/p>\n<h3><b>Question 274<\/b><\/h3>\n<p><b>Which mechanism lets Streamlit access configured secrets?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">st.secrets<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search attributes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query history<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File formats<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Streamlit applications can use <\/span><span style=\"font-weight: 400;\">st.secrets<\/span><span style=\"font-weight: 400;\"> to access configured secrets without embedding sensitive values directly into application source code. This is important for applications that require credentials, tokens, or other protected configuration values. Keeping sensitive information outside application code improves maintainability and reduces the risk of exposing credentials through source files. Search attributes are related to search filtering, query history provides information about executed queries, and file formats describe staged-file structure. Therefore, <\/span><span style=\"font-weight: 400;\">st.secrets<\/span><span style=\"font-weight: 400;\"> is the mechanism associated with accessing configured secret values within Streamlit applications.<\/span><\/p>\n<h3><b>Question 275<\/b><\/h3>\n<p><b>What does Cortex Search create for efficient serving?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A role hierarchy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A search-optimized representation of source data<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A failover account<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A virtual warehouse cluster<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Cortex Search processes source data into structures designed to support efficient search serving. The service maintains a representation of the source content that allows retrieval operations to be performed efficiently instead of repeatedly processing the original source query from scratch for every search request. This architecture is important for low-latency search applications where users expect results quickly. Role hierarchies concern authorization, failover accounts concern continuity, and warehouse clusters provide traditional Snowflake compute. Therefore, a search-optimized representation of the source data is an important architectural component behind efficient Cortex Search serving.<\/span><\/p>\n<h3><b>Question 276<\/b><\/h3>\n<p><b>What powers Snowflake Notebooks in Workspaces?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Standard SQL worksheet<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Container Runtime<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File transfer service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query result cache<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snowflake Notebooks in Workspaces use a managed notebook environment designed for data science and machine learning development. The notebook experience can use container-based infrastructure to provide additional runtime flexibility and specialized compute resources. This makes the environment different from a standard SQL worksheet, which is primarily designed for SQL execution and interactive database work. File transfer services and query result caches are supporting mechanisms rather than notebook execution environments. Architects should understand the notebook runtime because it affects package availability, compute options, resource requirements, and how data-science workloads are integrated with the broader Snowflake platform.<\/span><\/p>\n<h3><b>Question 277<\/b><\/h3>\n<p><b>Which Cortex Search feature combines retrieval approaches?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hybrid retrieval<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database replication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse federation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role chaining<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Hybrid retrieval combines different search techniques so that a service can use both semantic and lexical signals when finding relevant information. In Cortex Search, vector retrieval can identify conceptually related content while keyword retrieval can capture exact textual relationships. This combination is useful for enterprise search because user queries may contain both natural-language concepts and precise terms. Database replication, warehouse federation, and role chaining address different architectural requirements. A hybrid retrieval design therefore provides a more flexible search strategy than relying exclusively on one retrieval method and can improve the relevance of results across varied query patterns.<\/span><\/p>\n<h3><b>Question 278<\/b><\/h3>\n<p><b>What compute does a Streamlit container runtime use?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A database clone<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A compute pool<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A replication group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A search attribute<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Streamlit container runtime uses compute provided through Snowpark Container Services infrastructure, with a compute pool supplying the resources required for the containerized application. The compute pool determines the available infrastructure for the application and can be configured according to workload requirements. A database clone is a data-copy mechanism, a replication group supports replication architectures, and a search attribute provides metadata used for filtering search results. None of those objects provides the execution infrastructure for a containerized Streamlit application. Therefore, architects deploying this runtime need to account for the appropriate compute-pool configuration.<\/span><\/p>\n<h3><b>Question 279<\/b><\/h3>\n<p><b>Which workload can benefit from GPU-backed notebooks?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Simple metadata lookup<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role administration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Machine learning workloads<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database naming<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Machine learning workloads can benefit significantly from GPU-backed notebook environments because many training and inference operations can take advantage of parallel GPU computation. Snowflake&#8217;s notebook environment can provide access to specialized compute through its container-based runtime, allowing data scientists to work with governed Snowflake data while using resources appropriate for demanding ML workloads. Metadata lookups and database naming do not normally require GPU acceleration, while role administration is primarily a security and governance activity. Therefore, machine learning workloads represent the most relevant use case for GPU-enabled notebook execution.<\/span><\/p>\n<h3><b>Question 280<\/b><\/h3>\n<p><b>Which architecture suits a continuously available container endpoint?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Job service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Long-running service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Batch worksheet<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary table<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A long-running service is designed for containerized applications that need to remain available rather than terminate after completing a finite task. This model is appropriate for application endpoints, APIs, services, and other workloads that need ongoing availability. Snowflake manages the service lifecycle and can restart containers when necessary. A job service is instead designed for finite workloads that end after their processing completes. Batch worksheets and temporary tables are unrelated to container-service lifecycle management. Therefore, when an architect needs a continuously available container endpoint, a long-running service provides the appropriate execution model.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Snowflake SnowPro Advanced Architect Exam Dumps and Practice Test Dumps. Question 261 What type of retrieval does Cortex Search combine? Batch and streaming retrieval Relational and transactional retrieval Local and remote retrieval Vector and keyword retrieval Correct Answer: 4 Explanation: Cortex Search uses a hybrid retrieval approach that combines vector search with keyword [&hellip;]<\/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\/16367"}],"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=16367"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16367\/revisions"}],"predecessor-version":[{"id":16383,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16367\/revisions\/16383"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=16367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=16367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=16367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}