Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 48

Question 470

A high-rate transaction database uses st1 EBS. Large sequential log scans run well, but random 8KiB reads have unacceptable latency. What is the storage mismatch?

Increase the st1 volume size only to refill its throughput burst credits and assume the HDD can now meet submillisecond random read latency.
Attach a second st1 volume and stripe them without checking whether repeated random 8-KiB synchronous I/O still exceeds HDD access-latency requirements.
Increase st1 throughput provisioning to its supported burst limit and assume that MB/s guarantees low-latency random transaction IOPS.
The workload needs random low-latency IOPS better served by an SSD tier such as io2 or correctly sized gp3.

Explanation

Correct Answer

st1 HDD favors sequential throughput and has different random I/O latency.

Incorrect Answers

st1 is optimized for sequential throughput. More capacity and burst credits cannot change the high random I/O latency characteristics into those of SSD io2 or gp3.

Striping can raise aggregate throughput for compatible loads but not remove inherent seek-related random I/O latency. Choose SSD storage and verify end-to-end latency.

HDD sequential MB/s and random 8-KiB transactional IOPS/latency are different workload dimensions; the st1 class is not designed for this access pattern.

Question 471

A 1-TiB EBS st1 volume handles a large sequential read job at approximately 250 MiB/s for a while, but after long sustained processing throughput falls toward its baseline while the EC2 network remains healthy. CloudWatch BurstBalance has dropped near zero. What explains the slowdown?

The st1 throughput burst-credit bucket was depleted, so sustained performance fell toward the size-based baseline until credits recover.
The EBS st1 volume switched from HDD to S3 Intelligent-Tiering after 30 minutes and needs an S3 restore request.
Increasing EC2 IAM permissions restores already-spent st1 burst credits without changing the actual workload or volume capacity.
Enabling Provisioned IOPS io2 settings on a separate unattached volume automatically raises this st1 volume’s baseline throughput.

Explanation

Correct Answer

st1 uses volume-size-based baseline throughput and an accumulated burst-credit pool. A 1-TiB volume can burst substantially faster than its baseline, but extended high demand can spend the credits and expose the baseline ceiling.

Incorrect Answers

st1 remains an EBS HDD block volume; it does not automatically tier itself into S3 object storage, and Glacier restore workflows do not govern its throughput.

IAM authorizes operations but does not reset or increase the st1 performance credit bank. Model the sustained throughput needed versus the volume baseline and workload rate.

Provisioning a different EBS volume has no effect on the burst budget of the currently attached st1 device. Right-size this volume or choose a suitable sustained-throughput type.

Question 472

A shared EFS directory is reachable from EC2 instances in AZ-a but not AZ-b. The filesystem exists, and AZ-b instances have the correct IAM identity; their NFS security group path to the mount target is blocked. Why?

EFS files are automatically local-only to the first EC2 instance that created them.
Create the missing EFS mount target in AZ-b but leave inbound NFS TCP 2049 blocked on its security group.
Update IAM filesystem permissions to allow the instances but leave the AZ-b mount target security group still rejecting TCP 2049.
Network access to an eligible EFS mount target, including required NFS TCP 2049 security rules, is missing for AZ-b.

Explanation

Correct Answer

POSIX/IAM rights do not bypass NFS network access to file system mount targets.

Incorrect Answers

EFS is shared network file storage.

Mount-target placement is needed, but it does not bypass security-group filtering; NFS connectivity must be permitted along the actual client-to-target path.

IAM authorization is distinct from network transport. A principal can be authorized yet fail to mount when the NFS security-group path remains closed.

Question 473

An EFS file system using Bursting mode slows after sustained busy hours even though storage usage and network links are stable. CloudWatch shows burst credit depletion. What is happening?

EFS Bursting mode promises infinite peak throughput irrespective of credits.
Increase the number of EFS mount targets while retaining the same Bursting throughput mode and a depleted file-system credit bucket.
Burst credits for the Bursting throughput mode were exhausted; compare Elastic or Provisioned throughput to the sustained demand.
Increase the EFS permitted client connections but keep its depleted bursting credit pool, assuming more NFS sessions raise effective sustained file-system throughput.

Explanation

Correct Answer

Bursting mode has a capacity/credit relationship that may not fit continuous high throughput.

Incorrect Answers

Bursting is not an unlimited sustained mode.

