Cloud+ V3 Deployment Rollback Procedures

1. What is a database migration rollback strategy that maintains both old and new schemas?

Dual-write pattern

Shadow copying

Schema versioning

Table partitioning

2. Which metric is essential for measuring rollback success?

Time to restore service and data consistency

Number of employees notified

Color of server lights

Month of the year

3. What is a 'feature flag' used for in safe deployments?

To enable or disable features without redeployment

To mark completed tasks

To identify team members

To measure cloud costs

4. How should deployment logs be retained for rollback troubleshooting?

Indefinitely in secure, indexed storage

Deleted after 24 hours

Only printed on paper

Stored on local employee computers

5. What is a 'smoke test' in the context of post-deployment validation?

A quick test to verify basic functionality after deployment

Testing smoke alarm systems

A comprehensive 24-hour stability test

Testing network connectivity only

6. Which automated tool helps ensure consistent rollback procedures across multiple deployments?

Orchestration and automation platforms

Manual spreadsheets

Email notifications

Paper-based checklists

7. What is the purpose of creating a 'golden image' in cloud deployments?

To provide a tested, known-good baseline for quick rollback

To increase deployment costs

To eliminate testing requirements

To prevent any updates

8. In a canary deployment, what percentage of traffic typically goes to the new version initially?

5-10%

50%

100%

0%

9. What is the advantage of using infrastructure as code (IaC) for deployment?

Enables quick rollback to previous infrastructure states

Eliminates the need for backups

Reduces cloud expenses by 90%

Replaces all security measures

10. Which component must be documented for successful rollback procedures?

Previous version checksums and configuration states

Employee personal preferences

Marketing campaign schedules

Office supply inventory

11. What is the primary purpose of a rollback procedure in cloud deployment?

To restore a system to a previous stable state after a failed deployment

To increase deployment speed

To reduce cloud storage costs

To eliminate the need for testing

12. When should a rollback be initiated after a deployment failure?

After waiting one week to observe

Immediately after detecting critical issues

Only if all users complain

During the next scheduled maintenance window

13. What does RTO stand for in the context of disaster recovery?

Recovery Time Objective

Rollback Testing Operation

Resource Tracking Optimization

Redundant Transfer Operation

14. Which tool is commonly used for version control in cloud deployments?

Git or similar VCS

Email attachments

USB drives

Printed documentation

15. In Cloud+ V3, what is a 'rolling deployment'?

Deploying to all servers simultaneously

Gradually replacing old instances with new ones

Deploying only on weekends

Manual deployment by IT staff

16. What should be monitored during the initial rollout phase to detect deployment issues early?

Only database size

Application performance metrics and error rates

Network cable status

Employee login times

17. Which rollback method restores data to a point in time before the failed deployment?

Configuration rollback

Point-in-time recovery

Version revert

Snapshot restoration

18. What is a critical prerequisite before executing a rollback procedure?

Notifying all users immediately

Having a verified backup of the previous stable state

Deleting all deployment logs

Updating all documentation first

19. In a blue-green deployment, what does the 'blue' environment represent?

The new version being tested

The currently running production version

The backup database

The development environment

20. Which deployment strategy minimizes risk by gradually shifting traffic to a new version?

Big bang deployment

Blue-green deployment

Canary deployment

Shadow deployment

Cloud+ V3 Basic Deployment Rollback Procedures Quiz