20+ Interview Questions and Answers

Technical Lead interview questions on computer system validation, documentation, security policy, data integrity, GAMP5, risk assessment, backup and restoration, software categories, and more.

• Types of documentation for computer system validation

• Recent/current software execution and computer system validation

• Security policy for GxP computerization system

• Traceability matrix and its purpose

• ALCOA and ALCOA+ principles

• Definition and importance of data integrity

• Regulatory points fo...read more

I have created various objects in Kubernetes such as pods, services, deployments, config maps, secrets, etc.

• Pods - smallest deployable units in Kubernetes

• Services - provides a stable IP address and DNS name for a set of pods

• Deployments - manages the deployment and scaling of a set of pods

• Config Maps - stores configuration data as key-value pairs

• Secrets - stores sensitive information such as passwords and API keys

• Ingress - exposes HTTP and HTTPS routes from outside the cluster...read more

There is no limit to the number of EIPs that can be created for an AWS account.

• EIPs can be created and associated with instances in any region.

• However, there may be limits on the number of EIPs that can be used in a specific region.

• It is recommended to use Elastic Load Balancing or AWS Global Accelerator instead of EIPs for better scalability and availability.

Data sync replicates data across multiple databases while multi AZ provides high availability within a single region.

• Data sync is used for scaling read-heavy workloads and disaster recovery.

• Multi AZ is used for high availability and automatic failover within a single region.

• Data sync can be used across regions while multi AZ cannot.

• Data sync can be used with different database engines while multi AZ is specific to certain engines like RDS.

• Both can be used together for maximum...read more

Interfaces are used for multiple inheritance and loose coupling, while abstract classes are used for code reuse and common functionality.

• Use interfaces when you want to define a contract that multiple classes can implement.

• Use abstract classes when you want to provide a base implementation for derived classes.

• Interfaces promote loose coupling and allow for easy swapping of implementations.

• Abstract classes allow for code reuse and provide a common set of functionality.

• Interfac...read more

3-tier architecture separates presentation, logic, and data layers. ASP.NET page life cycle includes events from initialization to rendering.

• 3-tier architecture divides an application into presentation, logic, and data layers for better scalability and maintainability

• ASP.NET page life cycle includes events like Page_Init, Page_Load, and Page_PreRender for managing page state and rendering

• Example: Presentation layer can be a web form, logic layer can be a class library, and da...read more

The event loop is a programming construct that handles and dispatches events in a non-blocking manner.

• The event loop is responsible for handling and dispatching events in an application.

• It allows for non-blocking I/O operations by efficiently managing multiple events.

• The reactor pattern is a design pattern that uses an event loop to handle and dispatch events.

• The event loop has several phases: event registration, event polling, event handling, and event dispatching.

• During eve...read more

CTE stands for Common Table Expressions. It is a temporary result set that can be referenced within a SELECT, INSERT, UPDATE, or DELETE statement.

• CTE is defined using the WITH keyword in SQL.

• It helps in breaking down complex queries into simpler, more manageable parts.

• CTEs can reference themselves recursively, making them useful for hierarchical data.

• They are especially useful for avoiding code duplication and improving query readability.

