Tüm alıştırma soruları

1964 soru

Soru 421Soru

A company is designing a deployment strategy for a containerized microservice running on Amazon ECS with AWS Fargate. The infrastructure is managed using AWS CloudFormation. The microservice must meet the following requirements:

* The deployment process must be automated and roll back the service to the previous stable state if the new container version fails to launch or fails container health checks.
* The deployment must not require external deployment tools like AWS CodeDeploy.
* The service must maintain its desired capacity to handle traffic with no reduction in the number of running tasks during the update.
* The deployment must minimize cost by ensuring that no more than 50%50\% additional tasks are running at any point during the rolling update.

Which configuration should the Solutions Architect specify in the CloudFormation template to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Specify the `DeploymentController` type as `ECS` in the `AWS::ECS::Service` resource. Enable the deployment circuit breaker with rollback. Set `MinimumHealthyPercent` to 100%100\% and `MaximumPercent` to 150%150\%.

Cevap

Specify the `DeploymentController` type as `ECS` in the `AWS::ECS::Service` resource, enable the deployment circuit breaker with rollback, and set `MinimumHealthyPercent` to 100%100\% and `MaximumPercent` to 150%150\%.
Specifying the `ECS` deployment controller with `MinimumHealthyPercent` set to 100%100\% and `MaximumPercent` to 150%150\% ensures that the service's capacity is never reduced while limiting the extra tasks to 50%50\%. Enabling the ECS deployment circuit breaker with rollback provides native, automated rollbacks when new container tasks fail to start or pass health checks, without requiring external tools like AWS CodeDeploy.

Adım Adım Çözüm

1
Identify the constraints regarding capacity maintenance and maximum extra container tasks during deployment.
The service must keep 100%100\% of its desired tasks running (`MinimumHealthyPercent` = 100%100\%) and can launch at most 50%50\% additional tasks (`MaximumPercent` = 150%150\%) during updates.
To satisfy the requirement that no capacity reduction occurs while restricting the concurrent tasks to a maximum of 50%50\% above desired capacity.
2
Evaluate the tool and automation constraints for failure detection and rollback.
AWS CodeDeploy cannot be used, and the rollback must happen automatically if container tasks fail to launch or fail health checks.
This eliminates the `CODE_DEPLOY` deployment controller and points to the native ECS deployment controller with deployment circuit breaker rollback enabled.
3
Verify if CloudFormation rollback triggers or ECS deployment circuit breaker is the correct native mechanism for task-level failures.
The ECS deployment circuit breaker is the native feature that monitors task deployment state and triggers rollback if tasks cannot run, whereas CloudFormation rollback triggers do not monitor ECS container startup details.
To select the configuration that achieves automated rollback for task startup failures using native capabilities.

Anahtar Kavram

Amazon ECS rolling update parameters (`MinimumHealthyPercent` and `MaximumPercent`) and the native deployment circuit breaker feature are used in AWS CloudFormation to manage safe, cost-controlled, and automated updates.
Tahmini Süre:1m 30s
Soru 422Soru

A global payment processing company is designing a real-time fraud detection platform. The system must ingest credit card transaction events from merchant terminals worldwide, processing a baseline of 200,000200,000 write requests per second. During promotional sales, traffic instantly surges to 3 million3\text{ million} write requests per second. The application must analyze each transaction against historical user profiles stored in a backend database with sub-1010-millisecond latency. High-volume read queries for these profiles must scale dynamically to handle concurrent validation checks. Which architecture meets these scalability and performance requirements while minimizing operational overhead?

Cevabı ve açıklamayı göster

Cevap: Deploy a Network Load Balancer (NLB) in front of an Amazon ECS Service on AWS Fargate. Store user profiles in an Amazon Aurora PostgreSQL DB cluster, directing write traffic to the primary writer endpoint and read queries to the cluster reader endpoint. Configure Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas based on CPU utilization.

Cevap

Deploy a Network Load Balancer (NLB) in front of an Amazon ECS Service on AWS Fargate. Store user profiles in an Amazon Aurora PostgreSQL DB cluster, directing write traffic to the primary writer endpoint and read queries to the cluster reader endpoint. Configure Aurora Auto Scaling to dynamically adjust the number of Aurora Replicas based on CPU utilization.
The architecture utilizing a Network Load Balancer (NLB) and Amazon Aurora PostgreSQL with reader endpoints and Auto Scaling provides the optimal solution. The NLB natively handles instantaneous, volatile spikes of millions of requests per second without requiring pre-warming. Amazon Aurora's cluster reader endpoint load balances read queries across dynamically scaled Aurora Replicas, which scaling policies can provision automatically in response to CPU load. This ensures the backend meets sub-1010-millisecond latency requirements under heavy write and read pressures.

Adım Adım Çözüm

1
Analyze the ingestion scaling requirements to determine the appropriate load balancer tier.
Identify that the system must handle an instant traffic surge from 200,000200,000 to 3 million3\text{ million} write requests per second.
An Application Load Balancer (ALB) requires pre-warming to handle such rapid, massive spikes, and relying on its default auto-scaling will lead to dropped connections. A Network Load Balancer (NLB) is designed to scale to millions of requests per second instantly without pre-warming.
2
Evaluate the database tier for write performance and dynamic read scaling capabilities.
Select Amazon Aurora PostgreSQL over traditional RDS PostgreSQL.
Amazon Aurora supports up to 1515 Aurora Replicas that can be scaled dynamically using Auto Scaling policies to handle variable read loads, whereas RDS Multi-AZ standby instances are passive and cannot serve read queries.
3
Determine the proper configuration for routing database read and write queries.
Point write queries to the primary instance (writer endpoint) and read validation queries to the reader endpoint.
The reader endpoint automatically load balances connections across the active Aurora Replicas, enabling seamless horizontal scale-out of read queries under load to maintain sub-1010-millisecond latency.

Anahtar Kavram

Handling flash traffic spikes at the ingress layer using NLB, and scaling database reads horizontally using Aurora Auto Scaling and read replicas.
Tahmini Süre:3m 0s
Soru 423Soru

