Exam (elaborations)
AWS SAA-C02 Exam (1-50) Questions and Answers
AWS SAA-C02 Exam (1-50) Questions and Answers
[Show more]
Preview 3 out of 28 pages
Uploaded on
October 1, 2024
Number of pages
28
Written in
2024/2025
Type
Exam (elaborations)
Contains
Questions & answers
Institution
AWS SAA
Course
AWS SAA
$13.49
100% satisfaction guarantee
Immediately available after payment
Both online and in PDF
No strings attached
AWS SAA-C02 Exam (1-50) Questions
and Answers
#1
A iisolutions iiarchitect iiis iidesigning iia iisolution iiwhere iiusers iiwill iibe iidirected iito iia
iibackup iistatic iierror iipage iiif iithe iiprimary iiwebsite iiis iiunavailable. iiThe iiprimary
iiwebsiteג€™sDNS iirecords iiare iihosted iiin iiAmazon iiRoute ii53 iiwhere iitheir iidomain iiis
iipointing iito iian iiApplication iiLoad iiBalancer ii(ALB).Which iiconfiguration iishould iithe
iisolutions iiarchitect iiuse iito iimeet iithe iicompanyג€™s iineeds iiwhile iiminimizing iichanges
iiand iiinfrastructure iioverhead?
A. iiPoint iia iiRoute ii53 iialias iirecord iito iian iiAmazon iiCloudFront iidistribution iiwith iithe
iiALB iias iione iiof iiits iiorigins. iiThen, iicreate iicustom iierror iipages iifor iithe iidistribution.
B. iiSet iiup iia iiRoute ii53 iiactive-passive iifailover iiconfiguration. iiDirect iitraffic iito iia iistatic
iierror iipage iihosted iiwithin iian iiAmazon iiS3 iibucket iiwhen iiRoute ii53 iihealth iichecks
iidetermine iithat iithe iiALB iiendpoint iiis iiunhealthy.
C. iiUpdate iithe iiRoute ii53 iirecord iito iiuse iia iilatency-based iirouting iipolicy. iiAdd iithe
iibackup iistatic iierror iipage iihosted iiwithin iian iiAmazon iiS3 iibucket iito iithe iir ii- iiCorrect
iiAnswers ii-B
(Active-passive iifailover ii-Use iian iiactive-passive iifailover iiconfiguration iiwhen iiyou iiwant
iia iiprimary iiresource iior iigroup iiof iiresources iito iibe iiavailable iithe iimajority iiof iithe iitime
iiand iiyou iiwant iia iisecondary iiresource iior iigroup iiof iiresources iito iibe iion iistandby iiin
iicase iiall iithe iiprimary iiresources iibecome iiunavailable. iiWhen iiresponding iito iiqueries,
iiRoute ii53 iiincludes iionly iithe iihealthy iiprimary iiresources. iiIf iiall iithe iiprimary iiresources
iiare iiunhealthy, iiRoute ii53 iibegins iito iiinclude iionly iithe iihealthy iisecondary iiresources
iiin iiresponse iitoDNS iiqueries.To iicreate iian iiactive-passive iifailover iiconfiguration iiwith
iione iiprimary iirecord iiand iione iisecondary iirecord, iiyou iijust iicreate iithe iirecords iiand
iispecify iiFailover iifor iithe iirouting iipolicy. iiWhen iithe iiprimary iiresource iiis iihealthy,
iiRoute ii53 iiresponds iito iiDNS iiqueries iiusing iithe iiprimary iirecord. iiWhen iithe iiprimary
iiresource iiis iiunhealthy, iiRoute53 iiresponds iito iiDNS iiqueries iiusing iithe iisecondary
iirecord.How iiAmazon iiRoute ii53 iiaverts iicascading iifailuresAs iia iifirst iidefense iiagainst
iicascading iifailures, iieach iirequest iirouting iialgorithm ii(such iias iiweighted iiand iifailover)
iihas iia iimode iiof iilast iiresort. iiIn iithis iispecial iimode, iiwhen iiall iirecords iiare iiconsidered
iiunhealthy, iithe iiRoute ii53 iialgorithm iireverts iito iiconsidering iiall iirecords iihealthy.For
iiexample, iiif iiall iiinstances iiof iian iiapplication, iion iiseveral iihosts, iiare iirejecting iihealth
iicheck iirequests, iiRoute ii53 iiDNS iiservers iiwill iichoose iian iianswer iianyway iiand iireturn
iiit iirather iithan iireturning iino iiDNS iianswer iior iireturning iian iiNXDOMAIN ii(non-existent
iidomain) iiresponse. iiAn iiapplication iican iirespond iito iiusers iibut iistill iifail iihealth iichecks,
iiso iithis iiprovides iisome iiprotection iiagainst iimisconfiguration.Similarly, iiif iian
iiapplication iiis iioverloaded, iiand iione iiout iiof iithree iiendpoints iifails iiits iihealth iichecks,
,iiso iithat iiit's iiexcluded iifrom iiRoute ii53 iiDNS iiresponses, iiRoute ii53 iidistributes
iiresponses iibetween iithe iitwo iiremaining iiendpoints. iiIf iithe iiremaining iiendpoints iiare
iiunable iito iihandle iithe
#2
A iisolutions iiarchitect iiis iidesigning iia iihigh iiperformance iicomputing ii(HPC) iiworkload
iion iiAmazon iiEC2. iiThe iiEC2 iiinstances iineed iito iicommunicate iito iieach iiother
iifrequently iiand iirequire iinetwork iiperformance iiwith iilow iilatency iiand iihigh
iithroughput.Which iiEC2 iiconfiguration iimeets iithese iirequirements?
A. iiLaunch iithe iiEC2 iiinstances iiin iia iicluster iiplacement iigroup iiin iione iiAvailability
iiZone.
B. iiLaunch iithe iiEC2 iiinstances iiin iia iispread iiplacement iigroup iiin iione iiAvailability
iiZone.
C. iiLaunch iithe iiEC2 iiinstances iiin iian iiAuto iiScaling iigroup iiin iitwo iiRegions iiand iipeer
iithe iiVPCs.
D. iiLaunch iithe iiEC2 iiinstances iiin iian iiAuto iiScaling iigroup iispanning iimultiple
iiAvailability iiZones. ii- iiCorrect iiAnswers ii-A ii
(Placement iigroups ii-When iiyou iilaunch iia iinew iiEC2 iiinstance, iithe iiEC2 iiservice
iiattempts iito iiplace iithe iiinstance iiin iisuch iia iiway iithat iiall iiof iiyour iiinstances iiare
iispread iiout iiacross iiunderlying iihardware iito iiminimize iicorrelated iifailures. iiYou iican
iiuse iiplacement iigroups iito iiinfluence iithe iiplacement iiof iia iigroup iiof iiinterdependent
iiinstances iito iimeet iithe iineeds iiof iiyour iiworkload. iiDepending iion iithe iitype iiof
iiworkload.Cluster ii"€ גiipacks iiinstances iiclose iitogether iiinside iian iiAvailability iiZone.
iiThis iistrategy iienables iiworkloads iito iiachieve iithe iilow-latency iinetwork iiperformance
iinecessary iifor iitightly-coupled iinode-to-node iicommunication iithat iiis iitypical iiof iiHPC
iiapplications.Reference:https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/place
ment-groups.html)
#3
A iicompany iiwants iito iihost iia iiscalable iiweb iiapplication iion iiAWS. iiThe iiapplication iiwill
iibe iiaccessed iiby iiusers iifrom iidifferent iigeographic iiregions iiof iithe iiworld.Application
iiusers iiwill iibe iiable iito iidownload iiand iiupload iiunique iidata iiup iito iigigabytes iiin iisize.
iiThe iidevelopment iiteam iiwants iia iicost-effective iisolution iito iiminimize iiupload iiand
iidownload iilatency iiand iimaximize iiperformance.What iishould iia iisolutions iiarchitect iido
iito iiaccomplish iithis?
A. iiUse iiAmazon iiS3 iiwith iiTransfer iiAcceleration iito iihost iithe iiapplication.
B. iiUse iiAmazon iiS3 iiwith iiCacheControl iiheaders iito iihost iithe iiapplication.
C. iiUse iiAmazon iiEC2 iiwith iiAuto iiScaling iiand iiAmazon iiCloudFront iito iihost iithe
iiapplication.
D. iiUse iiAmazon iiEC2 iiwith iiAuto iiScaling iiand iiAmazon iiElastiCache iito iihost iithe
iiapplication. ii- iiCorrect iiAnswers ii-C
(Reference:https://aws.amazon.com/ec2/autoscaling/)
#4
A iicompany iiis iimigrating iifrom iian iion-premises iiinfrastructure iito iithe iiAWS iiCloud.
iiOne iiof iithe iicompanyג€™s iiapplications iistores iifiles iion iia iiWindows iifile iiserver iifarm
, iithat iiuses iiDistributed iiFile iiSystem iiReplication ii(DFSR) iito iikeep iidata iiin iisync. iiA
iisolutions iiarchitect iineeds iito iireplace iithe iifile iiserver iifarm.Which iiservice iishould iithe
iisolutions iiarchitect iiuse?
A. iiAmazon iiEFS
B. iiAmazon iiFSx
C. iiAmazon iiS3
D. iiAWS iiStorage iiGateway ii- iiCorrect iiAnswers ii-B
(Migrating iiExisting iiFiles iito iiAmazon iiFSx iifor iiWindows iiFile iiServer iiUsing iiAWS
iiDataSyncWe iirecommend iiusing iiAWS iiDataSync iito iitransfer iidata iibetween iiAmazon
iiFSx iifor iiWindows iiFile iiServer iifile iisystems. iiDataSync iiis iia iidata iitransfer iiservice
iithat iisimplifies, iiautomates, iiand iiaccelerates iimoving iiand iireplicating iidata iibetween
iion-premises iistorage iisystems iiand iiother iiAWS iistorage iiservices iiover iithe iiinternet
iiorAWS iiDirect iiConnect. iiDataSync iican iitransfer iiyour iifile iisystem iidata iiand
iimetadata, iisuch iias iiownership, iitime iistamps, iiand iiaccess
iipermissions.Reference:https://docs.aws.amazon.com/fsx/latest/WindowsGuide/migrate
-files-to-fsx-datasync.html)
#5
A iicompany iihas iia iilegacy iiapplication iithat iiprocesses iidata iiin iitwo iiparts. iiThe iisecond
iipart iiof iithe iiprocess iitakes iilonger iithan iithe iifirst, iiso iithe iicompany iihas iidecided iito
iirewrite iithe iiapplication iias iitwo iimicroservices iirunning iion iiAmazon iiECS iithat iican
iiscale iiindependently.How iishould iia iisolutions iiarchitect iiintegrate iithe iimicroservices?
A. iiImplement iicode iiin iimicroservice ii1 iito iisend iidata iito iian iiAmazon iiS3 iibucket. iiUse
iiS3 iievent iinotifications iito iiinvoke iimicroservice ii2.
B. iiImplement iicode iiin iimicroservice ii1 iito iipublish iidata iito iian iiAmazon iiSNS iitopic.
iiImplement iicode iiin iimicroservice ii2 iito iisubscribe iito iithis iitopic.
C. iiImplement iicode iiin iimicroservice ii1 iito iisend iidata iito iiAmazon iiKinesis iiData
iiFirehose. iiImplement iicode iiin iimicroservice ii2 iito iiread iifrom iiKinesis iiData iiFirehose.
D. iiImplement iicode iiin iimicroservice ii1 iito iisend iidata iito iian iiAmazon iiSQS iiqueue.
iiImplement iicode iiin iimicroservice ii2 iito iiprocess iimessages iifrom iithe iiqueue. ii- iiCorrect
iiAnswers ii-D
#6
A iicompany iicaptures iiclickstream iidata iifrom iimultiple iiwebsites iiand iianalyzes iiit iiusing
iibatch iiprocessing. iiThe iidata iiis iiloaded iinightly iiinto iiAmazon iiRedshift iiand iiis
iiconsumed iiby iibusiness iianalysts. iiThe iicompany iiwants iito iimove iitowards iinear-real-
time iidata iiprocessing iifor iitimely iiinsights. iiThe iisolution iishould iiprocess iithe iistreaming
iidata iiwith iiminimal iieffort iiand iioperational iioverhead.Which iicombination iiof iiAWS
iiservices iiare iiMOST iicost-effective iifor iithis iisolution? ii(Choose iitwo.)
A. iiAmazon iiEC2
B. iiAWS iiLambda
C. iiAmazon iiKinesis iiData iiStreams
D. iiAmazon iiKinesis iiData iiFirehose
E. iiAmazon iiKinesis iiData iiAnalytics ii- iiCorrect iiAnswers ii-BD
(Kinesis iiData iiStreams iiand iiKinesis iiClient iiLibrary ii(KCL) ii"€ גiiData iifrom iithe iidata
iisource iican iibe iicontinuously iicaptured iiand iistreamed iiin iinear iireal-time iiusing