Wings1 Process exam Preparation MCQ Part

Welcome to Part 2 of the Process Question Bank, along with their answers and explanations. Continue testing your knowledge!

Wings1 Process exam Preparation MCQ Part - 2

Page - 1️⃣2️⃣3️⃣4️⃣5️⃣

1. Major incident review takes place after a major incident has occurred. The contents of the review document should mandatorily Include

Timelines for incident resolution
Document who is going to own the problem and root cause.
Understand what went wrong during major incidents to ensure they will not repeat in future.
All of the Above ✔

Correct Answer: D

Explanation: The contents of a major incident review document should mandatorily include all of the options mentioned: A. Timelines for incident resolution: The major incident review document should include a detailed timeline of the incident, documenting when it occurred, when it was detected, and the duration of the incident. This helps provide an understanding of the incident's impact and the time taken to resolve it. B. Document who is going to own the problem and root cause: It is important to identify the individual or team responsible for owning the problem and investigating the root cause of the incident. This information should be documented in the review document to ensure accountability and facilitate further analysis. C. Understand what went wrong during major incidents to ensure they will not repeat in the future: The major incident review aims to identify and understand the causes and contributing factors that led to the incident. This includes analyzing the events, actions, and decisions that occurred during the incident response. The review document should document these findings to learn from the incident and implement preventive measures to avoid similar incidents in the future.

2. Sprint longer than one calendar month may result in

Too much to inspect in short meetings.
Detached Stakeholders.
Increased complexity needing more traditional controls like documentation
All of the Above ✔

Correct Answer: D

Explanation: Sprints longer than one calendar month can result in the issues mentioned in options A, B, and C: A. Too much to inspect in short meetings: Scrum emphasizes frequent inspection and adaptation. Longer sprints can lead to a larger amount of work to inspect and review within the limited time frame of the sprint review and retrospective meetings. This can make it challenging for the Scrum team to effectively assess progress, identify issues, and make necessary adjustments. B. Detached Stakeholders: With longer sprints, stakeholders may feel disconnected or less engaged in the development process. Their feedback and input may become less timely and less aligned with the evolving product. This can hinder collaboration, communication, and the ability to meet stakeholders' evolving needs. C. Increased complexity needing more traditional controls like documentation: Longer sprints may introduce more complexity into the development process, requiring additional documentation and traditional controls to manage and track the progress of the work. This can potentially increase overhead, bureaucratic processes, and a reliance on heavyweight documentation, which goes against the Agile principles of simplicity and working software over comprehensive documentation.

3. It has been decided that the architecture for a project will have 3 layers i.e.
a. Front End UI,
b. Middleware: which will host the business logic
c. Database Component for the storage.
Which of the following team structure would you recommend for a better business outcomes?

Three teams, one for each of the layers with clear protocols and interfaces between them to improve business oriented collaboration.
Six teams, one development and one testing for each of the layers. A central integration team to continuously integrate the work.
Feature based teams, where each team is staffed with all the skills needed to develop the features. ✔
As long as the architecture is robust, team structuring does not matter.

Correct Answer: C

Explanation: For better business outcomes, the recommended team structure would be C. Feature-based teams, where each team is staffed with all the skills needed to develop the features. By organizing teams based on features, the teams are composed of cross-functional members with diverse skills required to develop end-to-end features. This enables greater ownership, autonomy, and collaboration within the teams. Each team can work independently, focusing on delivering specific features or functionalities, which leads to faster development cycles and better alignment with business objectives. Option A suggests having separate teams for each layer, which can lead to increased dependencies, coordination efforts, and potential delays. While clear protocols and interfaces between teams can improve collaboration, the overall efficiency and speed of development might be impacted. Option B suggests having separate development and testing teams for each layer, along with a central integration team. This approach can introduce additional handoffs, communication overhead, and potential bottlenecks during the integration process. Option D suggests that team structuring does not matter as long as the architecture is robust. While a robust architecture is important, the team structure plays a significant role in enabling effective collaboration, efficiency, and agility in software development.

