1Z0-1127-25 Flashcards — Free Oracle Cloud Infrastructure Generative AI Professional 1Z0-1127-25 Study Cards

"Provide the output in JSON format with keys: 'summary', 'findings', and 'recommendations'."

Specifying JSON output with clear keys ensures the model returns a structured, machine-parseable result. Natural language descriptions are ambiguous, and markdown may not be reliably parsed.

Temperature

Temperature scales logits before softmax; higher values increase randomness.

Use Retrieval-Augmented Generation (RAG) with the policy documents indexed in a vector store

RAG (Retrieval-Augmented Generation) allows the LLM to retrieve relevant document sections at inference time, so knowledge stays current without retraining. The other options either require expensive retraining for each update or lack document grounding.

Cohere Embed (e.g., embed-english-v3.0)

The Cohere Embed models are designed for text-to-vector embedding. The other options are for text generation or reranking.

To compute a weighted sum of all token representations based on pairwise relevance

Self-attention allows each token to attend to every other token in the sequence, capturing contextual relationships regardless of distance.

An encoder-only embedding model like Cohere Embed

An encoder-only embedding model like Cohere Embed is designed to convert text into dense vector representations (embeddings) that capture semantic meaning, which is exactly what is needed for semantic search over a large corpus of legal documents. These models use a bidirectional transformer architecture to encode context from both directions, producing fixed-size embeddings that can be efficiently compared using cosine similarity or other distance metrics.

Use Retrieval-Augmented Generation (RAG) with the policy documents indexed in a vector store

Retrieval-Augmented Generation (RAG) is the most appropriate approach because it allows the chatbot to answer questions by retrieving relevant chunks from the policy documents stored in a vector store at query time, without requiring model retraining. When documents are updated monthly, only the vector store needs to be re-indexed, while the underlying LLM remains unchanged, making it cost-effective and scalable.

RetrievalQA chain

RetrievalQA chain is designed to combine a retriever and an LLM to answer questions based on retrieved documents.

Fine-tune a small open-source LLM on domain-specific data

Fine-tuning a small open-source LLM on domain-specific data is the best approach because it adapts the model to understand industry-specific jargon while keeping the model small enough to maintain low latency. Unlike larger models, a fine-tuned small model can run efficiently on local hardware, reducing inference time and avoiding the overhead of external API calls or large model sizes.

The temperature is set too low; increase temperature during inference

The model's repetitive and dull responses indicate that the temperature parameter is too low, causing the model to always select the most probable tokens, leading to deterministic and monotonous outputs. Increasing temperature during inference introduces randomness into token sampling, allowing for more diverse and creative responses. This is a common issue in production LLMs where low temperature settings optimized for training metrics fail to produce engaging real-world outputs.

Configure system instructions to define acceptable behavior

Configuring system instructions is the most effective approach because it allows you to define the model's behavior and constraints at inference time without modifying the underlying model weights. In OCI Generative AI Service, system instructions act as a persistent prompt that guides the model's responses, enabling you to explicitly prohibit inappropriate content and enforce safety guidelines. This is a non-invasive, immediate mitigation that does not require the time, cost, or data preparation associated with retraining or fine-tuning.

/chat

The /chat endpoint in OCI Generative AI Service is designed for conversational interactions and can handle long document summarization by accepting the document content as part of the chat context. This endpoint supports multi-turn dialogues and large input payloads, making it suitable for processing and summarizing lengthy documents.

Adjust the chunk size and chunk overlap to better capture coherent passages.

Adjusting chunk size and overlap helps create coherent chunks that align with query intent, improving retrieval relevance. Option A is wrong because the embedding model type (dense vs. sparse) affects retrieval method but does not directly fix chunk coherence issues. Option C is wrong because increasing chunk size may introduce noise and irrelevant context. Option D is wrong because reducing the number of retrieved chunks (k) only limits results, not improves relevance of individual chunks.

Create an ANN index on the embedding vector column.

Approximate Nearest Neighbor (ANN) indexes are specifically designed for high-dimensional vector spaces, enabling efficient similarity search on embedding vectors. In Oracle Autonomous Database, ANN indexes (e.g., using IVF or HNSW algorithms) drastically reduce search latency compared to brute-force scans, which is critical for real-time RAG chatbot responses.

Service Gateway

A Service Gateway enables private subnet resources to access OCI services (including the OCI Data Science model deployment endpoint) without traversing the internet. Since the inference endpoint must be accessible only from a private subnet within the same VCN, the Service Gateway provides the necessary private connectivity by routing traffic over the OCI network fabric, not through a NAT or internet gateway.

The batch size is too large for the GPU memory

The most likely cause is that the batch size is too large for the GPU memory. Even though the GPU instance has sufficient total memory, a batch size that exceeds the available GPU memory (after accounting for model parameters, gradients, and optimizer states) will trigger an out-of-memory (OOM) error. Reducing the batch size allows the model to fit within the GPU's memory limits, which explains why the job works on a smaller dataset but fails on a larger one.