• Example: WITH cte AS (SELECT * FROM ta...read more

Real-time scenarios for OOPS concepts include modeling a car as an object with properties and methods.

• Modeling a car as an object with properties like color, speed, and methods like accelerate, brake

• Inheritance can be seen in a vehicle hierarchy with classes like Car, Truck, Motorcycle

• Polymorphism can be demonstrated with a Drive method that behaves differently for each vehicle type

Use a common table expression (CTE) with ROW_NUMBER() function to delete duplicate records.

• Use a CTE to assign a row number to each record partitioned by the columns that define duplicates

• Delete records where the row number is greater than 1

• Example: WITH CTE AS (SELECT *, ROW_NUMBER() OVER (PARTITION BY column1, column2 ORDER BY column1) AS rn FROM table_name) DELETE FROM CTE WHERE rn > 1

I have learned various technologies in my previous organization.

• I have experience in working with Java, Python, and C++ programming languages.

• I have worked with various frameworks such as Spring, Hibernate, and Django.

• I have experience in working with databases like MySQL, Oracle, and MongoDB.

• I have worked with cloud platforms like AWS and Azure.

• I have experience in working with DevOps tools like Jenkins, Docker, and Kubernetes.

Design patterns are reusable solutions to common problems in software design.

• Design patterns provide proven solutions to recurring design problems.

• They help in creating flexible, maintainable, and scalable software.

• Design patterns can be categorized into three types: creational, structural, and behavioral.

• Examples of design patterns include Singleton, Factory Method, Observer, and Strategy.

Kubernetes services are a way to expose a set of pods as a network service.

• Services provide a stable IP address and DNS name for a set of pods.

• They can load balance traffic across the pods.

• There are different types of services, such as ClusterIP, NodePort, and LoadBalancer.

• Services can also be used to connect to external services or databases.

• Example: A web application running in Kubernetes can use a service to connect to a database running outside of Kubernetes.

The 7 OSI layers are a conceptual framework used to understand how network communication works.

• Physical Layer: Deals with physical connections and signals (e.g. cables, hubs)

• Data Link Layer: Manages data transfer between devices on the same network (e.g. Ethernet)

• Network Layer: Handles routing and forwarding of data packets (e.g. IP)

• Transport Layer: Provides end-to-end communication between devices (e.g. TCP)

• Session Layer: Manages sessions between applications (e.g. establish...read more

SOLID principles are a set of design principles that help in creating maintainable and scalable software.

• SOLID stands for Single Responsibility Principle, Open-Closed Principle, Liskov Substitution Principle, Interface Segregation Principle, and Dependency Inversion Principle.

• These principles guide developers to write code that is modular, flexible, and easy to understand and maintain.

• For example, the Single Responsibility Principle states that a class should have only one re...read more

SQL server architecture is a client-server model with a relational database management system.

• SQL server consists of a database engine, query processor, storage engine, and transaction manager.

• It uses a client-server model where clients send requests to the server for data manipulation.

• The relational database management system stores data in tables with relationships between them.

• SQL server supports multiple databases and can handle large amounts of data.

• It also includes secu...read more

Yes, I am willing to work 24*7 and open to relocation for the right opportunity.

• I am committed to my work and willing to put in the extra hours when needed.

• I understand that relocation may be necessary for career growth and am open to exploring new opportunities in different locations.

• I have successfully relocated for previous roles and have adapted well to new environments.

• I prioritize work-life balance and ensure that working 24*7 does not impact my overall well-being.

Handling a complex integration scenario involving multiple systems and dependencies

• Identify all systems involved and their dependencies

• Design a robust architecture to handle data flow between systems

• Implement error handling and fallback mechanisms

• Perform thorough testing to ensure all scenarios are covered

Terraform life cycle involves initialization, planning, applying, and destroying infrastructure.

• Terraform initializes by downloading providers and modules

• Planning phase creates an execution plan for infrastructure changes

• Apply phase executes the plan and makes changes to infrastructure

• Destroy phase removes all resources created by Terraform

• Terraform can also import existing infrastructure into its state

OSI layers refer to the seven layers of networking protocols that define how data is transmitted over a network.

• The seven OSI layers are: Physical, Data Link, Network, Transport, Session, Presentation, and Application.

• Each layer has its own specific functions and protocols that help in the transmission of data.

• Examples of protocols at different OSI layers include Ethernet at the Data Link layer, IP at the Network layer, TCP at the Transport layer, and HTTP at the Application ...read more

AG Availability Groups are a high-availability feature in SQL Server that provide failover clustering and database mirroring.

• AG Availability Groups allow for automatic failover of a group of databases between multiple SQL Server instances.

• They provide a way to distribute read-only workloads across multiple secondary replicas.

• AGs require Windows Server Failover Clustering (WSFC) and can be configured with synchronous or asynchronous data replication.

• They can also be used for d...read more

Solid principles are a set of design principles in object-oriented programming.

• S - Single Responsibility Principle

• O - Open/Closed Principle

• L - Liskov Substitution Principle

• I - Interface Segregation Principle

• D - Dependency Inversion Principle

• Examples: SOLID principles help in creating maintainable, scalable, and extensible code.

• They promote separation of concerns, modularity, and flexibility.

• They also help in reducing code smells and improving code quality.

Patching is the process of applying updates or fixes to software or systems to address vulnerabilities or improve functionality.

• Patching involves applying updates or fixes to software or systems.

• It is done to address vulnerabilities, security issues, or bugs.

• Patches can be released by software vendors or developers.

• Patching can be done manually or automatically.

• Examples of patching include installing operating system updates, applying security patches to web servers, or updat...read more

The project architecture refers to the overall structure and design of the software system.

• The project architecture defines how different components of the system interact with each other.

• It includes the high-level design decisions, such as the choice of programming languages, frameworks, and technologies.

• The architecture also outlines the communication protocols, data flow, and security measures.

• Examples of project architectures include monolithic, microservices, and serverl...read more

I am currently earning $100,000 per year.

• My current annual salary is $100,000.

• I am earning $8,333.33 per month.

• I receive a monthly salary of $8,333.33.

• My current compensation package is $100,000 per annum.

Key Performance Indicators (KPIs) of incident management measure the effectiveness of handling and resolving incidents.

• Average time to resolve incidents

• Percentage of incidents resolved within SLA

• Number of incidents per month/year

• Customer satisfaction ratings after incident resolution

• Incident recurrence rate