4. An organization needs to structure hundred's of developers into scrum teams. You as s scrum master will

Work with organization management and prepare the best structure for each scrum team based on the seniority and skills of developers. ✔
Identify required number of scrum masters and require them to choose their scrum teams.
Facilitate awareness of developers about the goals and objectives of product development, coach them about scrum and let them work among themselves to scrum teams.

Correct Answer: A

Explanation: Option A suggests collaborating with management to assess the seniority and skills of the developers and then structuring the teams accordingly. This approach ensures that the teams are balanced in terms of expertise, experience, and skill sets, which can contribute to better team dynamics and productivity. Option B suggests identifying the required number of Scrum Masters and having them choose their Scrum teams. While involving Scrum Masters in team formation can be beneficial, it's essential to consider a more comprehensive approach that takes into account the skills and seniority of the developers. Option C suggests facilitating awareness among the developers about the goals and objectives of product development and coaching them about Scrum, allowing them to form teams among themselves. While self-organization is a key aspect of Scrum, it's important to consider the skills and seniority of the developers to ensure balanced and effective teams.

5. Scrum master with respect to scrum artifacts is

Coach the team to increase the transparency of the artifacts ✔
Decide the format of the artifacts and ensures that the team follows it.
Owner of the artifacts and responsible for having them up to date.

Correct Answer: A

Explanation: The Scrum Master's role with respect to Scrum artifacts is to coach the team to increase the transparency of the artifacts. Scrum artifacts include the product backlog, sprint backlog, and potentially the increment. The Scrum Master's primary responsibility is to ensure that these artifacts are understood, visible, and accessible to the Scrum Team and stakeholders. The Scrum Master facilitates transparency by coaching the team on how to create and maintain the artifacts effectively. The Scrum Master does not decide the format of the artifacts (option B). The format and structure of the artifacts are typically determined by the Scrum Team collectively, with input from stakeholders and alignment with Agile and Scrum principles. Additionally, the Scrum Master is not the owner of the artifacts (option C). The artifacts are owned by the Scrum Team as a whole. The Scrum Master helps facilitate their proper usage, updates, and maintenance but is not solely responsible for them.

6. Select all that apply. The sprint review is an event that requires

The Product owner's sign off.
Active participation of the stakeholders invited by product owner. ✔
Transition Sign-off.
Inspection and Adaption activities. ✔

Correct Answer: B, D

Explanation: During the sprint review, active participation of the stakeholders invited by the product owner is crucial. The purpose of the sprint review is to inspect the increment and gather feedback from stakeholders to ensure the product is meeting their expectations. Inspection and adaptation activities are also integral to the sprint review. The Scrum Team and stakeholders review the increment, discuss any changes made during the sprint, and identify opportunities for improvement. This allows the team to adapt their approach in subsequent sprints based on the feedback received. Option A, the Product Owner's sign-off, is not explicitly required during the sprint review. The Product Owner's input and involvement are essential, but their sign-off typically happens in other events, such as the sprint planning or the sprint review. Option C, transition sign-off, is not directly related to the sprint review. Transition sign-off typically happens when the product is ready to be released or deployed to the production environment, and it involves different processes and activities. Therefore, the sprint review requires the active participation of stakeholders invited by the product owner and includes inspection and adaptation activities.

7. This DevOps tool is used to build the code, test it and deploy in staging/production

Jenkins ✔
Docker
Nagios
Collectd/collectl.

Correct Answer: A

