CompTIA Cloud+ Study Guide. Ben Piper

8 4.2 Given a scenario, maintain efficient operation of a cloud environment.Confirm completion of backupsLife-cycle managementRoadmapsOld/current/new versionsUpgrading and migrating systemsDeprecations or end of lifeChange managementAsset managementConfiguration management database (CMDB)PatchingFeatures or enhancementsFixes for broken or critical infrastructure or applicationsScope of cloud elements to be patchedHypervisorsVMsVirtual appliancesNetworking componentsApplicationsStorage componentsFirmwareSoftwareOSPoliciesn-1RollbacksImpacts of process improvements on systemsUpgrade methodsRolling upgradesBlue-greenCanaryActive-passiveDevelopment/QA/production/DRDashboard and reportingTaggingCostsChargebacksShowbacksElasticity usageConnectivityLatencyCapacityIncidentsHealthOverall utilizationAvailability 4, 5, 7, 8 4.3 Given a scenario, optimize cloud environments.Right-sizingAuto-scalingHorizontal scalingVertical scalingCloud burstingComputeCPUsGPUsMemoryContainersStorageTiersAdaptive optimizationIOPSCapacityDeduplicationCompressionNetworkBandwidthNetwork interface controllers (NICs)LatencySDNEdge computingCDNPlacementGeographicalCluster placementRedundancyColocationDevice drivers and firmwareGenericVendorOpen source 1, 2, 7, 8 4.4 Given a scenario, apply proper automation and orchestration techniques.Infrastructure as codeInfrastructure components and their integrationContinuous integration/ continuous deployment (CI/CD)Version controlConfiguration managementPlaybookContainersAutomation activitiesRoutine operationsUpdatesScalingShutdownsRestartsCreate internal APIsSecure scriptingNo hardcoded passwordsUse of individual service accountsPassword vaultsKey-based authenticationOrchestration sequencing 1, 2, 4, 5, 7 4.5 Given a scenario, perform appropriate backup and restore operations.Backup typesIncrementalDifferentialFullSynthetic fullSnapshotBackup objectsApplication-level backupFilesystem backupDatabase dumpsConfiguration filesBackup targetsTapeDiskObjectBackup and restore policiesRetentionSchedulesLocationSLAsRecovery time objective (RTO)Recovery point objective (RPO)Mean time to recovery (MTTR)3-2-1 ruleThree copies of dataTwo different mediaOne copy off siteRestoration methodsIn placeAlternate locationRestore filesSnapshot 5 4.6 Given a scenario, perform disaster recovery tasks.FailoversFailbackRestore backupsReplicationNetwork configurationsOn-premises and cloud sitesHotWarmColdRequirementsRPORTOSLACorporate guidelinesDocumentationDR kitPlaybookNetwork diagramGeographical datacenter requirements 6

5.0 Troubleshooting

Exam Objective	Chapters
5.1 Given a scenario, use the troubleshooting methodology to resolve cloud-related issues.Always consider corporate policies, procedures, and impacts before implementing changes.	10
Identify the problemQuestion the user and identify user changes to the computer and perform backups before making changesInquire regarding environmental or infrastructure changesEstablish a theory of probable cause (question the obvious)If necessary, conduct external or internal research based on symptomsTest the theory to determine causeOnce the theory is confirmed, determine the next steps to resolve the problemIf the theory is not confirmed, re-establish a new theory or escalateEstablish a plan of action to resolve the problem and implement the solutionVerify full system functionality and, if applicable, implement preventive measuresDocument the findings, actions, and outcomes throughout the process.
5.2 Given a scenario, troubleshoot security issues.PrivilegeMissingIncompleteEscalationKeysAuthenticationAuthorizationSecurity groupsNetwork security groupsDirectory security groupsKeys and certificatesExpiredRevokedTrustCompromisedMisconfiguredMisconfigured or misapplied policiesData security issuesUnencrypted dataData breachesMisclassificationLack of encryption in protocolsInsecure ciphersExposed endpointsMisconfigured or failedsecurity appliancesIPSIDSNACWAFUnsupported protocolsExternal/internal attacks	10
5.3 Given a scenario, troubleshoot deployment issues.Connectivity issuesCloud service provider (CSP) or Internet service provider (ISP) outagesPerformance degradationLatencyConfigurationsScriptsApplications in containersMisconfigured templatesMissing or incorrect tagsInsufficient capacityScaling configurationsComputeStorageBandwidth issuesOversubscriptionLicensing issuesVendor-related issuesMigrations of vendors or platformsIntegration of vendors or platformsAPI request limitsCost or billing issues	9
5.4 Given a scenario, troubleshoot connectivity issues.Network security group misconfigurationsACLInheritanceCommon networking configuration issuesPeeringIncorrect subnetIncorrect IP addressIncorrect IP spaceRoutesDefaultStaticDynamicFirewallIncorrectly administered micro-segmentationNetwork address translation (NAT)VPNSourceDestinationLoad balancersMethodsHeadersProtocolsEncryptionBack endsFront endsDNS recordsVLAN/VXLAN/GENEVEProxyMaximum transmission unit (MTU)Quality of service (QoS)Time synchronization issuesNetwork troubleshooting toolspingtracert/tracerouteflushdnsipconfig/ifconfig/ipnslookup/dignetstat/ssroutearpcurlPacket capturePacket analyzerOpenSSL client	10
5.5 Given a scenario, troubleshoot common performance issues.Resource utilizationCPUGPUMemoryStorageI/OCapacityNetwork bandwidthNetwork latencyReplicationScalingApplicationMemory managementService overloadIncorrectly configured or failed load balancing	9
5.6 Given a scenario, troubleshoot automation or orchestration issues.Account mismatchesChange management failuresServer name changesIP address changesLocation changesVersion/feature mismatchAutomation tool incompatibilityDeprecated featuresAPI version incompatibilityJob validation issuePatching failure	9