10+ ArcelorMittal Nippon Steel Interview Questions and Answers

Guidelines for writing better code

• Follow coding standards and conventions

• Write modular and reusable code

• Use meaningful variable and function names

• Write comments to explain complex logic

• Test code thoroughly before deployment

Microservices are small, independent services that work together to form a larger application.

• Microservices allow for greater flexibility and scalability in software development.

• Each microservice can be developed, deployed, and scaled independently.

• Microservices communicate with each other through APIs.

• Examples of companies using microservices include Netflix, Amazon, and Uber.

Exceptions in Microservices are handled by logging, returning error codes, and using circuit breakers.

• Log exceptions with relevant details for debugging purposes

• Return appropriate error codes to the client

• Use circuit breakers to prevent cascading failures

• Implement retry mechanisms for transient errors

• Use fallback mechanisms to provide a degraded service when necessary

Microservices can be secured by implementing authentication, authorization, encryption, and monitoring.

• Implement authentication and authorization to ensure only authorized users can access the microservices.

• Use encryption to protect sensitive data in transit and at rest.

• Implement monitoring to detect and respond to security threats.

• Use secure communication protocols such as HTTPS and TLS.

• Implement rate limiting to prevent denial of service attacks.

• Use containerization and orc...read more

Yes, I have experience working with cloud technologies such as AWS and Azure.

• I have worked with AWS services such as EC2, S3, RDS, and Lambda.

• I have also worked with Azure services such as Virtual Machines, Blob Storage, and Functions.

• I am familiar with cloud deployment models such as Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).

Emergency change is a change that must be implemented immediately to prevent or resolve a major incident.

• Emergency changes are unplanned and urgent.

• They are made to prevent or resolve a major incident.

• Emergency changes bypass the normal change management process.

• They require approval from the emergency change advisory board (ECAB).

• Examples of emergency changes include security patches and critical bug fixes.

Known Error Database is a repository of all known errors and their solutions.

• It is used in IT Service Management to track and manage known errors

• It helps in reducing the impact of incidents by providing quick solutions

• It is a part of Problem Management process

• Examples of known errors include software bugs, hardware failures, and network issues

Different types of changes include emergency changes, standard changes, and normal changes.

• Emergency changes are unplanned and require immediate action, such as fixing a critical system issue.

• Standard changes are pre-approved and follow a defined process, such as deploying a software update.

• Normal changes are routine and do not require additional approval, such as adding a new user to a system.

Fishbone analysis is a problem-solving technique used to identify the root cause of a problem.

• Also known as Ishikawa diagram or cause-and-effect diagram

• Used to visually organize possible causes of a problem

• Helps to identify the root cause of a problem

• Categories include people, process, equipment, materials, environment, and management

• Example: If a company is experiencing low sales, the fishbone diagram can help identify possible causes such as poor marketing strategy, lack of...read more

Different types of S can refer to operating systems, programming languages, and data structures.

• Operating systems: Windows, macOS, Linux, Android, iOS

• Programming languages: Swift, Java, Python, C++

• Data structures: Stack, Queue, Linked List, Tree