A medical research organization, Aegis Health Group, is designing a secure cross-account data sharing solution. A research application running on Amazon EC2 instances under an IAM role in Account A needs to read sensitive clinical trial datasets stored in an Amazon S3 bucket located in Account B. The S3 bucket is encrypted using a Customer Managed Key (CMK) generated in AWS KMS within Account B. The architecture must enforce the principle of least privilege and comply with healthcare data protection standards. Which combination of configuration steps is required to successfully establish this cross-account access? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: In Account B, configure the S3 bucket policy to grant the IAM role in Account A permissions to perform s3:GetObject on the target S3 bucket objects.; In Account B, update the Customer Managed Key (CMK) key policy to delegate permission to Account A, allowing the IAM role in Account A to perform kms:Decrypt and kms:DescribeKey actions.

Cevap

Configure the S3 bucket policy in Account B to grant access to the IAM role in Account A, and configure the Customer Managed Key (CMK) key policy in Account B to delegate decrypt permissions to the IAM role in Account A.
The correct solution requires configuring the S3 bucket policy in Account B to grant access to the IAM role in Account A, and updating the KMS Customer Managed Key (CMK) key policy in Account B to delegate decrypt permissions to the IAM role in Account A. Together, these steps satisfy the cross-account S3 and KMS requirements.

Adım Adım Çözüm

1
Configure the S3 bucket policy in Account B (the resource owner) to trust and permit the specific IAM role from Account A to execute S3 operations.
The IAM role in Account A passes the first layer of cross-account authorization for S3 access.
For cross-account access, S3 requires authorization from the resource policy (bucket policy) of the owning account.
2
Modify the key policy of the KMS Customer Managed Key (CMK) in Account B to allow the IAM role in Account A to decrypt objects.
The IAM role in Account A passes the KMS decryption authorization layer.
Since the objects are encrypted with a CMK, the caller needs both S3 read permissions and KMS decrypt permissions, both of which must be explicitly allowed by the resource policy of the KMS key.
3
Ensure the IAM role's policy in Account A grants permission to read the S3 bucket and decrypt using the Account B KMS CMK ARN.
The caller has local permission to initiate the API calls to S3 and KMS in Account B.
Cross-account access requires permissions to be granted on both the trust/resource side (Account B) and the identity/caller side (Account A).

Anahtar Kavram

Cross-account resource access with S3 and KMS Customer Managed Keys
Tahmini Süre:2m 0s
Soru 424Soru

A financial technology company is designing a secure compliance monitoring solution for credit card transaction logs. The logs are generated by applications running on Amazon ECS tasks in a Production account (Account 111122223333). These logs must be stored in an Amazon S3 bucket located in a dedicated Compliance account (Account 444455556666). The compliance team requires that:

1. All logs must be encrypted at rest using a customer managed key (CMK) in AWS KMS that the compliance team controls and rotates.
2. Production application tasks must have permission to write logs directly to the S3 bucket and use the KMS key, but must not be able to read or delete any logs once written.
3. The S3 bucket policy must enforce that only encrypted logs are accepted, and all uploaded log objects must be owned by the Compliance account.

Which combination of actions should the solutions architect take to meet these security and compliance requirements? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Create a customer managed KMS key in the Compliance account. Configure the KMS key policy to grant the ECS task role in the Production account permissions to perform kms:GenerateDataKey and kms:Decrypt actions.; In the Compliance account, configure the S3 bucket policy to allow s3:PutObject from the ECS task role in the Production account, and enable S3 Object Ownership with the Bucket Owner Enforced setting on the bucket.

Cevap

Create a customer managed KMS key in the Compliance account with permissions for the Production ECS task role to generate a data key and decrypt, and configure the S3 bucket policy to allow writes while enabling Bucket Owner Enforced for S3 Object Ownership.
To design a secure compliance monitoring solution that meets all requirements, the solutions architect must use a Customer Managed Key (CMK) in the Compliance account and configure its key policy to allow the Production account's ECS task role to perform `kms:GenerateDataKey` and `kms:Decrypt`. AWS-managed keys cannot be shared cross-account. Additionally, S3 Object Ownership must be configured with Bucket Owner Enforced on the S3 bucket to disable ACLs and ensure that all cross-account uploaded objects are automatically owned by the Compliance account. The S3 bucket policy must also explicitly allow the `s3:PutObject` action from the ECS task role.

Adım Adım Çözüm

1
Address the KMS encryption requirement for cross-account access.
Create a Customer Managed Key (CMK) in the Compliance account (destination) and configure its key policy to allow the Production account's ECS task role access to generate data keys and decrypt.
AWS-managed KMS keys cannot be shared cross-account, so a Customer Managed Key is required.
2
Configure S3 Object Ownership to transfer ownership to the Compliance account.
Set S3 Object Ownership to Bucket Owner Enforced on the destination bucket in the Compliance account.
This disables ACLs on the bucket and automatically makes the Compliance account the owner of all uploaded files, avoiding cross-account ownership issues.
3
Allow the ECS task role to write to the S3 bucket.
Add an S3 bucket policy in the Compliance account that grants s3:PutObject permissions to the specific ECS task role ARN from the Production account.
Cross-account access requires explicit permission in both the local IAM policy (sender) and the resource-based bucket policy (receiver).

Anahtar Kavram

Cross-account security controls involving S3 bucket policies, KMS Customer Managed Keys, and S3 Object Ownership configuration.
Soru 425Soru

A logistics company is modernizing its package tracking update microservice by refactoring it to a serverless architecture. The new design uses Amazon API Gateway and AWS Lambda to write tracking updates to a shared Amazon Aurora PostgreSQL database that serves multiple other critical company applications. During load testing, the backend database experiences connection exhaustion, and the API Gateway begins returning 429 Too Many Requests errors because the tracking function consumes the entire regional Lambda execution limit, impacting other serverless applications. Which of the following architectural modifications best resolves both the database connection exhaustion and the regional Lambda execution throttling?

Cevabı ve açıklamayı göster

Cevap: Implement Amazon RDS Proxy between the Lambda function and the Aurora PostgreSQL database, and configure a reserved concurrency limit on the tracking Lambda function.

Cevap

