To achieve resource-level visibility in cloud billing, the engineer should configure tagging. In CompTIA Cloud+ (CV0-004) objectives for cost management, chargeback/showback, and governance, tags (labels
/metadata) are used to categorize and track cloud resources by attributes such as department, project, application, environment (dev/test/prod), owner, or cost center. Once consistently applied, tags enable detailed billing reports that break down spending per resource and per business unit, supporting accurate budgeting, accountability, and optimization decisions. Many cloud providers also allow "cost allocation tags" or similar features that integrate directly into billing dashboards and exports, making it easier to identify which workloads drive cost.
Rightsizing (A) is an optimization activity to reduce waste by selecting appropriate instance sizes, but it does not provide reporting granularity by itself. Invoicing (B) relates to billing documents, not categorization.
Reserved instances (C) reduce compute costs through commitment discounts but do not inherently improve visibility into which teams or resources consume spend. Therefore, tagging is the correct configuration for resource-level billing visibility.

Check the Explanation for the complete Solution.
Explanation:
The issue is with Web app 1 (Finance application).
From the WAF logs, we can see that requests to https://webapp1.comptia.org/FIN/login.html are being blocked (Rule ID 1006). The rule is configured to block access to the finance application's login page. This corresponds to the reported issue of the web-based login prompt not loading.
To remediate the issue, the WAF configuration for Rule ID 1006 should be changed from "Block" to "Allow".
This will enable the web-based login prompt to load for the client.
Additionally, the client app configuration indicates that the client laptop (IP 192.168.10.142) is trying to access the service, and the WAF logs show that requests from this IP are being blocked due to the current rule set. Changing the action for Rule ID 1006 will also ensure that legitimate attempts to access the login page from this IP are not blocked.
Steps for remediation:
Go to the WAF configuration.
Find Rule ID 1006 for the Finance application 1.
Change the action from "Block" to "Allow".
Save the changes.
Web application firewall (WAF) configurations typically include rules that define which traffic should be allowed or blocked. Blocking legitimate traffic to login pages can prevent users from accessing the application, which seems to be the case here.
Client application configurations and WAF logs provide valuable insights into the source of the traffic and the rules that are affecting it. It's important to ensure that the rules align with the intended access policies for the application.

A container image is used to deliver code quickly and efficiently across the development, test, and production environments. Container images are lightweight, standalone, executable software packages that include everything needed to run a piece of software, including the code, runtime, system tools, libraries, and settings.
References: CompTIA Cloud+ Study Guide (Exam CV0-004) - Chapter on Cloud Deployment Methods

If users are unable to access an application that uses TLS 1.1 but can access other internet applications, it is likely that changes were made on the web server to address vulnerabilities, such as disabling outdated and less secure protocols like TLS 1.1. References: CompTIA Cloud+ Study Guide (Exam CV0-004) - Chapter on Cloud Security

When an organization can predict demand spikes (such as seasonal sales), the most cost-effective approach is to use scheduled scaling-a scaling configuration tied to a known timeline. In the CompTIA Cloud+ (CV0-
004) objectives covering elasticity, scaling strategies, and cost optimization, scheduled scaling allows the business to increase capacity shortly before the surge begins and reduce it immediately after the event ends.
This minimizes cost by ensuring resources run only for the required window, while still maintaining performance and availability during peak traffic.
Option A (least-connections) improves how traffic is distributed but does not add capacity; it cannot prevent resource exhaustion if the backend pool is undersized. Option C (reconfiguring to have more resources- vertical scaling) can help performance but often increases cost continuously and may introduce downtime or scaling limits. Option D (deploying additional compute in advance) can meet the requirement, but it may waste money if instances remain overprovisioned longer than necessary. Therefore, enabling a scheduled scaling configuration for the identified timeline best meets the need at minimal cost.