Explanation: Jenkins is a popular DevOps tool used for continuous integration and continuous delivery (CI/CD) pipelines. It is commonly used to automate the build, test, and deployment processes of code in staging and production environments. Jenkins allows developers to configure and automate the entire software development lifecycle, including building the code, running tests, and deploying the application to different environments. It integrates with various version control systems, testing frameworks, and deployment tools, making it a versatile tool for software development and deployment. Option B, Docker, is a containerization platform that enables developers to package applications and their dependencies into portable containers. While Docker is commonly used alongside Jenkins for deploying applications, Docker itself is not primarily focused on building and testing code. Options C and D, Nagios and Collectd/collectl, are monitoring and performance analysis tools, respectively. They are not specifically designed for building, testing, and deploying code. Therefore, the correct tool for building the code, testing it, and deploying it in staging/production is Jenkins (option A).

8. Practice involved analysis of patterns of potential issues, assessment of flow volume, and resolution time taken to improve operation efficiency is

Data Fix
Change Management
Ticket Analysis ✔
Problem Control

Correct Answer: C

Explanation: The practice described, involving the analysis of patterns of potential issues, assessment of flow volume, and resolution time taken to improve operational efficiency, is typically associated with Ticket Analysis. Ticket Analysis refers to the process of analyzing data and information from tickets or incidents raised in an IT service management system. It involves studying patterns, trends, and metrics related to ticket volumes, issue types, resolution times, and other relevant factors. By conducting Ticket Analysis, organizations can identify recurring issues, bottlenecks, or areas for improvement in their IT operations. This analysis helps in making data-driven decisions to optimize processes, allocate resources effectively, and improve overall operational efficiency. Options A and D, Data Fix and Problem Control, are not directly related to the described practice. Data Fix usually refers to correcting or manipulating data in a system or database, while Problem Control refers to the process of managing and resolving problems within an IT service environment. Option B, Change Management, is also not directly related to the described practice. Change Management focuses on managing and controlling changes to IT services, systems, or infrastructure to minimize disruptions and ensure the stability and reliability of the environment. Therefore, the practice involved in the analysis of patterns of potential issues, assessment of flow volume, and resolution time taken to improve operational efficiency is best represented by Ticket Analysis (option C).

9. In which of the following scenario's RCA must be performed?

Recurring issues with low priority
Upon Client request for incidents with defined criteria.
Major Incidents causing business impact
All of the options ✔

Correct Answer: D

Explanation: Root Cause Analysis (RCA) should be performed in all of the scenarios mentioned: A. Recurring issues with low priority: RCA helps identify the underlying causes of recurring issues, even if they have a low priority. By addressing the root causes, organizations can prevent the issues from happening again in the future. B. Upon client request for incidents with defined criteria: When a client specifically requests an RCA for certain incidents, it is important to perform the analysis to determine the root causes and provide insights into preventing similar incidents in the future. C. Major incidents causing business impact: RCA is especially important for major incidents that have a significant impact on the business. By conducting an in-depth analysis of the root causes, organizations can take corrective actions to prevent such incidents from occurring again and minimize their impact on business operations. Performing RCA helps organizations understand the underlying causes of issues, improve their processes, and prevent recurrence. It is a valuable practice for continuous improvement and ensuring the stability and reliability of systems and services.

10. A company composes a project team of analysis ,developers testers and architects. The company wants the team ro adapt scrum. To do so, they must take a cultural change. What is most likely the hardest change for this team?

Adapt a set of metrics to measure progress.
Eliminate the focus on comprehensive documentation.
Eliminate the throw-it-over-the-wall mentality. ✔
Adopt a focus on delivering working software

Correct Answer: C

Explanation: the hardest change for this team, when transitioning to Scrum, is likely to be eliminating the throw-it-over-the-wall mentality. The throw-it-over-the-wall mentality refers to the traditional approach where each role in the project team works in isolation, completing their tasks and passing them on to the next role without much collaboration or communication. In Scrum, collaboration, communication, and cross-functional teamwork are essential. The team works together closely throughout the sprint to deliver a potentially shippable product increment. There is a shared responsibility for the success of the project, and all team members contribute their expertise and work collaboratively towards the project's goals. Eliminating the throw-it-over-the-wall mentality requires a cultural shift in how the team members perceive their roles and responsibilities. They need to embrace the idea of collective ownership and collaboration, where the focus is on working together as a team rather than passing work from one individual to another without much interaction. While the other options, such as adapting metrics, eliminating comprehensive documentation, and focusing on delivering working software, are also changes associated with adopting Scrum, they are typically easier to address compared to changing deeply ingrained habits and mindset related to collaboration and teamwork.