Implement Amazon RDS Proxy between the AWS Lambda function and the Amazon Aurora PostgreSQL database to manage the connection pool, and configure a reserved concurrency limit on the high-volume Lambda function to prevent it from exhausting both database connections and the regional account execution pool.
The correct architecture uses Amazon RDS Proxy to pool database connections, which addresses the connection exhaustion issue on Amazon Aurora PostgreSQL. Additionally, configuring reserved concurrency on the tracking Lambda function sets a hard limit on its concurrent executions. This ensures it does not scale out to consume the entire regional concurrency pool, resolving the throttling issue for other serverless applications in the account.

Adım Adım Çözüm

1
Analyze the requirements and current issues: database connection exhaustion and regional Lambda concurrency throttling.
Identified the need to pool database connections and limit the concurrency of the tracking Lambda function.
This target isolation prevents database resource exhaustion and keeps other regional functions operational.
2
Select a database connection management solution.
Chose Amazon RDS Proxy to intercept and pool database connections.
RDS Proxy scales database connection pools automatically and handles transient Lambda connections efficiently.
3
Select a concurrency management solution for the Lambda function.
Configured Reserved Concurrency on the tracking Lambda function.
Reserved concurrency reserves a portion of the account's pool and acts as a hard limit, preventing the function from taking over the entire regional capacity.

Anahtar Kavram

Using Amazon RDS Proxy for connection pooling and AWS Lambda reserved concurrency to limit scaling limits in serverless architectures.
Tahmini Süre:1m 30s
Soru 426Soru

An organization is designing a high-volume financial transaction platform (OLTP workload). The platform requires a relational database that can support up to 50,000 read requests per second and 10,000 write requests per second. The system must maintain a Recovery Point Objective (RPO) of 0 (no data loss) and a Recovery Time Objective (RTO) of less than 30 seconds during an Availability Zone outage. The database must encrypt all data at rest, and the security team in Account A must centrally manage the encryption keys and audit key usage for database instances deployed in Account B.

Which database and storage configuration meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy an Amazon Aurora PostgreSQL database cluster in Account B with Aurora Replicas. Enable Aurora Auto Scaling for the replicas to handle read scaling. Encrypt the database cluster at rest using an AWS KMS Customer Managed Key (CMK) created in Account A and shared with Account B via key policy.

Cevap

Deploying an Amazon Aurora PostgreSQL database cluster in Account B with Aurora Replicas and scaling them using Aurora Auto Scaling, encrypted with a cross-account Customer Managed Key (CMK) from Account A.
The correct option meets all requirements. Amazon Aurora PostgreSQL supports synchronous replication within its storage volume across multiple Availability Zones, ensuring an RPO of 0. Aurora's failover mechanism promotes a replica to primary in less than 30 seconds, meeting the RTO requirement. Aurora Replicas can serve read queries and support auto-scaling to handle high read volumes. By using an AWS KMS Customer Managed Key (CMK) in Account A, the key policy can be modified to grant the database in Account B permissions to use the key, while keeping key management and auditing under the control of Account A.

Adım Adım Çözüm

1
Evaluate RPO and RTO requirements to select the database architecture.
Amazon Aurora PostgreSQL with Multi-AZ/Aurora Replicas provides synchronous replication within the cluster (RPO = 0) and automated failover in less than 30 seconds (RTO < 30 seconds). A single-AZ RDS instance or manual snapshot restores cannot meet these criteria.
Aurora's storage architecture and replica failover design are built to meet strict RPO and RTO goals.
2
Evaluate read capacity requirements to select the read scaling strategy.
Aurora Replicas can be scaled horizontally (optionally using Auto Scaling) to handle up to 50,000 read requests per second. RDS Multi-AZ standby instances are passive and cannot serve read traffic.
Read scaling must be handled by active replicas, not passive failover standbys.
3
Evaluate security and cross-account key management requirements.
An AWS KMS Customer Managed Key (CMK) created in Account A can be shared with Account B using a key policy, allowing the Account A security team to retain full administrative and audit control. AWS managed keys (like aws/rds) cannot be shared across accounts.
Cross-account resource encryption requires a Customer Managed Key to allow policy modification for cross-account access.

Anahtar Kavram

Designing database and storage solutions to meet replication, scale, and security requirements by choosing between Aurora and RDS, managing read capacity, and implementing cross-account AWS KMS encryption.
Soru 427Soru

CareSync Technologies is deploying a new telemedicine application. The application's core processing engine runs on Amazon ECS in the Application account (Account 111111111111111111111111). The engine must write and read patient record files in an Amazon S3 bucket located in the Data account (Account 222222222222222222222222). To comply with regulatory requirements, all stored data must be encrypted at rest. The security team has established the following constraints:
- All S3 objects must be encrypted using a Customer Managed Key (CMK) stored in Account 222222222222222222222222.
- The ECS tasks in Account 111111111111111111111111 must be able to upload and download objects to and from the S3 bucket.
- Access control lists (ACLs) must be completely disabled on the bucket, and the Data account must automatically own all uploaded objects.

Which combination of configurations will meet these requirements? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Configure the KMS key policy in Account 222222222222222222222222 to grant the ECS task role in Account 111111111111111111111111 permissions for the kms:Decrypt and kms:GenerateDataKey actions.; Configure the S3 bucket policy in Account 222222222222222222222222 to allow the ECS task role in Account 111111111111111111111111 to perform s3:PutObject and s3:GetObject actions, and set the S3 Object Ownership setting on the bucket to Bucket owner enforced.

Cevap

Configure the KMS key policy in the Data account to grant the ECS task role in the Application account permissions for key actions, and configure the S3 bucket policy to allow S3 access while enforcing the Bucket owner enforced Object Ownership setting.
To satisfy all requirements, two conditions must be met: S3 access delegation and KMS key delegation. First, configuring the KMS key policy in the Data account to trust the ECS task role in the Application account for key generation and decryption allows the ECS task to perform server-side encryption with AWS KMS (SSE-KMS) on upload and decryption on download. Second, setting S3 Object Ownership to 'Bucket owner enforced' disables ACLs and makes all uploaded objects owned by the bucket owner, while the S3 bucket policy explicitly allows the application role to upload and download objects.

Adım Adım Çözüm

