According to the PMBOK Guide, a Scrum project is an example of an adaptive or agile approach that is suitable for projects with high uncertainty, changing requirements, and fast delivery. A Scrum project delivers value incrementally through short iterations called sprints, where the team collaborates with the customer and other stakeholders to define and prioritize the product backlog, which contains the features and functionalities of the product. The team then selects a subset of the product backlog items to work on during each sprint, and delivers a potentially shippable product increment at the end of each sprint. The team also inspects and adapts the product and the process through frequent feedback loops and retrospectives. Therefore, a Scrum project suits the scenario of a new product launch with evolving requirements and flexible scope, as it allows the team to start the work based on the forecast of a similar project, but also to respond to changes and customer needs as they emerge. References:
* PMBOK Guide, Chapter 2, Section 2.4.2, Adaptive Life Cycle
* PMBOK Guide, Chapter 13, Section 13.2.2.1, Agile/Adaptive Environments
* PMBOK Guide, Appendix X3, Section X3.2, Agile Principles
* Agile Practice Guide, Chapter 2, Section 2.2.1, Scrum
* Agile Practice Guide, Chapter 3, Section 3.2, Delivering in an Agile Environment

The project manager should plan a communication method and allow the project team members to virtually interact. This will help to facilitate effective communication, information sharing, feedback, and coordination among the remote project team members. The project manager should also consider the cultural, linguistic, and time zone differences among the team members and use appropriate tools and techniques to overcome the challenges of virtual collaboration. Discussing the concerns with the project sponsor, modifying the project charter, creating a social media group platform, and setting the ground rules are all possible actions that the project manager can take, but they are not the best answer to the question, as they do not directly address the issue of collaboration between the remote project team members. References: = PMBOK Guide, 6th edition, pages 366-367, 378-379, 555-556; Agile Practice Guide, pages 28-29, 32-33; PMP Exam Content Outline,
2020, pages 6-7.

The project manager should first try to address the issue of team members not following the ground rules by scheduling a meeting with the project team to reinforce the ground rules. This is the most proactive and collaborative approach to resolve the problem and ensure team adherence to the ground rules. The project manager should also use this opportunity to listen to the team members' feedback and concerns, and make any necessary adjustments to the ground rules to suit the project context and team dynamics. This is consistent with the agile principles of self-organizing teams, frequent communication, and continuous improvement. The other options are not the best choices, as they involve escalating the issue to external parties, such as the project sponsor, human resources, or the functional manager, without first trying to resolve it within the team.
These options may also create a negative impact on the team morale, trust, and performance, and undermine the project manager's leadership and authority. References: (Professional in Business Analysis Reference Materials source and documents) A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition, Chapter 9:
Project Team Management, Section 9.2.2: Team Charter
Business Analysis for Practitioners: A Practice Guide, Chapter 5: Elicitation and Collaboration, Section 5.3.1:
Ground Rules
Agile Practice Guide, Chapter 2: An Introduction to Agile, Section 2.3: Agile Teams

In the event of a team member's sudden unavailability, the project manager should first log the situation in the issue log. This is a document where all the issues are recorded and tracked. It's used to document and monitor the status of all identified issues that can impact the project's schedule, cost, or scope. The issue log helps the project manager to analyze the issue, assess its impact, and plan the necessary actions to manage it.
While options A, B, and D might be part of the subsequent actions, the first step should be to log the issue.
Holding an emergency meeting (option A) might be necessary, but it should be done after recognizing and logging the issue. Asking the HR manager for an external replacement (option B) might be a potential solution, but it's not the immediate action. Updating the stakeholders (option D) is also important, but it should be done after the issue has been logged and a plan of action has been determined.
: Project Management Body of Knowledge (PMBOK) Guide, 6th Edition, Section 11.2: Identify Risks.

According to the PMBOK Guide, the project manager should include projected inflation rates in the budget estimate for a long-term project that will be executed over several years. This is because inflation rates affect the purchasing power of the project funds and the cost of resources over time. By including projected inflation rates, the project manager can account for the changes in the value of money and the cost of goods and services, and adjust the budget accordingly. This is part of the Estimate Costs process, which involves developing an approximation of the monetary resources needed to complete the project activities. References:
(Professional in Business Analysis Reference Materials source and documents) PMBOK Guide, 6th edition, Chapter 7, Section 7.2, Estimate Costs PMP Exam Prep, 10th edition, Rita Mulcahy, Page 223, Estimate Costs