Free AWS-CERTIFIED-SOLUTIONS-ARCHITECT-PROFESSIONAL-SAP-C02 – Amazon AWS-CERTIFIED-SOLUTIONS-ARCHITECT-PROFESSIONAL-SAP-C02 Practice Test Question

Reference / correct answer:

Most accepted answer: C. Install the AWS DataSync agent as a VM that runs on the on-premises hypervisor. Configure a DataSync task to replicate the data to Amazon S3 daily.

Community votes: B=2, C=8

Selected Answer: C Because of: The company needs a solution that applies custom filters to back up only a subset of the data that is located in designated source directories. upvoted 14 times PAUGURU 2 years, 8 months ago The only problem with C is that a data sync is not a backup. If you delete a file, the sync will delete the file on AWS, but with backups you can restore it from yesterday's backup. So I think it's B. upvoted 2 times vibzr2023 2 years, 6 months ago I agree AWS DataSync is not a dedicated backup solution but it can be used for data replication that serves as a backup, it's essential to understand its limitations and distinctions compared to a comprehensive backup service: When to Use DataSync for Backup-Like Purposes: Initial Data Transfer: It's efficient for bulk migration of large datasets to AWS storage services. Incremental Updates: It excels at replicating ongoing changes to keep a copy of data in AWS, serving as a near-real-time backup. Cost-Effective Replication: It's often more cost-effective than traditional backup tools for ongoing data replication, especially for large datasets. upvoted 2 times ... ...

The only problem with C is that a data sync is not a backup. If you delete a file, the sync will delete the file on AWS, but with backups you can restore it from yesterday's backup. So I think it's B. upvoted 2 times vibzr2023 2 years, 6 months ago I agree AWS DataSync is not a dedicated backup solution but it can be used for data replication that serves as a backup, it's essential to understand its limitations and distinctions compared to a comprehensive backup service: When to Use DataSync for Backup-Like Purposes: Initial Data Transfer: It's efficient for bulk migration of large datasets to AWS storage services. Incremental Updates: It excels at replicating ongoing changes to keep a copy of data in AWS, serving as a near-real-time backup. Cost-Effective Replication: It's often more cost-effective than traditional backup tools for ongoing data replication, especially for large datasets. upvoted 2 times ...

I agree AWS DataSync is not a dedicated backup solution but it can be used for data replication that serves as a backup, it's essential to understand its limitations and distinctions compared to a comprehensive backup service: When to Use DataSync for Backup-Like Purposes: Initial Data Transfer: It's efficient for bulk migration of large datasets to AWS storage services. Incremental Updates: It excels at replicating ongoing changes to keep a copy of data in AWS, serving as a near-real-time backup. Cost-Effective Replication: It's often more cost-effective than traditional backup tools for ongoing data replication, especially for large datasets. upvoted 2 times

Selected Answer: C For me there are two cues: 1- "custom filters" which are available in Datasync 2- AWS Backup does not back up to S3, rather to a Storage Vault. upvoted 6 times

Selected Answer: C Automatización: DataSync permite programar tareas periódicas, como respaldos diarios. Filtros personalizados: Puedes configurar filtros para incluir solo ciertos archivos o directorios específicos. Compatibilidad: DataSync está diseñado para grandes cantidades de archivos (como 1 millón de archivos .csv). Rendimiento: Se integra con Direct Connect, aprovechando la conexión de alta capacidad. Bajo overhead operativo: Solo debes instalar un agente una vez y definir tareas desde la consola de AWS. Es administrado completamente por AWS. upvoted 1 times

Reference / correct answer:

Most accepted answer: A. Create an organization in AWS Organizations. Set up AWS Control Tower, and turn on the strongly recommended controls (guardrails). Join all accounts to the organization. Categorize the AWS accounts into OUs.

Community votes: A=11, C=10, D=1, E=2

Selected Answer: AC A: strongly recommended controls - detects whether the Amazon EBS volumes attached to an Amazon EC2 instance are encrypted C: Best way to encrypt an unencrypted volume upvoted 6 times

Selected Answer: AC the appropriate guardrail is: A Strongly recommended guardrail: Detect Whether Encryption is Enabled for Amazon EBS Volumes Attached to Amazon EC2 Instances. This guardrail continuously monitors your environment and detects any EC2 instances with unencrypted EBS volumes attached upvoted 5 times

Selected Answer: CD n AWS Control Tower, the mandatory guardrails are the baseline for security and compliance. The question emphasizes compliance and security, so the exam expects mandatory guardrails, not just strongly recommended ones. upvoted 1 times

Option A is correct because setting up an organization with AWS Control Tower will help centrally manage multiple AWS accounts and ensure compliance and security. Joining all accounts to the organization ensures that encryption is enforced across all accounts. Option C is also correct because creating snapshots of each unencrypted volume, encrypting them, and replacing the original volumes with encrypted ones is a more efficient and automated way to handle the encryption. upvoted 1 times

Selected Answer: AC A and C are correct according to https://docs.aws.amazon.com/controltower/latest/userguide/strongly-recommended-controls.html#ebs-enable-encryption upvoted 2 times

Reference / correct answer:

Most accepted answer: A. Convert the API Gateway Regional endpoint to an edge-optimized endpoint. Enable caching in the production stage.

Community votes: A=8, B=6, D=1

Selected Answer: A Option A because B is more expensive than A upvoted 12 times

Option A is correct While A and B do the job but the question says "minimizing the increase in costs associated with the solution".. I'll go with A coz Edge-optimized endpoints cache responses at edge locations closer to users, significantly reducing the number of requests reaching the database and Lambda functions.. While Option B -- While ElastiCache for Redis a good caching solution, it adds complexity and cost compared to edge caching. upvoted 11 times

Selected Answer: A Why not the others: B (ElastiCache Redis): Works, but adds always-on infrastructure, capacity planning, and operational overhead/cost. Not “minimizing cost increase” for a serverless stack. C (increase Aurora max memory): Treats the symptom by scaling up DB capacity, usually higher cost and doesn’t reduce duplicated work. D (throttling): Prevents overload by rejecting requests (429s). That harms partners/users and doesn’t “support additional usage.” upvoted 1 times

Selected Answer: A A is right, it's much cheaper to cache the GET endpoints at the edge location. Creating a redis ElastiCache cluster might prove much more expensive, don't forget about the transfer costs of data from the edge location to the cluster. It will be FAR more expensive. Lastly, caching in the edge WILL reduce database reads, as there wouldn't be as many requests to the database, because the cache is at the endpoint. upvoted 2 times

Selected Answer: B B. Use ElastiCache (Redis) as a caching layer ElastiCache for Redis provides a high-performance, in-memory cache that can handle frequent identical queries without hitting the database. Caching reduces database calls, which avoids memory errors and reduces Aurora Serverless compute scaling, thereby minimizing cost. Lambda functions can easily be updated to check Redis before querying the database. Ideal for read-heavy workloads with repeated identical queries, which is exactly the case here. upvoted 2 times