Skip to content
PrepMint

Gemini

Gemini Basics

Core features and setup

2 questions
Easy· 1Medium· 1

Last reviewed

Recommended

Gemini Basics — Timed Test (2 questions)

TimedEasy2 questions · 2 min
Start test

No account needed. Answers and explanations arrive when you submit.

What this topic tests

The mix every Gemini Basics set is built to, and the questions published against it so far. Nothing here is hidden before you start.

Gemini Basics — target difficulty mix and published question count per level
LevelTarget sharePublished
Easy40%1
Medium40%1
Hard20%0
Total2

Gemini Basics — the theory

Gemini is Google's family of AI models and the associated consumer-facing chat assistant.

Core interaction. Like other AI chat assistants, Gemini offers a conversational interface where users can ask questions, request help with tasks, and have multi-turn conversations that maintain context.

Integration with Google's ecosystem. Gemini is integrated across various Google products and services, allowing it to be used within tools many people already use daily, beyond just a standalone chat interface.

Multimodal capabilities. Gemini models are generally designed to handle multiple types of input — text, images, and in some cases other media — allowing for tasks like asking questions about an uploaded image, not just plain text conversations.

Plans and access. Gemini is available through a free tier with certain limitations, alongside paid plans that typically offer higher usage limits and access to more capable models.

How conversational context behaves. Within a conversation, the assistant can refer back to what has already been said, so follow-up questions do not need to restate the whole problem — a considerable convenience that also has limits worth understanding. Context is finite, so very long conversations can lose track of details established much earlier, and a thread that has wandered across several unrelated topics tends to produce worse answers than a fresh one focused on the current question. Starting a new conversation when the subject genuinely changes is often the fastest fix for degrading responses.

Multimodal input in practice. The practical value of accepting images alongside text is that a large class of questions is far easier to show than to describe: a diagram to be explained, a screenshot of an error, a photograph of a handwritten page, a chart whose trend you want summarized. The quality of the result depends heavily on the quality of the input — a blurry or cropped image gives the model less to work with, exactly as an ambiguous text prompt does — and the same verification caution applies, since a confident description of an image can still be mistaken.

Access to current information. A model's training data has a cutoff, so questions about recent events fall outside what the model itself knows. Assistants address this by retrieving current information and using it to inform the answer, which is why an assistant can discuss things that postdate its training. When accuracy about anything recent matters, it is worth checking whether the answer is grounded in retrieved sources or is being produced from training data alone, since the two have very different reliability profiles.

Availability across products. Because Gemini is integrated into other Google products rather than existing only as a standalone assistant, the same underlying capability appears in different forms depending on where you meet it — assistance inside a document, a summary in a mail client, or answers in search. Each surface exposes a different subset of the capability, shaped by what makes sense in that context, so the assistant's abilities are not uniform everywhere it appears. Availability of particular integrations also varies by plan, region, and account type.

Limitations and verification. Like every current AI assistant, Gemini can produce fluent text containing incorrect facts, invented references, or flawed reasoning, and it presents those errors in the same confident register as correct answers. Arithmetic, dates, citations, quotations, and anything specialized are the categories most worth checking. The reasonable posture is to treat responses as a well-informed draft: useful for structure, orientation, and getting unstuck, but not authoritative on matters of fact without an independent check.

Privacy and data controls. Conversations with an AI assistant may be retained and, depending on the product and settings, used to improve the underlying service, with the specifics varying between consumer and enterprise offerings. Controls over history and data use are exposed in account settings. Anyone entering confidential, personal, or regulated information should understand those settings first, and organizations typically have policies governing what may be shared with an external assistant at all.

Assistant, model family, and API. The name Gemini refers both to the consumer assistant most people interact with and to the underlying family of models that developers can build on directly. These are related but distinct: the assistant is a product wrapping a model with an interface, retrieval, safety handling, and product integrations, while the models themselves are available through Google's developer platforms for building applications. Keeping the distinction clear avoids a common confusion, since a capability available in the assistant may be a product feature rather than a model capability, and behavior available through the API may not be exposed in the consumer interface at all.

Getting better results. The general prompting fundamentals apply directly here: state the task clearly, supply the context the model cannot infer, specify the format you want, break large requests into steps, and iterate rather than accepting the first draft. These habits transfer between assistants almost unchanged, which is why learning them once pays off across whichever tool you happen to be using.

Understanding these basics — what Gemini is, its integration with Google's broader ecosystem, and its multimodal design — provides the foundation for the more specific model-lineup topic that follows.

Sample questions

Three questions from this topic, with the answer and the reasoning shown.

Q1EasyWho develops Gemini?
  • GoogleCorrect
  • OpenAI
  • Anthropic
  • Meta

Explanation

Gemini is Google's model family, developed by Google DeepMind, the research unit behind AlphaFold and Veo. Keying that from the name is easy. The part worth carrying away is which Google surface a developer actually reaches for, because choosing wrong burns an afternoon.

Four surfaces share the name. The Gemini app is consumer chat. Google AI Studio is the browser workspace where a key gets issued and prompts get prototyped; it creates a Cloud project and key automatically for new users. The Gemini Developer API is what application code calls with that key. The enterprise path, now called the Gemini Enterprise Agent Platform and previously the Vertex AI generative path, takes a Cloud project and a region instead, with its own auth and billing. Google's own guidance sends most developers to the Developer API unless specific enterprise controls are required.

OpenAI, Anthropic and Meta each ship a separate family behind separate endpoints and separate credentials. A Gemini key authenticates against none of them, and no SDK setting bridges that. Changing vendor means changing the endpoint and the account under it.

Open this question on its own page

Q2MediumWhat does 'multimodal' mean in the context of Gemini?
  • It can handle multiple types of input, like text and imagesCorrect
  • It can only respond in multiple languages simultaneously
  • It requires multiple separate accounts to use
  • It can only process audio input

Explanation

Multimodal describes what the model accepts on the way in, and the consequence matters more than the definition. Images, audio, video, PDFs and other documents ride in the same request as the text prompt, as entries in one input list, not through some separate vision endpoint with its own key. Small payloads go inline as base64 or by URL; anything pushing the request past 100 MB goes through the Files API first, with a 50 MB ceiling on PDFs.

That is what makes captioning, classification and visual question answering possible without training a specialist model, and it is why a single call can hand over a scanned invoice, ask which line items were taxed, and get a written answer.

Multilingual is a different property: a text-only model can answer in twenty languages and still be single-modality, so option B confuses output language with input type. Accounts are unrelated — one key on one project covers every modality. And audio is one accepted input among several rather than the only one, which is where option D goes wrong.

Open this question on its own page

Practise all 2 questions

Every published question in Gemini Basics, with its answer and explanation.

More Gemini topics

All of Gemini