FINOPS-CERTIFIED-PRACTITIONER practice question 29 of 35

You are a FinOps Certified Practitioner (FOCP) working for a financial services company that operates globally. The company wants to optimize costs while ensuring compliance with data residency regulations. Which cloud billing and pricing model would you recommend for this scenario?

Full set: 300 questions
Answer options
A: Reserved Instances with one-year terms
B: Multi-Region Pricing Correct answer
C: Dedicated Hosts
D: Data Transfer Pricing
E: Spot Instances with capacity reservations
Correct Answer:
B. Multi-Region Pricing
Explanation

A global financial services company must adhere to data residency regulations, which mandates operating in specific, multiple geographic cloud regions. Cloud service pricing varies significantly between these regions due to factors like local infrastructure costs and taxes. Therefore, the most relevant model for this scenario is Multi-Region Pricing. A FinOps practitioner must analyze and manage the different price points across required regions to effectively optimize costs while maintaining compliance. This involves strategic workload placement and resource selection based on the unique cost structure of each mandated region, directly addressing the dual challenges of cost optimization and regulatory adherence in a global context.

Why Incorrect

A. Reserved Instances with one-year terms: This is a commitment-based discount model applied within a specific region. It does not address the overarching strategy of managing costs across a global, multi-region footprint.
C. Dedicated Hosts: This is a specific compute option for meeting strict compliance or licensing requirements that demand physical server isolation, not a pricing model for managing a global operation.
D. Data Transfer Pricing: This is a single component of cloud costs, related to moving data. While important, it is not the comprehensive pricing model for managing a multi-region architecture.
E. Spot Instances with capacity reservations: This is a cost-optimization tactic for fault-tolerant workloads, typically applied within a single region or availability zone, not a model for global compliance.

References

1. Storment, J.R., Fuller, M., & Quinn, C. (2023). Cloud FinOps, 2nd Edition. O'Reilly Media.

Reference: Chapter 6, "Understanding Cloud Cost and Billing," discusses the various dimensions of cloud cost, explicitly mentioning that the choice of geographic region is a significant factor influencing the price of services. This underpins the concept of managing multi-region pricing.

2. AWS Documentation - Amazon EC2 On-Demand Pricing.

Reference: The official pricing page for AWS EC2 instances demonstrates that prices for the same instance type vary by region. The user interface requires selecting a region to view its specific pricing, confirming that "Multi-Region Pricing" is a fundamental concept practitioners must manage. (e.g., https://aws.amazon.com/ec2/pricing/on-demand/).

3. Google Cloud Documentation - Regions and Zones.

Reference: The "Locations" page in the Google Cloud documentation states, "Pricing varies between regions based on a number of factors." This official vendor statement validates that managing costs across different regions is a key consideration for global deployments. (e.g., https://cloud.google.com/about/locations).

4. FinOps Foundation - FinOps Framework.

Reference: The "Optimize Cloud Usage & Cost" domain within the FinOps Framework includes capabilities like "Managing commitment based discounts." These discounts (e.g., Reserved Instances, Savings Plans) are often purchased for specific regions, requiring an understanding of regional pricing to be effective on a global scale.

Scroll to Top