NEW
Font size
WorksheetsModule 6: Optimise Phase
Total questions: 30
Worksheet time: 10mins
What is the first step in the optimisation phase after visibility and accountability are established?
Set optimisation goals
Implement automation tools
Identify areas for improvement
Negotiate enterprise agreements
Which of the following is an example of identifying areas for improvement?
Signing a multi-year cloud contract
Eliminating idle resources
Creating a FinOps team
Migrating to multi-cloud
Optimisation goals should primarily be:
General and flexible
Focused only on IT needs
Specific and measurable
Defined by cloud providers
Why should optimisation goals be aligned with business objectives?
To simplify billing
To ensure cloud providers offer discounts
To maximize business value from cloud spend
To eliminate the need for monitoring
Which activity is best supported by optimisation tools and automation?
Negotiating contracts
Identifying idle resources
Defining company strategy
Training developers
Native cloud provider tools are mainly used to:
Replace FinOps processes
Track, analyse, and optimise usage and spend
Eliminate reserved instances
Manage only on-premise costs
After implementing optimisation changes, what is the next critical action?
Stop monitoring costs
Renegotiate pricing
Monitor results against goals
Increase cloud usage
Why is the optimisation phase considered iterative?
Cloud costs never change
Goals and strategies must be regularly adjusted
Automation replaces decision-making
Providers require constant changes
What best defines usage optimisation?
Negotiating lower prices
Managing and adapting resources to minimise waste
Migrating workloads to on-premise
Reducing performance
Right-sizing primarily focuses on:
Increasing resource capacity
Matching capacity to actual needs
Eliminating auto-scaling
Locking in long-term contracts
What is a risk of under-provisioning resources?
Higher costs
Performance issues
Overcommitment
Unused discounts
Auto-scaling helps optimise costs by:
Locking instance size
Scaling resources based on demand
Eliminating monitoring
Preventing workload changes
Which workload is most suitable for spot instances?
Mission-critical production systems
Predictable long-term workloads
Interruption-tolerant workloads
Compliance-heavy workloads
Waste elimination focuses on identifying:
Reserved instances
Idle or unused resources
High-performing workloads
Pricing models
Improving performance efficiency may include:
Increasing instance sizes only
Optimising code and using CDNs
Avoiding caching
Disabling monitoring
Savings plans and reserved instances are best for:
Unpredictable workloads
Short-term workloads
Predictable workloads
Temporary testing environments
Continuous monitoring in FinOps means:
Monitoring only once a year
A continual cycle of measurement and adjustment
Eliminating automation
Tracking only total spend
Rate optimisation focuses on:
Reducing performance
Maximising value from cloud spend
Eliminating all discounts
Avoiding commitments
On-demand instances are best suited for:
Long-term stable workloads
Predictable workloads
Short-term or unpredictable workloads
Interruption-tolerant workloads
What is a key benefit of reserved instances?
No commitment required
Higher flexibility than spot instances
Lower hourly rates through commitment
Automatic scaling
Savings Plans typically require:
Commitment to instance type
Commitment to a usage amount over time
Multi-cloud usage
No long-term agreement
Volume discounts work because:
Costs increase with usage
Providers charge more per unit
Unit cost decreases as usage increases
Discounts apply only to storage
Enterprise agreements usually require:
No commitments
Small workloads
Substantial usage commitments
Spot instance usage
Multi-cloud strategies may help with optimisation by:
Increasing complexity only
Avoiding discounts
Choosing the most cost-effective provider per service
Eliminating monitoring
Reserved Instances are most cost-effective when workloads are:
Short-lived
Predictable and stable
Highly volatile
Rarely used
Why is RI utilisation monitoring important?
To cancel contracts early
To ensure reserved capacity is fully used
To increase on-demand usage
To eliminate automation
RI marketplaces allow organisations to:
Eliminate reservations
Buy or sell unused reservations
Avoid commitments
Increase spot usage
A key advantage of Committed Use Discounts (CUDs) is:
No commitment required
Instance flexibility within a service family
Higher prices
Short-term contracts
CUDs are particularly useful when workloads:
Never change
Are highly predictable
May evolve over time
Are always idle
What is essential for both RI and CUD strategies?
One-time analysis
Continuous monitoring and adjustment
Eliminating flexibility
Avoiding business alignment