11. Tools or frameworks that facilitates source code to be automatically complied into releasable binaries is known as

Build Automation ✔
Business Intelligence
Environment Fix
Monitoring

Correct Answer: A

Explanation: Build Automation is a practice that involves using tools or frameworks to automatically compile source code into releasable binaries or executable software. It is an essential part of the software development process, particularly in agile and DevOps environments. Build Automation tools streamline the build process by automating tasks such as compiling source code, managing dependencies, running tests, and packaging the software into deployable artifacts. These tools help ensure consistency, efficiency, and reliability in the software build process. By automating the build process, development teams can save time, reduce human errors, and improve the overall quality of the software. It allows for faster and more frequent builds, enabling continuous integration and delivery practices.

12. In a RACI matrix used for Stakeholder management , R stands for

Required.
Respectable
Responsible ✔
Requested

Correct Answer: C

Explanation: In a RACI matrix used for stakeholder management, the letter "R" stands for "Responsible." The RACI matrix is a tool used to define and clarify roles and responsibilities within a project or organization. It helps identify who is accountable, who should be consulted, who needs to be informed, and who is responsible for specific tasks, decisions, or activities. The key roles in a RACI matrix are: Responsible (R): The person or role responsible for executing or completing a task or activity. They are directly responsible for the successful completion of the task. Accountable (A): The person or role who is ultimately accountable for the overall outcome or result. They have the authority to make decisions and are answerable for the success or failure of the task. Consulted (C): Individuals or roles who provide input, expertise, or guidance related to the task. They are consulted for their opinions or advice before a decision or action is taken. Informed (I): Individuals or roles who need to be kept informed about the progress, decisions, or outcomes of a task. They are not directly involved in the execution but should be kept up to date. In this context, "Responsible" (option C) refers to the person or role who is directly responsible for executing or completing a specific task or activity. They are the ones who take ownership and ensure that the task is carried out effectively.

13. The following data points can be considered for evaluating Risk of changes

Number of Components undergoing changes
Existence of Implementers
Existence of templates.
Change implementation duration

Correct Answer: A, B, C, D ✔

Explanation: A. Number of Components undergoing changes: The more components or systems involved in a change, the higher the risk, as there are more potential points of failure or impact. B. Existence of Implementers: Having experienced and knowledgeable implementers who understand the system and the change being made can reduce the risk associated with the change. C. Existence of templates: Templates can provide a standardized approach to change management, ensuring that proper steps and considerations are followed, reducing the risk of overlooking important factors. D. Change implementation duration: Longer implementation durations can increase the risk of potential disruptions, conflicts with other changes, or extended periods of system unavailability, which may impact business operations. These data points can help assess the risk associated with changes and guide decision-making in change management processes. It is important to consider additional factors specific to the organization and the nature of the changes being made to comprehensively evaluate risk.

14. Which metric should be focused more for standardization of changes and deployment automation?

Outage Duration (Outage End Time – Outage Start Time)
Deployment Duration (Planned End Time -Planned Start Time)
Change Risk Impact and categorization
Change Cycle Time ( Change Closure Time – Change Open Time) ✔

Correct Answer: D