1
Disable ACLs and enforce bucket owner ownership.
Setting S3 Object Ownership to Bucket owner enforced disables S3 ACLs completely and makes the bucket owner the owner of all uploaded objects.
This satisfies the security requirement to disable ACLs and ensure the Data account owns the data.
2
Enable cross-account S3 permissions.
The S3 bucket policy in the Data account is configured to trust the application's ECS task role for read/write operations.
Because ACLs are disabled, all access control is managed via policies. A cross-account bucket policy is required to allow the Application account to access the bucket.
3
Enable cross-account KMS permissions.
The Customer Managed Key policy in the Data account is updated to grant kms:GenerateDataKey and kms:Decrypt permissions to the ECS task role in the Application account.
Cross-account access to S3 objects encrypted with KMS requires that the external identity has direct permissions on the KMS CMK.

Anahtar Kavram

Cross-account S3 access combined with S3 Object Ownership controls and Customer Managed KMS key delegation.
Soru 428Soru

A financial service provider is designing a new compliance auditing application. The application runs on Amazon EC2 instances inside a private VPC in a Production Account. The application retrieves database credentials from AWS Secrets Manager to decrypt transaction logs. To meet regulatory compliance, the Solutions Architect must implement the following controls:
1. Prevent data exfiltration by ensuring that requests to AWS Secrets Manager from the private VPC can only access Secrets Manager secrets belonging to the company's AWS Organization.
2. Restrict access to the secrets so that only requests originating from the private VPC's endpoint are permitted, blocking any public internet access.
3. Encrypt the secrets at rest using a custom key that allows secure cross-account decryption by auditors in a separate Audit Account.

Which TWO configurations must the Solutions Architect implement to meet these security requirements? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Deploy an interface VPC endpoint for AWS Secrets Manager in the Production VPC, and attach an endpoint policy that allows access only to secrets where the aws:ResourceOrgID condition key matches the company's AWS Organization ID.; Attach a resource-based policy to each Secrets Manager secret that denies all access to the secret if the aws:sourceVpce condition key does not match the ID of the Production VPC endpoint.

Cevap

To meet the security and compliance requirements, the Solutions Architect must deploy an interface VPC endpoint for AWS Secrets Manager in the Production VPC with an endpoint policy that restricts access to the company's AWS Organization using the aws:ResourceOrgID condition key, and attach a resource-based policy to each secret that denies access if the request does not originate from the Production VPC endpoint (using the aws:sourceVpce condition key).
The correct configurations involve using an interface VPC endpoint for AWS Secrets Manager combined with a VPC endpoint policy using the aws:ResourceOrgID condition key to restrict outgoing VPC traffic to the company's AWS Organization, preventing exfiltration to outside accounts. Additionally, attaching a resource-based policy to each secret that denies access when aws:sourceVpce does not match the VPC endpoint ID restricts access exclusively to that private endpoint, blocking external access.

Adım Adım Çözüm

1
Implement data perimeter controls on the VPC endpoint.
An interface VPC endpoint is deployed, and its policy is configured with aws:ResourceOrgID to restrict outbound Secrets Manager requests to the company's organization only.
This prevents data exfiltration by blocking access to secrets hosted in external or personal AWS accounts.
2
Restrict secret access to the VPC endpoint.
A resource-based policy is attached to each secret using a Deny effect with StringNotEquals for aws:sourceVpce pointing to the VPC endpoint.
This ensures that the secrets can only be accessed through the private VPC endpoint, blocking public access.
3
Establish cross-account decryption for auditing.
A Customer Managed Key (CMK) is used to encrypt the secrets, with its key policy configured to delegate decryption permissions to the Audit Account.
AWS-managed keys cannot be shared cross-account or have their policies modified, so a Customer Managed Key is required.

Anahtar Kavram

Data perimeter design using VPC endpoint policies, resource-based policies, and cross-account Customer Managed Key sharing.
Soru 429Soru

A media company is designing a new platform to store user-uploaded video files and track viewing metadata. The platform requires:
- Storage for video files (averaging 20 MB each) with 99.999999999% durability, replicated to a secondary AWS region with an RTO of 10 minutes and an RPO of 1 minute.
- A metadata database that supports millisecond query latency, has a flexible schema, and replicates across regions to support global low-latency reads.
- Data encryption at rest using AWS KMS Customer Managed Keys that can be shared with a centralized auditing account in another AWS account.

Which two database and storage design choices should the solutions architect select to meet these requirements?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Use Amazon S3 with Cross-Region Replication (CRR) configured to replicate video files to the secondary region, encrypting the buckets using Customer Managed KMS Keys (CMKs) in each region.; Use Amazon DynamoDB global tables to store viewing metadata, enabling replication across the primary and secondary regions to provide active-active reads and schema flexibility.

Cevap

The correct choices are using Amazon S3 with Cross-Region Replication and Customer Managed KMS Keys for video storage, and using Amazon DynamoDB global tables for viewing metadata.
The correct choices are using Amazon S3 with Cross-Region Replication and Customer Managed KMS Keys for video storage, and using Amazon DynamoDB global tables for viewing metadata. S3 provides high durability and CRR supports cross-region replication with low RTO/RPO. Using Customer Managed Keys allows modifying the key policy for cross-account access. DynamoDB global tables provide a schema-flexible, low-latency, multi-region metadata store that scales horizontally.

Adım Adım Çözüm

