Find Interview Questions for Mobigesture

Right Answer:
* **Epic:** A large, high-level user story that is too big to complete in a single iteration. It's usually broken down into smaller user stories.
* **User Story:** A small, self-contained requirement that represents a valuable piece of functionality for the end-user. It follows the format: "As a [user type], I want [goal] so that [benefit]".
* **Task:** A small, actionable item that needs to be done to complete a user story. It's a technical breakdown of the work required by the development team.

Right Answer:
I would assess the organization's context, choose a suitable scaling framework like SAFe or LeSS based on needs, implement it incrementally with training and coaching, focusing on value delivery, and continuously inspect and adapt the implementation based on feedback and results.

Right Answer:
"In one project, we underestimated the complexity of integrating a new third-party API. This caused us to miss our sprint goal. To address this, we immediately re-estimated the remaining work, broke down the integration into smaller, more manageable tasks, and increased communication with the API vendor. We also temporarily shifted team focus to prioritize the integration, delaying a lower-priority feature for the next sprint. Finally, in the sprint retrospective, we implemented a better vetting process for third-party integrations to avoid similar issues in the future."

Right Answer:
During a sprint, I generally avoid scope creep. If a change request is small and doesn't impact the sprint goal, the team can discuss and decide if it can be included. If the change is significant, it goes into the product backlog to be prioritized for a future sprint.

Right Answer:
To facilitate effective sprint retrospectives, I would:

1. **Set the Stage:** Create a safe and open environment where the team feels comfortable sharing.
2. **Gather Data:** Collect information about what went well, what didn't, and any challenges faced during the sprint.
3. **Generate Insights:** Facilitate a discussion to identify root causes and patterns.
4. **Decide on Actions:** Collaborate to define specific, actionable, measurable, achievable, relevant, and time-bound (SMART) improvements.
5. **Close the Retrospective:** Summarize action items and assign owners.
6. **Follow Up:** Track progress on action items in subsequent sprints to ensure continuous improvement.

Right Answer:
API testing is the process of verifying that an application programming interface (API) functions as expected, ensuring it meets the requirements for functionality, reliability, performance, and security. Tools that can be used for API testing include Postman, SoapUI, JMeter, RestAssured, and Swagger.

Right Answer:
An API Gateway acts as a single entry point for clients to access multiple microservices, handling requests, routing them to the appropriate services, managing authentication, rate limiting, and aggregating responses.

Right Answer:
CORS, or Cross-Origin Resource Sharing, is a security feature implemented by web browsers that allows or restricts web applications from making requests to a domain different from the one that served the web page. It affects API development by requiring developers to configure their APIs to specify which origins are allowed to access their resources, ensuring that only trusted domains can interact with the API.

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:
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:
1. Remove duplicates
2. Handle missing values
3. Correct inconsistencies
4. Standardize formats
5. Filter out irrelevant data
6. Validate data accuracy
7. Normalize data if necessary

Right Answer:
Classification analysis is a data analysis technique used to categorize data into predefined classes or groups. It works by using algorithms to learn from a training dataset, where the outcomes are known, and then applying this learned model to classify new, unseen data based on its features. Common algorithms include decision trees, logistic regression, and support vector machines.

Right Answer:
The purpose of feature engineering in data analysis is to create, modify, or select variables (features) that improve the performance of machine learning models by making the data more relevant and informative for the analysis.

Right Answer:
Correlation is a statistical measure that indicates the extent to which two variables fluctuate together, while causation implies that one variable directly affects or causes a change in another variable.

Right Answer:
Outliers are data points that significantly differ from the rest of the dataset. They can skew results and affect statistical analyses. To handle outliers, you can:

1. Identify them using methods like the IQR (Interquartile Range) or Z-scores.
2. Remove them if they are errors or irrelevant.
3. Transform them using techniques like log transformation.
4. Use robust statistical methods that are less affected by outliers.
5. Analyze them separately if they provide valuable insights.