Explanation: Change Cycle Time measures the time it takes for a change to go from the open state to the closed state. By focusing on reducing the Change Cycle Time, organizations can improve the efficiency and speed of their change management and deployment processes. Shorter Change Cycle Time indicates faster and more streamlined change implementation, reducing the time required for testing, approval, and deployment. While metrics like Outage Duration and Deployment Duration are important to track and analyze, they may not directly address the standardization of changes and deployment automation. Change Risk Impact and categorization, on the other hand, focus more on evaluating the impact and severity of changes, which is a different aspect compared to standardization and automation.

15. Which of the Following is not a type of Change?

Emergency Change
Normal Change
Quick Change ✔
Standard Change

Correct Answer: C

Explanation: "Quick Change" is not a recognized type of change in the commonly used change management frameworks like ITIL (Information Technology Infrastructure Library) or Agile/Scrum. The three commonly recognized types of changes are: A. Emergency Change: This type of change is unplanned and requires immediate implementation to resolve critical issues or incidents that are impacting the business or services. B. Normal Change: Also known as "Standard Change," this type of change follows the defined change management process and requires assessment, planning, and approval before implementation. D. Standard Change: This type of change refers to pre-authorized changes that are considered routine and low risk. They are repetitive in nature, have well-defined procedures, and are pre-approved to expedite the change process. "Quick Change" is not a standard type of change recognized in these frameworks, and its definition may vary depending on the specific context or organization.

16. New Catalogue item has to be added to the existing list of services where TCS is managing the end to end IT Services for the customer IT Organizations. Who Should Authorize the creation of the service catalogue?

Service Catalogue Owner.
TCS, as there is new type of skill for TCS
Both customer and TCS ✔
Customer , if there is a financial impact of provisioning services

Correct Answer: C

Explanation: The creation of a new service catalog item involves both the customer and the service provider (in this case, TCS) working together to define and authorize the addition. The customer, as the owner of the IT organization, has the authority to determine the services they require and the financial impact of provisioning those services. TCS, as the service provider, needs to collaborate with the customer to understand their needs and align the new service catalog item with the overall IT service management strategy. Therefore, the authorization for creating a new service catalog item should come from both the customer and TCS, ensuring mutual agreement and alignment of goals and requirements.

17. The Developers create the sprint goal. What is the role of Product owner in creating the Sprint goal?

The Product Owner First describes the business objective of the sprint to the developers, Based on this, and the selected items for the sprint , the sprint goal is crafted. ✔
The Product Owner is not concerned with the sprint goal as it an optional activity for the developers.
The Product Owner is responsible for getting the stakeholders formal approval for the sprint goal.
The Product Owner can change the sprint goal anytime during the Sprint. He/She can create a new sprint goal and ask the developers to work on it.

Correct Answer: A

Explanation: The Product Owner plays a crucial role in creating the sprint goal. The Product Owner is responsible for communicating the business objective or the desired outcome of the sprint to the development team. This objective serves as the foundation for the sprint goal. The development team then collaborates with the Product Owner to determine the specific work items or backlog items that will contribute to achieving the sprint goal. The sprint goal provides focus and direction to the development team during the sprint and helps them prioritize their work. It aligns the team's efforts with the overall business objectives and ensures that the sprint delivers value to the stakeholders.

18. Escalation Matrix Should contain the details of the following stakeholders

Both TCS and Customers Stakeholders. ✔
TCS Stakeholders only
No Stakeholder details are required to be documented as you have all the stakeholders personally.
Customer Stakeholders only

Correct Answer: A

Explanation: An escalation matrix is a document or process that outlines the chain of communication and escalation in case of issues or problems within a project or organization. It includes the details of stakeholders who should be contacted or notified at various levels of escalation. In order to effectively manage and address issues, it is important to have the contact information and roles of both TCS (the service provider) and customer stakeholders included in the escalation matrix. This ensures that the appropriate individuals from both sides are informed and involved in the escalation process, allowing for timely resolution and effective communication.

Back to Questions & Answers (Page1) | Continue to Questions & Answers (Page3)

Wings1 Process exam Preparation MCQ Part - 2