Free SAP-C02 flashcards

How can a team preview the exact resource actions, including forced replacements, of an AWS CloudFormation stack update before any change is applied?

Create a CloudFormation change set from the revised template. The change set compares the running stack to the proposed template and lists each resource with its planned action and a flag showing whether the update forces a replacement. This lets the team see, for example, that a database would be replaced, gate the release on sign-off, and only then execute the change set. Nothing is applied until execution.

CloudFormation rollback triggers on CloudWatch alarms give you a preview of an update's impact before it runs.

Rollback triggers act only after the update has already started executing, by which point a resource may already have been replaced. They revert a stack after a fault, they do not preview planned actions. To see resource actions and replacements before anything runs, use a change set.

What is the most scalable way to give hundreds of VPCs across many accounts transitive any-to-any routing with centrally controlled route propagation?

AWS Transit Gateway is a regional routing hub that every VPC attaches to, providing transitive routing without a quadratic mesh of links. Shared through AWS Resource Access Manager, accounts across the organisation can attach, and Transit Gateway route tables centrally decide which attachments propagate routes to which. It scales to thousands of attachments.

A full mesh of VPC peering connections is a clean way to give hundreds of VPCs any-to-any reachability.

VPC peering is non-transitive, so a mesh needs a link between every pair, and the link count grows roughly with the square of the VPC count. That becomes unmanageable well before 200 VPCs. AWS Transit Gateway provides transitive routing through one hub instead.

How can an unhealthy Amazon EC2 instance be rebooted automatically the moment it fails, with no added servers and no custom code?

Create an Amazon CloudWatch alarm on the StatusCheckFailed metric and attach a built-in EC2 recovery alarm action that reboots the instance as soon as the alarm enters the ALARM state. The native action fires the instant the status check fails, so recovery is automatic and there is nothing for the team to maintain.

A CloudWatch alarm on a custom memory metric that emails the on-call rota through Amazon SNS removes the manual reboot.

Paging an engineer only shortens the response, it does not remove it. A human still has to log in and reboot the instance, so the recovery stays manual. A CloudWatch alarm with a native EC2 reboot action remediates automatically with no person in the loop.

In the 7Rs migration framework, which strategies fit a per-server licensed packaged ERP suite and a self-hosted SQL Server estate moving to a managed engine?

Repurchase fits licensed or packaged software dropped for a SaaS or different commercial product, which suits a per-server ERP suite. Replatform is a lift-and-optimise that swaps a self-managed component for a managed equivalent, such as moving self-hosted SQL Server onto Amazon RDS without rewriting the application.

A closed packaged ERP suite should be classified as refactor, and lifting a SQL Server estate into AWS unchanged is relocate.

Refactor means re-architecting an application you control, which a closed packaged ERP suite does not allow. Relocate is the VMware Cloud on AWS hypervisor move, not a database engine change, so both labels are mismatched.