AWS Cloud Practitioner Certification Exam
With Correct Questions And Answers 2024
Cloud .benefits .over .on-premises .- .correct .answer.1. .Trade .capital .expense .for .variable
.expense
2. .Massive .economies .of .scale
3. .Stop .guessing .capacity
4. .Increase .speed .and .agility
5. .Stop .spending .money .on .running .and .maintaining .data .centers
6. .Go .global .in .minutes
Basic .benefits .of .the .cloud .- .correct .answer.1. .Scalability .- .ability .to .resize .your .resources
.as .necessary.
2. .Agility .- .increasing .speed .(via .global .reach), .ease .of .experimentation .(via .access .to
.new .resources)
3. .Innovation .- .experiment .quickly
4. .Efficiencies .of .Scale .- .deploy .system .in .multiple .regions .around .the .world .providing
.lower .latency, .and .a .better .experience .for .your .customers .at .a .minimal .cost.
5. .Reliability .- .ability .to .recover .from .infrastructure .service .failures
AWS .Shared .Responsibility .Model .- .correct .answer.1. .User .Data
2. .Applications
3. .Guest .Operating .System
------------------------------
4. .Hypervisor .(virtual .machine .monitor)
5. .Network
6. .Physical
AWS .Cloud .- .correct .answer.Access .to .servers, .database, .storage, .higher-level
.application .components .in .seconds. .Treat .them .as .temporary .and .disposable .resources,
.free .from .the .constraints .of .fixed .and .finite .IT .infrastructure.
Reduce .risks, .auto .scale, .ensure .reliable .coverage .even .in .the .face .of .a .natural .disaster,
.and .secure .data.
,Security .Compliance .- .Responsibility .of .Customer .- .correct .answer.Customers .are
.responsible .for .configuring .in .secure .and .controlled .way
1. .Must .review .info/resources .available .to .meet .compliance .requirements
2. .Designs/Implements .controls .owned .by .outside .parties
3. .Verifies .all .control .objectives .are .met
Security .Compliance .- .Responsibility .of .AWS .- .correct .answer.AWS's .approach .to
.compliance: .works .with .3rd .party .auditors/agents .to .provide .customers .compliant
.security.
1. .Risk .management .= .reevaluate .2x/year .(at .least) .to .identify .the .risk .and .address .them
2. .Control .environment .= .internal .and .external .assessments
3. .Information .security .= .establish .framework .and .policies, .formal .progress .to .protect
.confidential .data
Security .Best .Practices .- .correct .answer.a. .Test .often, .patch .quickly, .and .respond .to
.incidents .at .a .lightning .speed
b. .Data .Security: .resilient .infrastructure, .highly .secure, .strong .safeguards
c. .Continual .Improvement: .constant .evolving .on .IAM, .logging, .DDOS .protection
d. .Advanced .Security .Services: .address .real-time .emerging .risk, .ops .management
e. .Network .Security: .built-in .firewalls, .encryption .in .transit, .private/dedicated .connection,
.DDOS .mitigation
f. .Inventory .and .Configuration .Tools: .deployment, .template .management, .definitive .tools
g. .Data .Encryption: .encryption .capabilities, .key .management .options, .hardware .based
.key
h. .Access .Control: .IAM, .multi-factor .authentication, .integration .and .federation
.w/corporate .discretion, .Amazon .Cognito, .SSO
i. .Monitoring .& .Logging: .visibility .into .API .calls, .log .aggregation, .alert .notification
IAM .- .correct .answer.Identity .and .Access .Management
Groups .- .correct .answer.collection .of .users, .users .can .be .in .multiple .groups
Users .- .correct .answer.permanent .named .operator. .Credentialed .or .temporary. .Human
.or .machine. .Automated .method.
Role .- .correct .answer.authentication .method, .operator, .human .or .machine. .Credentialed
.or .temporary. .Role .≠ .permissions.
Policy .Documents .- .correct .answer.Permissions. .Json. .Attached .to .either .a .role, .group,
.or .user. .Looked .at .from .a .single .view.
i. .Deny .Statements: .Override .any .Allow .statements
ii. .Implicit .allow .if .there .is .not .a .deny .statement
iii. .Every .API .action .(successful .or .denied) .is .recorded .in .Cloudtrail
If .there .are .no .policy .documents .attached .to .IAM, .nothing .happens .but .it .gets .tracked .in
.CloudTrail
, Amazon .Inspector .- .correct .answer.Automated .security .assessment .service. .Eliminates
.security .risks .- .runs .security .benchmarks .against .specific .EC2 .instances. .
i. .Looks .for .deviations .from .best .practices .or .vulnerabilities
ii. .Findings .are .dependent .on .choices .of .rule .packages
iii. .Vulnerabilities .found .before .and .after .deployment
iv. .API .driven .- .can .be .integrated .in .devops .process
v. .Visibility .in .security .testing .during .app .development
vi. .Can .define .standards .and .best .practices .for .organizational .enforcement
AWS .Shield .- .correct .answer.provides .always-on .detection .and .automatic .inline
.mitigations .that .minimize .application .downtime .and .latency, .so .there .is .no .need .to
.engage .AWS .Support .to .benefit .from .DDoS .protection. .Two .tiers .- .Standard .and
.Advanced.
Benefits: .Minimizes .downtime .& .latency. .Cost .efficient, .seamless .integration,
.customizable .protection, .proactively .and .automatically .blocks .bad .traffic.
Helps .overcome .challenges .of .mitigating .DDOS .attacks; .overcome .costs .and .challenges
Denial .of .Service .Attacks .(DOS) .- .correct .answer.website .or .app .is .unavailable .bc .of
.large .bandwidth .consumption .or .tied .up .other .system .resources. .Disrupts .access .for .the
.legit .users.
Distribution .of .Denial .of .Service .Attacks .(DDOS) .- .correct .answer.Attacker .uses .multiple
.sources .- .compromised .computer. .Objective .is .to .knock .the .webapp .offline .for .a .period .of
.time.
Amazon .Web .Application .Firewalls .(WAF) .- .correct .answer.Protects .web .apps .from
.common .web .exploits. .Write .your .own .rules .to .allow .or .deny .traffic .based .on .its .HTTPS
.requests. .Block .requests .of .app .layers .before .reaching .the .AWS .web .infrastructure.
Can .be .attached .to .cloudfront .or .application .load .balancer. .Protects .against .DDoS
.attacks.
Cloud .Deployement: .Cloud .- .correct .answer.fully .deployed .in .cloud; .all .part .of .apps .run .in
.cloud; .either .been .created .in .cloud .or .have .been .migrated .from .existing .infrastructure;
.built .on .low-level .infra .pieces. .Startups .use .this.
Cloud .Deployement: .Hybrid .- .correct .answer.most .common .method .is .between .cloud
.and .existing .on-premises .infrastructure .to .extend, .grow, .an .org's .infra .into .cloudwhile
.connecting .cloud .resources .to .internal .system. .Banks .use .this.
Cloud .Deployement: .On .Premises .- .correct .answer.no .benefits .of .cloud, .but .people .use .it
.bc .it .provides .dedicated .resources; .same .as .legacy .IT .infrastructure. .sometmes .called
.'private .cloud'. .For .super .sensitive .stuff, .like .Government .uses .it.