OSOpenStack Learning Academy
INTERVIEW PREPARATION

OpenStack Question & Answer Bank

All 50 questions from the supplied senior interview guide, grouped by module.

MODULE E · Q33–Q40

Identity, Interface & Orchestration

Q33. What is Keystone and what are its basic functions?
Keystone is OpenStack's Identity service. It authenticates users and identities, issues tokens, manages users, groups, projects, domains, roles and assignments, and provides the service catalog. A client receives a token scoped to project, domain or system context and presents it to other APIs. Keystone establishes identity and authorization context; individual services enforce policy.
Q34. What is the OpenStack Service Catalog?
The service catalog is information returned by Keystone identifying available services and API endpoints. Entries commonly include service type, region and endpoint interface such as public, internal or admin. Clients discover API URLs through the catalog rather than hard-coding them. The catalog is endpoint discovery information; it does not prove service health or authorize every operation.
Q35. Explain the difference between Authentication and Authorization in the context of Keystone.
Authentication answers 'Who are you?' Keystone validates credentials and issues a token. Authorization answers 'What may you do?' Role assignments and service policy determine permitted actions within project, domain or system scope. Successful login does not grant administrative access automatically. A user may authenticate successfully but receive an authorization error if token scope or role is insufficient.
Q36. What is Horizon?
Horizon is OpenStack's web dashboard. It provides a graphical interface for operations such as launching instances, managing networks, viewing images, creating volumes and managing identity resources, subject to permissions and enabled dashboards. Horizon communicates with OpenStack APIs using the user's context. It is a user interface, not the control plane itself.
Q37. What is OpenStack Heat?
Heat is OpenStack's orchestration service. It automates creation and management of infrastructure resources using declarative templates. Users describe desired resources and relationships; Heat coordinates API operations to create, update or delete a stack. It can manage instances, networks, ports and volumes when plugins are available. It supports repeatability, dependencies, parameters and outputs.
Q38. What is a Heat Orchestration Template (HOT) and what format does it use?
A HOT template declaratively describes resources, parameters, mappings, conditions, outputs and dependencies for a Heat stack. It uses YAML and a defined structure including `heat_template_version`. It describes desired infrastructure rather than imperative shell steps. Heat parses it and orchestrates service API calls. Supported versions and resource types depend on the Heat release and plugins.
Q39. What is Ceilometer and what is its main use case?
Ceilometer is an OpenStack telemetry data collection service. It gathers measurements and events about cloud resources through configured agents, notifications and polling. Data can support usage reporting, rating, monitoring or integration with other telemetry systems. Ceilometer is not itself a complete monitoring dashboard or billing product. Meters and architecture depend on release and configuration.
Q40. What is OpenStack Ironic and how does it plug into the compute layer?
Ironic is OpenStack's Bare Metal service. It provisions and manages physical servers rather than VMs. Hardware drivers and management interfaces such as IPMI or Redfish support inspection, power control, provisioning and cleaning. Ironic integrates with Nova so physical machines can be requested as compute resources. It suits workloads needing direct hardware access or specialized performance.