Additional AZ mount targets improve connectivity, but do not refill the throughput credit balance for a sustained workload; change throughput sizing or mode when justified.

NFS concurrency cannot bypass the service throughput baseline once burst credits are exhausted. Choose a suitable sustained throughput mode or workload shape.

Question 474

A client interrupted a multipart S3 upload after sending half its parts and immediately issues GET for the full intended key. GET reports NotFound. Why?

Every uploaded part is automatically joined into a visible object even without CompleteMultipartUpload.
Issue ListParts successfully and assume an inventory of uploaded parts is equivalent to a successful CompleteMultipartUpload operation.
Multipart parts are not committed as a visible object until a successful CompleteMultipartUpload.
Call AbortMultipartUpload for the upload ID and expect all aborted parts to appear as a completed object with that key.

Explanation

Correct Answer

Incomplete uploads consume part storage but do not create a retrievable complete object.

Incorrect Answers

Completion is the commit step.

ListParts enumerates uploaded parts, but does not commit an S3 object. CompleteMultipartUpload with the correct upload ID and part list must succeed before normal GetObject resolves the key.

Abort cancels the multipart upload and makes its staged parts unavailable; it cannot stand in for CompleteMultipartUpload to create the final object.

Question 475

S3 Transfer Acceleration was enabled for global uploads, but a network performance test shows no improvement and increased charges for users close to the bucket Region. What does that imply?

Transfer Acceleration guarantees lower cost for every upload regardless of geography.
Enable Transfer Acceleration and use its accelerated endpoint for clients in the same Region, assuming its edge path always improves an already short local route.
Acceleration should be measured per network path and disabled where latency or cost benefit is absent.
Increase the S3 multipart upload part count without testing whether client Internet routing, request overhead or fees actually improve for nearby users.

Explanation

Correct Answer

Edge-optimized transfer is optional and not universally faster or cheaper.

Incorrect Answers

Pricing and path advantage vary.

Acceleration performance depends on client location and route; AWS recommends measuring upload speed and price rather than presuming local clients benefit.

Parallel multipart requests can improve throughput/recovery but do not inherently make a nearby client path faster or justify additional acceleration charges.

Question 476

An application writes to S3 Express One Zone expecting it to remain available when its selected AZ fails entirely. Data is unavailable during the AZ outage. Why?

S3 Express One Zone is an automatically replicated multi-Region object storage class.
S3 Express One Zone stores the directory-bucket data in one selected AZ, so zone failure is within its explicit resilience tradeoff.
All S3 directory buckets are always copied to every AZ by an implicit CRR rule.
Enable S3 Transfer Acceleration on the directory bucket and assume edge ingress also replicates the objects to other Availability Zones for failover.

Explanation

Correct Answer

The storage class optimizes zonal latency rather than cross-AZ availability.

Incorrect Answers

Its defining placement is zonal.

Replication and placement must not be assumed.

Network transfer optimization does not change S3 Express One Zone AZ-local storage durability. The application must design a distinct recovery path if AZ loss is unacceptable.

Question 477

An FSx for Lustre file system linked to S3 processes data quickly, but analysts incorrectly assume every local edited file was already exported back to the S3 durable repository. Which boundary was missed?

FSx for Lustre file writes are automatically identical to immediate S3 object commits in every configuration.
Treat an FSx for Lustre data repository association as a synchronous write-through cache where every file modification instantly becomes a durable S3 object.
Run an S3 bucket inventory report and assume that listing the old export objects automatically uploads unsent local Lustre modifications.
Data repository associations/export tasks and their completion must be configured and verified; local file writes are not proof S3 copies exist.

Explanation

Correct Answer

Lustre-to-S3 synchronization has explicit supported import/export behavior.

Incorrect Answers

Repository update behavior depends on configured associations and tasks.

Data repository associations and export behavior have documented asynchronous controls; local Lustre writes should not be treated as verified S3 copies without an export completion/validation path.

Inventory reports existing S3 object state, but cannot perform FSx for Lustre file exports. Configure and verify supported repository export activity for changes.

Question 478

A Windows EC2 client has correct Active Directory credentials and a valid UNC path for an Amazon FSx for Windows File Server SMB share, but mounting the share times out. The file system security group denies inbound TCP 445 from that client subnet. What must be repaired?