1
Analyze storage requirements for video files and metadata.
Identify that video files require durable object storage (Amazon S3) with replication, and metadata requires low latency, schema flexibility (DynamoDB).
To choose appropriate storage and database services that match the workload characteristics.
2
Evaluate disaster recovery (RTO/RPO) and security (cross-account encryption) constraints.
Determine that Customer Managed KMS Keys are needed for cross-account sharing, and active-active replica configurations like DynamoDB global tables and S3 CRR are needed for meeting RTO/RPO.
To filter out options using AWS-managed KMS keys (which can't be shared cross-account) or pilot light/offline recovery strategies (which fail RTO/RPO).

Anahtar Kavram

Selecting appropriate database and storage services based on workload patterns, performance, high availability, and cross-account encryption requirements.
Soru 430Soru

A solutions architect is planning a heterogeneous database migration from an on-premises Microsoft SQL Server database to an Amazon Aurora PostgreSQL DB cluster. The migration strategy must minimize downtime by using continuous replication. Which of the following actions must the solutions architect perform to successfully convert the schema and support continuous replication? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Use the AWS Schema Conversion Tool (SCT) to convert the source database schema and database code objects to PostgreSQL-compatible formats.; Enable Microsoft Change Data Capture (MS-CDC) on the source SQL Server database and tables to allow AWS Database Migration Service (DMS) to capture ongoing changes.

Cevap

To perform a successful migration, the solutions architect must use the AWS Schema Conversion Tool to convert the source database schema and enable Microsoft Change Data Capture on the source SQL Server database.
The correct options properly address both parts of the requirement: using AWS Schema Conversion Tool (SCT) to translate the schema for a heterogeneous database engine target, and enabling MS-CDC on the source SQL Server database to support continuous replication during the database migration.

Adım Adım Çözüm

1
Analyze schema compatibility and perform conversion.
Convert the SQL Server source schema to Aurora PostgreSQL using the AWS Schema Conversion Tool (SCT).
Heterogeneous database migrations require schema translation since SQL Server and PostgreSQL use different SQL dialects and features.
2
Configure the source database for replication.
Enable Microsoft Change Data Capture (MS-CDC) on the source SQL Server database.
AWS Database Migration Service (DMS) needs MS-CDC enabled on the source SQL Server database to identify and replicate transactional changes during the Change Data Capture (CDC) phase.

Anahtar Kavram

Heterogeneous database migrations with AWS DMS and SCT require schema conversion first, followed by configuring proper source database logging to allow continuous replication (CDC).
Soru 431Soru

A company is implementing federated access to multiple AWS accounts within an AWS Organization using a third-party SAML 2.0 compliant corporate Identity Provider (IdP). Employees must be able to log in to the AWS Management Console using their corporate credentials and assume specific roles based on their Active Directory group memberships. Which of the following configurations are required to establish this federation and trust relationship? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Create an IAM SAML identity provider in each target AWS account using the metadata document from the corporate Identity Provider, and create IAM roles with a trust policy that allows the sts:AssumeRoleWithSAML action.; Configure the corporate Identity Provider to include attributes in the SAML assertion that map the user to the target IAM role ARN and the SAML provider ARN.

Cevap

The configurations required are creating an IAM SAML identity provider in each target account with a trust policy allowing the sts:AssumeRoleWithSAML action, and configuring the corporate IdP to send SAML assertions mapping the user to the target IAM role ARN and SAML provider ARN.
Establishing SAML 2.0 federation requires the creation of an IAM identity provider entity in target accounts linked with the IdP's metadata document. Additionally, roles must be defined with trust policies that allow the sts:AssumeRoleWithSAML action. Simultaneously, the corporate IdP must be configured to pass the appropriate SAML attributes (specifically mapped IAM role and SAML provider ARNs) inside the assertion for AWS to complete the sign-in sequence.

Adım Adım Çözüm

1
Generate and export the SAML metadata document from the corporate Identity Provider (IdP).
An XML file containing the cryptographic keys and endpoints for the IdP.
This metadata is necessary to establish the cryptographic trust relationship in AWS.
2
Create an IAM SAML Identity Provider in each target AWS account using the metadata XML, and define target IAM roles with trust policies specifying the sts:AssumeRoleWithSAML action.
Target IAM roles are configured to trust assertions from the corporate IdP.
This allows the sts:AssumeRoleWithSAML action to be invoked when a valid SAML assertion is presented.
3
Configure claims and attribute mappings in the corporate IdP to output the Role and RoleSessionName attributes in the SAML assertion.
SAML assertions carry the required AWS attributes mapping to the target IAM role and provider ARNs.
AWS uses these specific attributes to identify which role the federated user is authorized to assume.

Anahtar Kavram

Establishment of SAML 2.0 federation in a multi-account environment requires both an IAM SAML provider with a matching trust policy in target accounts and proper attribute configuration in the corporate IdP.
Soru 432Soru

A company is configuring federated single sign-on (SSO) to multiple target AWS accounts using an on-premises SAML 2.0 Identity Provider (IdP). To enable corporate users to authenticate and access the target accounts, an administrator must create IAM roles in each target account. Which action must be included in the trust policy of these IAM roles to allow users to assume them via the SAML Identity Provider?

Cevabı ve açıklamayı göster

Cevap: Specify the sts:AssumeRoleWithSAML action, listing the SAML provider as the trusted principal.

Cevap

Specify the sts:AssumeRoleWithSAML action, listing the SAML provider as the trusted principal.
For SAML 2.0 federation, target IAM roles require a trust policy that permits the Security Token Service (STS) action sts:AssumeRoleWithSAML. The trust policy must specify the SAML Identity Provider as the principal to allow users authenticated by the IdP to obtain temporary AWS security credentials.

Adım Adım Çözüm

1
Identify the authentication protocol used by the corporate Identity Provider.
The company is using SAML 2.0.
This determines which Security Token Service (STS) assume role action is appropriate.
2
Select the correct STS API action for SAML 2.0 federation.
The correct action is sts:AssumeRoleWithSAML.
This API operation returns a set of temporary security credentials for users authenticated by a SAML provider.
3
Configure the trust relationship policy document for the IAM role.
The IAM role trust policy is configured with sts:AssumeRoleWithSAML as the action and the SAML provider's ARN as the Principal.
This allows the SAML Identity Provider to trust and assume the IAM role.

Anahtar Kavram

SAML 2.0 Federation Trust Policy Action
Soru 433Soru

A software development company is setting up federated access for its development teams to access multiple AWS accounts within an AWS Organization. The developer identities are managed in an external OpenID Connect (OIDC) compliant identity provider. A Solutions Architect registers the OIDC provider as an IAM Identity Provider in each target member account and creates an IAM role named DeveloperRole in those accounts with appropriate permissions. However, when developers attempt to authenticate using the OIDC provider and assume the DeveloperRole, the requests fail. Upon reviewing the configurations, the architect finds that the IAM roles cannot be assumed via OIDC. Which of the following is the most likely configuration error causing this issue?

Cevabı ve açıklamayı göster

Cevap: The trust policy of DeveloperRole in the member accounts specifies the sts:AssumeRole action instead of the sts:AssumeRoleWithWebIdentity action.

Cevap

The trust policy of DeveloperRole in the member accounts specifies the sts:AssumeRole action instead of the sts:AssumeRoleWithWebIdentity action.
The correct answer states that the trust policy of DeveloperRole in the member accounts specifies the sts:AssumeRole action instead of the sts:AssumeRoleWithWebIdentity action. To assume a role using OpenID Connect (OIDC) web identity tokens, the target role's trust policy must trust the registered OIDC provider ARN under the Federated principal and allow the sts:AssumeRoleWithWebIdentity action. Using sts:AssumeRole will fail because it expects AWS security credentials, which federated developers do not possess during the initial token exchange.

Adım Adım Çözüm

1
Analyze the authentication flow for federating external OpenID Connect (OIDC) identities into target AWS accounts.
Identified that developers use an external OIDC provider and need to assume DeveloperRole in target member accounts via OIDC tokens.
Understanding the entry point of federation helps isolate whether AWS STS expects a SAML assertion, an OIDC token, or standard AWS credentials.
2
Verify the STS action required in the trust policy for OIDC-based federation.
OIDC federation requires the sts:AssumeRoleWithWebIdentity action in the trust policy of the target role.
The standard sts:AssumeRole action is reserved for cross-account or service-based role assumption using AWS credentials, whereas OIDC tokens require sts:AssumeRoleWithWebIdentity.
3
Examine the role trust policy's Principal configuration for OIDC identity provider integration.
The trust policy must declare the federated OIDC provider's ARN under the Principal's Federated key.
Using an incorrect principal configuration (such as an AWS service principal or missing the Federated key) breaks the trust chain between AWS STS and the OIDC IdP.

Anahtar Kavram

To establish federation with an external OpenID Connect (OIDC) identity provider, target IAM roles must have a trust policy that permits the sts:AssumeRoleWithWebIdentity action and references the OIDC provider ARN under the Federated principal.
Tahmini Süre:1m 30s
Soru 434Soru

An enterprise is implementing a multi-account strategy using AWS Organizations. The security team has attached a Service Control Policy (SCP) to a production Organizational Unit (OU) that explicitly denies the s3:DeleteBucket action. A developer operating within a member account under this OU has been assigned an IAM policy granting administrator access (*:*), but finds they are blocked from deleting any S3 buckets in their account. Which of the following statements correctly explains why the developer cannot delete S3 buckets?

Cevabı ve açıklamayı göster

Cevap: The Service Control Policy (SCP) acts as a guardrail that restricts the maximum allowed permissions, and an explicit deny in the SCP overrides any permissions granted by the local IAM policy.

Cevap

The Service Control Policy (SCP) acts as a guardrail that restricts the maximum allowed permissions, and an explicit deny in the SCP overrides any permissions granted by the local IAM policy.
The correct option correctly states that Service Control Policies (SCPs) act as guardrails defining the maximum allowed permissions for member accounts. Under the AWS policy evaluation logic, an explicit deny in an SCP overrides any allow permissions defined in local IAM policies.

Adım Adım Çözüm

1
Evaluate the role of the Service Control Policy (SCP) in AWS Organizations.
The SCP is attached to the Organizational Unit (OU) containing the member accounts.
SCPs define the permission boundaries (maximum permissions) for all accounts within the scope of the OU.
2
Analyze how SCPs interact with local IAM policies.
An explicit deny in an SCP overrides any allow permission granted in a local identity-based or resource-based IAM policy.
AWS evaluation logic dictates that a request is denied if any applicable policy contains an explicit Deny, regardless of any Allow statements.

Anahtar Kavram

Service Control Policies (SCPs) act as permission filters (guardrails) and do not grant permissions directly. An explicit deny in an SCP overrides any local IAM permissions.
Tahmini Süre:45s
Soru 435Soru

A financial services company is establishing a multi-account, multi-region AWS environment. In the primary Region (`us-east-1`), they have deployed a central AWS Transit Gateway (TGW) to interconnect 1515 spoke VPCs. To connect their main on-premises data center to AWS, they deploy a 10 Gbps10\text{ Gbps} AWS Direct Connect (DX) connection terminating at a Direct Connect Gateway (DXGW) associated with the TGW. For high availability, they also configure an IPsec AWS Site-to-Site VPN terminating directly on the same TGW as a backup. The network team requires symmetric routing: all traffic between AWS and the on-premises data center must utilize the DX connection during normal operation, failing over to the VPN only if the DX link becomes unavailable. The on-premises network uses the prefix 10.0.0.0/810.0.0.0/8, which must be reachable from AWS, and on-premises systems must reach resources in the AWS VPCs. The solution must minimize administrative overhead and rely on dynamic routing protocols where possible. Which TWO configurations will achieve this routing policy while preventing asymmetric traffic flows? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Configure the customer gateway (CGW) to advertise the 10.0.0.0/810.0.0.0/8 prefix over the Direct Connect connection, and advertise the same 10.0.0.0/810.0.0.0/8 prefix over the Site-to-Site VPN connection with its own Autonomous System Number (ASN) prepended at least three times in the AS-Path.; Configure the CGW to assign a higher BGP Local Preference value to AWS prefixes received over the Direct Connect connection than to those received over the Site-to-Site VPN connection.

Cevap

Configure the customer gateway (CGW) to prepend its own ASN at least three times when advertising the prefix over the Site-to-Site VPN, and assign a higher BGP Local Preference value to AWS prefixes received over the Direct Connect connection compared to the VPN on the CGW.
To achieve symmetric routing, both paths must prefer the Direct Connect connection under normal conditions. AWS Transit Gateway evaluates the AS-Path length for BGP advertised prefixes. By prepending the customer gateway's ASN multiple times on the VPN connection, AWS Transit Gateway will see a longer AS-Path and select the Direct Connect path as the active route. For return traffic, configuring the customer gateway to assign a higher BGP Local Preference value to prefixes received via Direct Connect ensures that traffic originating from the on-premises network to AWS exits via the Direct Connect connection.

Adım Adım Çözüm

1
Determine how to influence outbound traffic from AWS to the on-premises network.
Evaluate AWS Transit Gateway's path selection process: Transit Gateway evaluates AS-Path length first when comparing identical prefixes.
To ensure Direct Connect is preferred, the Site-to-Site VPN path must be configured with a longer AS-Path using AS-Path prepending on the customer gateway.
2
Determine how to influence inbound traffic from the on-premises network to AWS.
Identify that the customer gateway will receive identical AWS VPC prefixes from both the Direct Connect connection and the VPN connection.
Since the local router decides how to reach AWS, BGP attributes must be tuned on the on-premises side.
3
Apply BGP Local Preference on the customer gateway.
Configure a higher Local Preference (e.g., 200200) for prefixes received over Direct Connect compared to those received over VPN (e.g., 100100).
In BGP path selection, Local Preference is the highest-priority attribute processed locally within an AS, ensuring that all outbound traffic to AWS exits via the Direct Connect connection.

Anahtar Kavram

Ensuring symmetric routing in hybrid network environments with AWS Transit Gateway, Direct Connect, and VPN backup using BGP path attributes.
Tahmini Süre:3m 0s
Soru 436Soru

An enterprise is migrating its workforce identity management to a centralized model and needs to establish single sign-on (SSO) access for internal engineers. The engineers must be able to log into multiple AWS member accounts within their AWS Organization using their existing Active Directory credentials via a SAML 2.0 compliant Identity Provider (IdP). Which of the following configuration steps are required in the target member accounts to enable this federation? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Create an IAM SAML identity provider in each target account using the SAML metadata document from the enterprise Identity Provider.; Create an IAM role in each target account with a trust policy that permits the AssumeRoleWithSAML action from the local SAML identity provider principal.

Cevap

To configure federated access using an external SAML Identity Provider (IdP) in a multi-account environment, the Solutions Architect must create an IAM SAML identity provider in each target member account using the IdP's metadata document. Additionally, an IAM role must be created in each target member account with a trust policy that references the SAML identity provider as the principal and allows the AssumeRoleWithSAML action.
Establishing federated access via a SAML 2.0 Identity Provider requires two core configuration steps in each target account. First, the SAML provider metadata must be imported into the account to define the trust anchor (the IAM SAML identity provider). Second, a target role must be created with a trust policy that allows the AssumeRoleWithSAML action, which permits users authenticated by the SAML IdP to assume the role and receive AWS credentials.

Adım Adım Çözüm

1
Configure the IAM SAML Identity Provider
An IAM SAML identity provider is registered in each target AWS member account using the corporate IdP's XML metadata document.
This establishes a cryptographically verified trust relationship between the specific AWS account and the external SAML IdP.
2
Configure IAM Roles with federated trust policies
IAM roles are created in each target account with a trust policy allowing the AssumeRoleWithSAML action.
The trust policy permits the external SAML provider to invoke the AssumeRoleWithSAML API, enabling authenticated users to obtain temporary security credentials.

Anahtar Kavram

Establishing SAML 2.0 identity federation requires registering an IAM SAML identity provider in target accounts and configuring an IAM role with a trust policy allowing the AssumeRoleWithSAML action.
Soru 437Soru

A retail company is migrating to a multi-account AWS environment managed by AWS Organizations. The company wants to federate its on-premises Active Directory using a SAML 2.0 compliant Identity Provider (IdP) to allow administrators to access the AWS Management Console. The administrators must be able to assume a target role named SysAdminRole in various member accounts. Which of the following actions must the solutions architect take to configure the trust relationship for the federated role?

Cevabı ve açıklamayı göster

Cevap: Create an IAM SAML provider in each target member account, and configure the trust policy of the SysAdminRole to allow the sts:AssumeRoleWithSAML action with the SAML provider as the principal.

Cevap

Create an IAM SAML provider in each target member account, and configure the trust policy of the SysAdminRole to allow the sts:AssumeRoleWithSAML action with the SAML provider as the principal.
To set up SAML 2.0-based federation to multiple member accounts, an IAM SAML provider must be created in each target account. The target IAM role in those accounts must contain a trust policy that allows the `sts:AssumeRoleWithSAML` action, targeting the local SAML provider as the trusted principal. This enables the Identity Provider to redirect users with a signed SAML assertion that AWS STS can verify to generate temporary console access credentials.

Adım Adım Çözüm

1
Download the SAML metadata document from the on-premises Identity Provider (IdP).
Obtained the XML metadata document required to establish trust.
This document contains the signing certificates and endpoints used by the IdP.
2
Create an IAM SAML identity provider in each target AWS member account using the IdP metadata document.
An IAM SAML provider resource is established in each target account.
Each member account must have a local configuration of the trusted IdP to resolve the federation request.
3
Create the SysAdminRole in each target member account with a trust policy that permits the sts:AssumeRoleWithSAML action, referencing the IAM SAML provider ARN as the principal.
The federated role is configured with the correct trust relationships.
This allows AWS Security Token Service (STS) to authenticate SAML assertions and issue temporary credentials to users.

Anahtar Kavram

SAML 2.0 Federation in Multi-Account Architectures
Tahmini Süre:2m 0s
Soru 438Soru

An enterprise manages its multi-account environment using AWS Organizations. The cloud architecture team is implementing a centralized networking and cost management strategy with the following requirements:
- A Transit Gateway created in a dedicated Network account must be shared with all member accounts in the organization to enable hybrid connectivity. The sharing process must be automated, avoiding manual resource share invitations.
- The company has purchased Savings Plans to lower costs for its workloads running on AWS Fargate and AWS Lambda.
- The discounts from these Savings Plans must be prioritized for production accounts, meaning dev/test accounts must be excluded from automatically absorbing these discounts.

Which TWO actions should the solutions architect take to meet these requirements?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: In the AWS Resource Access Manager (RAM) console of the organization's management account, enable resource sharing with AWS Organizations. In the Network account, create a resource share for the Transit Gateway and share it with the target organizational units (OUs).; In the AWS Billing console of the management account, access the Billing Preferences and disable Savings Plans discount sharing for the specific dev/test member accounts.

Cevap

To meet the requirements, the solutions architect must enable resource sharing with AWS Organizations in the AWS RAM console of the management account, create a resource share for the Transit Gateway in the Network account targeting the organizational units, and disable Savings Plans discount sharing for the dev/test member accounts in the Billing Preferences of the management account.
The correct strategy requires enabling resource sharing with AWS Organizations in AWS RAM to allow seamless cross-account resource sharing without manual invitations, and sharing the Transit Gateway with the organizational units. Additionally, the solutions architect must disable Savings Plans discount sharing for dev/test accounts in the Billing Preferences of the management account to ensure the production accounts prioritize using the Compute Savings Plans discounts.

Adım Adım Çözüm

1
Configure AWS RAM for organization-wide sharing.
Resource sharing with AWS Organizations is enabled in the management account, allowing seamless sharing without invitations.
This automates the process and avoids manual acceptance steps for member accounts.
2
Share the Transit Gateway from the Network account.
The Transit Gateway is shared with the target OUs.
This grants the member accounts access to attach their VPCs to the central Transit Gateway.
3
Configure billing preferences for Savings Plans.
Savings Plans discount sharing is turned off for the dev/test accounts.
This prevents dev/test accounts from absorbing the Compute Savings Plans benefits, prioritizing them for production workloads.

Anahtar Kavram

AWS Organizations resource sharing using AWS RAM and consolidated billing preferences management for Savings Plans.
Soru 439Soru

A company is setting up federated single sign-on (SSO) using a SAML 2.0 compliant corporate identity provider (IdP). They have already created the SAML identity provider entity in AWS IAM. To allow corporate users to federate into the AWS account, they need to create an IAM role. What must be configured in the trust policy of this IAM role to allow successful federation?

Cevabı ve açıklamayı göster

Cevap: Specify the SAML identity provider as the principal and allow the sts:AssumeRoleWithSAML action.

Cevap

Specify the SAML identity provider as the principal and allow the sts:AssumeRoleWithSAML action.
The correct answer specifies mapping the SAML identity provider as the principal and allowing the sts:AssumeRoleWithSAML action because the AWS Security Token Service (STS) requires this specific API action to handle assertions generated by a SAML 2.0-compliant Identity Provider (IdP).

Adım Adım Çözüm

1
Identify the type of federation required.
The scenario specifies SAML 2.0 compliant corporate identity provider (IdP) federation.
This determines which security token service (STS) API action must be allowed.
2
Determine the correct STS API action for SAML 2.0.
The correct action is sts:AssumeRoleWithSAML.
SAML assertion exchanges require the specific WithSAML variation of the assume role API.
3
Determine the required trust policy components.
The Principal must target the ARN of the IAM SAML Identity Provider entity, and the Action must be sts:AssumeRoleWithSAML.
An IAM role must explicitly define who (the Principal) is trusted to assume it and under what action.

Anahtar Kavram

SAML 2.0 Identity Federation Trust Relationships
Tahmini Süre:45s
Soru 440Soru

A global energy enterprise is migrating its smart grid monitoring system to a multi-account AWS environment managed under AWS Organizations. The architecture consists of a central Shared Services VPC (10.10.0.0/16) connected to an on-premises datacenter (172.16.0.0/12) via AWS Direct Connect and AWS Transit Gateway. Multiple spoke VPCs in production accounts (using the range 10.50.0.0/16) are attached to the same Transit Gateway. A Route 53 Private Hosted Zone (PHZ) for grid.internal is created in the Shared Services account. The on-premises DNS servers (172.16.1.10 and 172.16.1.11) host the zone corp.internal. Spoke VPC instances must resolve domains in both grid.internal and corp.internal, and on-premises hosts must resolve domains in grid.internal. Which combination of actions should the Solutions Architect take to implement this DNS architecture? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: In the Shared Services account, authorize the association of the grid.internal private hosted zone with each spoke VPC. In each production account, accept the association using the AWS CLI or Route 53 API to link the spoke VPCs to the private hosted zone.; In the Shared Services account, create a Route 53 Resolver Outbound Endpoint in the central VPC, and create a forwarding rule for corp.internal pointing to the on-premises DNS servers. Share this rule with the production accounts using AWS Resource Access Manager (RAM), and associate it with the spoke VPCs.

Cevap

The correct architecture requires authorizing the cross-account association of the private hosted zone with the spoke VPCs using the Route 53 API, and sharing a centralized Route 53 Resolver Outbound Endpoint forwarding rule using AWS Resource Access Manager (RAM).
To establish hybrid DNS resolution, a combination of cross-account Private Hosted Zone (PHZ) association and shared Route 53 Resolver rules is required. The option to authorize the association of the grid.internal PHZ with each spoke VPC followed by accepting the association in the production accounts correctly handles name resolution for the AWS-hosted zone. Additionally, the option to create a Route 53 Resolver Outbound Endpoint in the central VPC, create a forwarding rule for corp.internal, and share it with production accounts using AWS RAM provides a cost-effective and scalable mechanism for spoke VPCs to resolve on-premises domain names.

Adım Adım Çözüm

1
Authorize the association of the grid.internal Private Hosted Zone (PHZ) in the Shared Services account with the spoke VPCs in the production accounts.
The spoke VPCs are permitted to link to the PHZ managed in the Shared Services account.
Route 53 Private Hosted Zones cannot be shared directly via AWS Resource Access Manager (RAM). Cross-account VPC association requires an explicit authorization step from the zone owner.
2
Accept the association in each production account for their respective spoke VPCs using the Route 53 API or CLI.
Spoke VPCs can now resolve grid.internal domains directly using the Route 53 Resolver.
The association must be accepted from the target account's context to complete the relationship.
3
Create a Route 53 Resolver Outbound Endpoint in the Shared Services VPC and configure a forwarding rule for corp.internal pointing to the on-premises DNS IPs.
A centralized mechanism is established to route queries for corp.internal to the on-premises environment.
This centralizes outbound DNS resolution and avoids the cost of deploying outbound endpoints in every individual spoke VPC.
4
Share the Route 53 Resolver forwarding rule via AWS Resource Access Manager (RAM) to the production accounts and associate the rule with the spoke VPCs.
Spoke VPCs can now resolve corp.internal domains by forwarding queries through the shared outbound endpoint in the Shared Services VPC.
Sharing rules via RAM allows spoke VPCs to utilize the central outbound resolver endpoints transitively over the Transit Gateway.

Anahtar Kavram

Hybrid and multi-account DNS integration utilizing Route 53 Resolver endpoints, cross-account Private Hosted Zone association, and AWS Resource Access Manager (RAM) rule sharing.
ÖncekiSayfa 22 / 99Sonraki
Tüm alıştırma soruları — AWS Certified Solutions Architect - Professional | Examkin