AWS Certified Security – Specialty 1-10

表示モード
画像位置
文字位置
理解度の自動記録
STATUS FILTER

Choose confidence levels to display

Loading...
Q1AWS Certified Security Specialty
Show answer
Correct answer: A. Configure S3 Block Public Access for the entire AWS account.
Enabling S3 Block Public Access at the AWS account level is the recommended approach for protecting data with the least operational overhead.
When configured at the account level, it is automatically applied to all existing and newly created buckets and objects, collectively preventing exposure caused by misconfigured bucket policies or ACLs.
Per-object configuration (B) and disabling ACLs (C) require individual handling that is prone to omissions and actually increases operational overhead.
PrivateLink (D) is a mechanism related to the connection path and does not match the requirement of suppressing public access settings.
Being preventive and centrally manageable is the basis for the correct answer.
Blocking public access to your Amazon S3 storage (AWS official documentation)
Q2AWS Certified Security Specialty
Show answer
Correct answer: D. Use an SCP to deny all lambda:CreateFunctionUrlConfig and lambda:UpdateFunctionUrlConfig actions where the lambda:FunctionUrlAuthType condition key value is NONE.
Lambda function URLs have two authentication types: AWS_IAM (IAM authentication) and NONE (public).
NONE makes the function accessible to anyone, which poses a serious risk in a production environment.
By explicitly denying Create/UpdateFunctionUrlConfig where FunctionUrlAuthType is NONE via an SCP (service control policy), you can prevent the creation of unauthenticated functions across the entire organization without any effort on the developers’ part.
Option C (Allow), which permits AWS_IAM, still leaves room for creation via other permissions unless a Deny is in place, so it is insufficient as a preventive guardrail.
WAF (B) and CORS (A) are not means of enforcing the authentication type itself.
Security and auth model for Lambda function URLs (AWS official documentation)
Q3AWS Certified Security Specialty
Show answer
Correct answer: C. Configure the Amazon EBS volume attached to the suspicious EC2 instance so that it is not deleted on instance termination. Terminate the instance. Launch a new EC2 instance equipped with diagnostic tools in us-east-1a. Mount the EBS volume of the terminated instance to that new instance and investigate.
The fundamental principles of incident response are immediate containment, evidence preservation, and forensics in a safe environment.
Without logging in directly to the suspected compromised instance or installing additional tools, you preserve the EBS volume, then terminate the instance to immediately cut off the malicious communication.
By setting the volume to not be deleted on termination, the on-disk evidence is retained and can be analyzed by mounting it to a separate clean instance.
Options A and D, which log in and operate on the instance, risk contaminating the evidence.
WAF cannot be attached directly to EC2, so D itself is inappropriate.
B isolates via the network but keeps the instance running, making its containment weaker than C.
AWS Security Incident Response Guide (AWS official documentation)
Q4AWS Certified Security Specialty
Show answer
Correct answer: C. Add an interface-type VPC endpoint to the VPC to provide a route to the Secrets Manager endpoint.
Secrets Manager is a regional service that can be connected to privately via interface-type VPC endpoints built on AWS PrivateLink.
In a VPC with no internet route, an interface endpoint creates an ENI and a private IP within the subnet, allowing communication with Secrets Manager without going through the internet or a NAT, which makes it the most secure option.
A NAT gateway (A) and an internet gateway (D) send traffic out to the public internet, which violates the requirement.
Gateway-type endpoints (B) only support S3 and DynamoDB and cannot be used for Secrets Manager.
Using a Secrets Manager VPC endpoint (AWS official documentation)
Q5AWS Certified Security Specialty
Show answer
Correct answer: D. Attach the AWS managed policy CloudWatchAgentServerPolicy to the EC2 instance’s role.
The CloudWatch agent requires explicit IAM permissions to create log groups and log streams and to send log events.
The most common cause of failed log delivery by the agent is insufficient IAM permissions on the EC2 instance role, and attaching CloudWatchAgentServerPolicy grants the logs:CreateLogGroup, CreateLogStream, and PutLogEvents permissions, resolving the issue.
A trust policy defines the principals that can assume a role, so options A, B, and C, which add S3, Inspector, or CloudTrail to the trust policy, have a different meaning and do not meet this requirement.
Create IAM roles and users for use with the CloudWatch agent (AWS official documentation)
Q6AWS Certified Security Specialty
Show answer
Correct answer: A, D, E
Session Manager requires outbound HTTPS (port 443) communication from EC2 to the Systems Manager endpoints.
In a VPC with no internet route, you can connect securely without external exposure by creating an interface VPC endpoint for Systems Manager (D), allowing outbound port 443 in the EC2 security group (A), and allowing inbound port 443 from the VPC CIDR in the endpoint’s security group (E).
A key pair (C) is for SSH, so it is unnecessary and could compromise evidence due to the risk of a reboot.
An inbound rule for Session Manager itself (B) is unnecessary, and an endpoint for EC2 (F) does not apply to this connection requirement.
Creating VPC endpoints for Systems Manager (AWS official documentation)
Q7AWS Certified Security Specialty
Show answer
Correct answer: C. Create a key grant that allows the application team to use the KMS key, and retire the grant once access is no longer needed.
A KMS key grant is a mechanism that can grant temporary, fine-grained usage permissions without changing the key policy itself.
Grants can programmatically and dynamically grant and revoke permissions such as Encrypt, Decrypt, and GenerateDataKey, making them ideal for short-term access requirements and minimizing operational overhead.
Editing the key policy (B) involves the effort of changing and reverting it, and carries a high risk of misconfiguration.
Exporting key material (A) is not possible in KMS, and operating with imported keys (D) is a cumbersome procedure; both are excessive responses.
Grants in AWS KMS (AWS official documentation)
Q8AWS Certified Security Specialty
Show answer
Correct answer: A. Run the AWS IAM Access Analyzer policy generation feature against that IAM role.
The IAM Access Analyzer policy generation feature automatically generates a least-privilege policy based on actual usage history recorded in CloudTrail.
Because the role has been used for three months and sufficient CloudTrail history has accumulated, policy generation can create a policy that includes only the API actions and resources actually invoked, achieving least privilege with minimal effort.
Policy validation (B) only checks syntax and best practices and does not generate a least-privilege policy.
Manually searching logs (C) requires significant effort, and Trusted Advisor (D) is not suited for generating least-privilege policies.
IAM Access Analyzer policy generation (AWS official documentation)
Q9AWS Certified Security Specialty
Show answer
Correct answer: B. Change the attribute mappings in the IAM Identity Center trust relationship to match the information sent by the new IdP.
IAM Identity Center associates federated users with identities, groups, and permission sets through SAML assertions and attribute mappings.
When switching only the IdP without changing the underlying directory, updating the attribute mappings to match the new IdP’s assertions allows migration while maintaining the associations of existing users and groups.
Disabling existing users (A) is unnecessary and instead causes them to lose access.
Changing IAM role trust (C) is a matter of role-based access rather than IdP federation and does not apply.
Checking clock skew (D) is only for isolating connection failures and does not itself meet the requirement of switching the IdP.
Attribute mappings in IAM Identity Center (AWS official documentation)
Q10AWS Certified Security Specialty
Show answer
Correct answer: A. Set the security account as the delegated administrator account for Amazon Macie and AWS Security Hub. Enable and configure Macie, and publish the sensitive data findings to Security Hub.
Amazon Macie is a service specialized in the discovery, classification, and inventorying of sensitive data stored in S3.
Macie can be enabled organization-wide across AWS Organizations using the delegated administrator mechanism, and setting the security account as the delegated administrator for both Macie and Security Hub allows the findings to be aggregated in a single location.
Amazon Inspector does not perform sensitive data discovery for S3 (B and C), so it does not meet the requirement.
Trusted Advisor (C and D) is not an aggregation destination for sensitive data findings and does not match the requirement for centralized visibility.
Amazon Macie and AWS Organizations (AWS official documentation)