Permit the required SMB TCP 445 network path between the Windows client and the FSx file-system endpoint, also checking relevant NACL and Windows firewall controls.
Recreate all NTFS ACLs without changing the blocked TCP 445 transport path, assuming filesystem permissions permit a connection even when the network drops it.
Enable EFS NFS port 2049 and assume that it automatically converts the existing FSx SMB share into a reachable NFS mount.
Increase FSx storage capacity and assume additional GiB overrides a denied inbound SMB connection from the client subnet.

Explanation

Correct Answer

An authenticated SMB application still needs network transport to the file server. AWS lists TCP 445 for Windows SMB sharing, so the relevant VPC security group, NACL and client firewalls must permit that path.

Incorrect Answers

NTFS ACLs govern authorized file operations after a client connects. They cannot establish a TCP session across an explicit security-group denial.

NFS and SMB use distinct protocols. Opening NFS on a separate EFS service does not repair TCP 445 access to the configured FSx for Windows share.

Extra FSx disk space cannot open a blocked SMB network session. Diagnose connectivity before capacity or file authorization.

Question 479

An FSx for NetApp ONTAP volume has a tiering policy that moved inactive files into capacity-pool storage. A monthly analytics job now experiences high latency on first reads of its cold input files while its normal SSD workloads remain fast. Which mechanism should be evaluated?

Disable SMB authentication and assume that removing Windows file credentials returns every capacity-pool block to the SSD storage tier.
Increase the volume snapshot retention count and assume more snapshots automatically keep all user-file blocks in the hot SSD tier.
Review the ONTAP tiering and cloud retrieval policies, including promotion or prewarming of cold blocks into SSD when repeat analytics require hot-read performance.
Add an S3 Transfer Acceleration endpoint and assume it bypasses FSx for ONTAP tiered capacity-pool reads for all NFS/SMB file clients.

Explanation

Correct Answer

ONTAP tiering can place cold data in a capacity pool; cloud retrieval settings determine if and when data is promoted to the SSD tier. A planned analytics workload may benefit from a supported promotion policy.

Incorrect Answers

SMB/NFS credentials control access and do not change the physical storage tier that hosts a given file block. Tiered capacity-pool reads can add latency even for authorized users.

Snapshots provide data protection, not a universal promotion of all historical active user blocks to SSD storage. Evaluate the actual tiering policy and retrieval behavior.

S3 Transfer Acceleration is an object-upload route optimization, not a way to accelerate file-protocol reads of FSx capacity-pool blocks. Choose ONTAP policy and workload locality changes instead.

Question 480

An on-premises File Gateway VM is shut down before its dirty cache uploads complete. After restart, some files are missing in S3. What caused the data loss window?

The gateway had acknowledged local cached writes that were not yet uploaded to durable S3 before shutdown.
File Gateway sends every completed SMB write synchronously into every S3 Region before acknowledging it.
Force shutdown the on-premises File Gateway while its CachePercentDirty metric remains high, assuming SMB acknowledgement means all changed blocks are already durable in S3.
Enable S3 versioning on the destination bucket and assume versioning guarantees that dirty gateway cache bytes that never uploaded are recoverable from S3.

Explanation

Correct Answer

File Gateway writes are locally cached and asynchronously uploaded; monitor CachePercentDirty and graceful shutdown.

Incorrect Answers

The local cache/writeback contract is asynchronous.

File Gateway can acknowledge application writes to local cache before asynchronous upload completes. Shutting it down without a clean flush/operational procedure risks leaving undelivered dirty data.

Bucket versioning protects object versions that reached S3, not data still only present in a local gateway cache. Upload completion and safe shutdown procedures remain necessary.

Pass Your Amazon AWS Certified Solutions Architect - Associate SAA-C03 Exam Easy!

Question 470

Explanation

Correct Answer

Incorrect Answers

Question 471

Explanation

Correct Answer

Incorrect Answers

Question 472

Explanation

Correct Answer

Incorrect Answers

Question 473

Explanation

Correct Answer

Incorrect Answers

Question 474

Explanation

Correct Answer

Incorrect Answers

Question 475

Explanation

Correct Answer

Incorrect Answers

Question 476

Explanation

Correct Answer

Incorrect Answers

Question 477

Explanation

Correct Answer

Incorrect Answers

Question 478

Explanation

Correct Answer

Incorrect Answers

Question 479

Explanation

Correct Answer

Incorrect Answers

Question 480

Explanation

Correct Answer

Incorrect Answers

AWS Certified Solutions Architect - Associate SAA-C03 Practice Tests