Find Interview Questions for MANET

Right Answer:
Yes, you should write different test cases for each user profile to ensure that all rights and functionalities are tested according to the specific permissions and roles of each profile.

Right Answer:
The Scrum Master is a servant-leader who helps the Scrum Team follow the Scrum framework. They facilitate Scrum events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), remove impediments, protect the team from distractions, and coach the team on Agile principles and practices.

Right Answer:
Kanban focuses on visualizing workflow, limiting work in progress (WIP), and continuous flow. Scrum uses time-boxed iterations (sprints) with specific roles (Scrum Master, Product Owner, Development Team) and events (sprint planning, daily scrum, sprint review, sprint retrospective).

Use Kanban when you need continuous delivery, have evolving priorities, and want to improve workflow incrementally. Use Scrum when you need structured development with fixed-length iterations, have clear goals for each iteration, and benefit from team collaboration with defined roles.

Right Answer:
The Agile Manifesto values:

* **Individuals and interactions** over processes and tools.
* **Working software** over comprehensive documentation.
* **Customer collaboration** over contract negotiation.
* **Responding to change** over following a plan.

That is, while the items on the right have value, we value the items on the left more.

Right Answer:
A product backlog is a prioritized list of features, bug fixes, tasks, and requirements needed to build a product. It's managed through regular refinement, prioritization, estimation, and updates based on feedback and changing business needs, often facilitated by the Product Owner.

Right Answer:
Scrum is an Agile framework for managing and completing complex projects.

Implementation involves:

1. **Roles:** Defining roles like Product Owner, Scrum Master, and Development Team.
2. **Sprints:** Working in short, time-boxed iterations (Sprints), typically 2-4 weeks.
3. **Artifacts:** Using artifacts like Product Backlog, Sprint Backlog, and Increment.
4. **Events:** Conducting events such as Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
5. **Continuous Improvement:** Regularly inspecting and adapting the process based on feedback.

Right Answer:
I find it most difficult to work with people who are resistant to feedback and unwilling to collaborate. This can hinder progress and create misunderstandings in the team.

Right Answer:
QA (Quality Assurance) focuses on preventing defects by ensuring processes are followed and standards are met, while QC (Quality Control) involves identifying defects in the final product through testing and inspection.

Right Answer:
RESTful principles include:

1. **Statelessness**: Each API call must contain all the information needed to understand and process the request, with no stored context on the server.
2. **Client-Server Architecture**: The client and server are separate, allowing for independent development and scalability.
3. **Uniform Interface**: A consistent way to interact with resources, typically using standard HTTP methods (GET, POST, PUT, DELETE).
4. **Resource-Based**: APIs should expose resources (data entities) through URIs, and clients interact with these resources.
5. **Representation**: Resources can be represented in various formats (like JSON or XML), and clients can request the format they prefer.
6. **Cacheability**: Responses should indicate whether they can be cached to improve performance and reduce server load.

These principles guide the design of APIs to be scalable, efficient, and easy to use.

Right Answer:
API authentication is the process of verifying the identity of a user or application trying to access an API. Common methods include:

1. **API Keys**: Unique keys provided to users to access the API.
2. **Basic Authentication**: Uses a username and password encoded in Base64.
3. **OAuth**: A token-based authentication method that allows users to grant limited access to their resources without sharing credentials.
4. **JWT (JSON Web Tokens)**: A compact, URL-safe means of representing claims to be transferred between two parties, often used for stateless authentication.
5. **HMAC (Hash-based Message Authentication Code)**: Uses a secret key to create a hash of the request, ensuring data integrity and authenticity.

Right Answer:
Rate limiting in APIs is a technique used to control the number of requests a user can make to an API within a specific time period. It is implemented by setting thresholds (e.g., requests per minute) and using mechanisms like tokens, counters, or IP address tracking to monitor and restrict access when the limit is exceeded.

Right Answer:
An API endpoint is a specific URL or URI where an API can be accessed by a client to perform operations like retrieving or sending data. It defines the location and method (such as GET, POST) for interacting with the API.

Right Answer:
API documentation is a technical manual that explains how to use an API, including its endpoints, request and response formats, authentication methods, and examples. It is necessary because it helps developers understand how to integrate and interact with the API effectively, ensuring proper usage and reducing errors.