Q90. Which of these AWS services can be related to Lambda via a trigger?
l Cognito Sync Trigger, SNS
l SNS, SQS
l all of these answers
l SQS, DynamoDB
Q91. When creating a RESTful API into a DynamoDB table, which is the right service to facilitate this?
l API Sync
l AppSync
l CloudAPI
l API Gateway
ChatGPT also says ..
The right service to facilitate the creation of a RESTful API into a DynamoDB table in the AWS ecosystem is "API Gateway."
Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs. You can use API Gateway to create RESTful APIs that can integrate with various AWS services, including DynamoDB, and also external services. It provides features for request and response transformation, authentication, authorization, and rate limiting, making it a powerful tool for building RESTful APIs that interact with DynamoDB or other AWS resources.
The other options you mentioned, such as "API Sync," "AppSync," and "CloudAPI," are not standard AWS services for creating RESTful APIs into DynamoDB, and they may not be recognized services as of my last knowledge update in September 2021. However, AWS services and offerings can change over time, so it's a good practice to check the latest AWS documentation and services to ensure you are using the most up-to-date and appropriate tools for your specific use case.
Q92. Which AWS service is valid data source for AppSync?
l DynamoDB table
l ElastiCache
l none of these answers
l Step Functions
ChatGPT also adds ..
AWS AppSync allows you to connect to different data sources to provide the necessary backend data for your GraphQL APIs. DynamoDB is one of the supported data sources that can be integrated with AppSync to perform CRUD (Create, Read, Update, Delete) operations, making it an efficient way to retrieve and manipulate data through your GraphQL API.
ElastiCache and Step Functions are not natively supported data sources for AWS AppSync. ElastiCache is an in-memory data store and cache, while Step Functions is a serverless function orchestrator to coordinate multiple AWS services into serverless workflows, neither of which are directly integrated as data sources for AWS AppSync.
Q93. If a single instance has failed to launch within 24 hours due to some issues during a set up of Auto-scaling.
Then what will happen to the Auto-Scaling condition?
l Auto Scaling will continue to launch the instance for straight 3 days
l The Auto Scaling group will be automatically terminated.
l In a separate region Auto Scaling will start an instance
l Auto Scaling will remove the scaling process
ChatGPT states completely opposite opinion ..
If a single instance has failed to launch within 24 hours due to issues during the setup of Auto Scaling, the Auto Scaling group will not be automatically terminated. Instead, Auto Scaling will continue to attempt to launch instances based on the defined scaling policies.
Auto Scaling is designed to be resilient, and it will continue to monitor the health of the instances and make additional attempts to launch new instances to meet the defined scaling conditions. The failure to launch a single instance does not typically trigger the termination of the Auto Scaling group itself.
The exact behavior can vary depending on your Auto Scaling configuration, but typically, if an instance fails to launch due to issues, Auto Scaling will continue to retry the launch process based on your defined scaling policies until it reaches the maximum number of retries or until the issues causing the failures are resolved.
So, option "Auto Scaling will remove the scaling process" is not accurate, and the Auto Scaling group will not be terminated due to a single instance failing to launch.
注、ChatGPTの説明が自然で納得感が高い。
Q94. Point out the wrong statement.
l Amazon Machine Instances are sized at various levels and rented on a computing/hour basis
l The metrics obtained by CloudWatch may be used to enable a feature called Auto Scaling
l A number of tools are used to support EC2 services
l None of the mentioned
Q95. In terms of Amazon VPC design, a VPC with a single public subnet is ideal for which of the following application designs?
l A single-tier application
l A serverless application
l A microservice application
l A multi-tier application
ChatGPT also adds ..
A VPC (Virtual Private Cloud) with a single public subnet is more suitable for a single-tier application.
In VPC design, the "tier" refers to the layers of an application. A single-tier application typically involves a straightforward architecture where the entire application runs in a single layer without separation or division. This type of application is often simple, with both the application and database residing together.
A single public subnet in a VPC allows resources within that subnet to have direct access to the internet. This setup is ideal for a single-tier application where the application doesn’t require multiple layers of separation, such as front-end, back-end, and database layers, and instead can function adequately with a single public-facing layer.
For more complex applications such as multi-tier applications, serverless applications, or microservices, a VPC design typically involves multiple subnets, both public and private, with different layers of the application separated into different subnets for security, scalability, and manageability reasons. These designs often use a combination of public and private subnets, allowing for more controlled access and segregation of services.
Therefore, a VPC with a single public subnet is more suited for a single-tier application where the application and its associated components are not divided into separate layers.
Q96. If you stop and restart an EC2 instance, does it retain its private IP address?
l Yes, the instance retains its private IP addresses
l No, it retains only the public IP addresses
l No, it retains only the Elastic IP addresses
l No, it does not retain its private IP addresses
ChatGPT also adds ..
When you stop and restart an EC2 instance in Amazon Web Services, it retains its private IP address.
The private IP address of an EC2 instance is associated with the instance itself, not the state it's in. When you stop an EC2 instance and start it again, the private IP address remains the same unless you specifically terminate the instance.
However, it's important to note that the public IP address is subject to change upon each stop and start, unless you have an Elastic IP address attached. Elastic IP addresses are static and can be reassociated with an instance after a stop/start, maintaining a consistent public IP address.
But in the case of the private IP address, stopping and starting the instance does not affect it - the instance will retain the same private IP address it had before the stop.
Q97. All the Amazon EC2 instances you launch into a nondefault VPC are _ by default.
l stateless
l protected
l public
l private
Q98. When you launch an instance into a dedicated-tenancy VPC, what happens?
l Your instance is automatically a Dedicated instance, regardless of the instance's specific tenancy attribute
l You receive an error message notifying you that you must set your instance's tenancy attribute to dedicated
l Your instance launch fails, but AWS prompts you to launch a new one with the tenancy attribute set to dedicated
l Your instance launch fails immediately
Q99. Use the _ protocol in a VPC security group to communicate with a DB instance.
l SSH
l SSL
l TCP
l UDP
過去問
https://github.com/Ebazhanov/
No comments:
Post a Comment