{"id":17260,"date":"2026-09-21T07:24:10","date_gmt":"2026-09-21T07:24:10","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=17260"},"modified":"2026-09-21T07:24:10","modified_gmt":"2026-09-21T07:24:10","slug":"amazon-aws-certified-security-specialty-scs-c02-practice-test-questions-and-exam-dumps-part14-q261-280","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/amazon-aws-certified-security-specialty-scs-c02-practice-test-questions-and-exam-dumps-part14-q261-280\/","title":{"rendered":"Amazon AWS Certified Security &#8211; Specialty SCS-C02 Practice Test Questions and Exam Dumps Part14 Q261-280"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/aws-certified-security-specialty-scs-c02-exam-dumps\"><b>Amazon AWS Certified Security &#8211; Specialty SCS-C02 Exam Dumps<\/b><\/a><b> and Practice Test Dumps<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 261<\/b><\/h3>\n<p><b>Which IAM feature lets administrators define reusable access assignments for workforce users?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IAM user groups<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource policies<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Permission sets<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Inline role policies<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">IAM Identity Center permission sets provide reusable permission definitions that administrators can assign to workforce users or groups when granting access to AWS accounts. A permission set can contain AWS managed policies, customer managed policies, or other supported permission configurations. When assigned, IAM Identity Center provisions the corresponding permissions into the target account. IAM user groups are associated with traditional IAM users, resource policies control access to specific resources, and inline policies are directly attached to individual identities. Permission sets are particularly useful in multi-account environments because they provide a centralized and repeatable way to manage workforce access.<\/span><\/p>\n<h3><b>Question 262<\/b><\/h3>\n<p><b>Which AWS feature helps prevent accidental exposure of an S3 bucket through ACLs?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Object Ownership<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 Inventory<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replication Rules<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage Lens<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">S3 Object Ownership can disable access control lists by using the Bucket owner enforced setting. With ACLs disabled, the bucket owner automatically owns objects uploaded to the bucket, and access can be managed through IAM policies and bucket policies instead of object ACLs. This reduces complexity and helps prevent security problems caused by inconsistent object ownership or ACL configurations. S3 Inventory provides object reports, replication rules control data copies, and Storage Lens provides storage-usage visibility. Object Ownership is therefore the relevant S3 capability when the goal is to simplify permissions and eliminate ACL-based exposure.<\/span><\/p>\n<h3><b>Question 263<\/b><\/h3>\n<p><b>Which AWS service can scan Lambda functions for software vulnerabilities?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Macie<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Inspector<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Audit Manager<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Security Hub<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Amazon Inspector can assess supported AWS Lambda functions for software vulnerabilities and generate findings for detected issues. This provides security teams with visibility into vulnerable dependencies and packages used by serverless applications. Inspector&#8217;s vulnerability assessment capabilities complement its supported scanning of other workload types, including EC2 instances and container images in Amazon ECR. Macie focuses on sensitive data discovery, Audit Manager collects compliance evidence, and Security Hub aggregates findings from security services. Inspector is therefore the service most directly associated with identifying vulnerabilities in supported Lambda workloads.<\/span><\/p>\n<h3><b>Question 264<\/b><\/h3>\n<p><b>Which control can restrict an S3 bucket policy to requests originating through a specific VPC endpoint?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 VersionId condition<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">aws condition<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">aws condition<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">s3 condition<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The aws:SourceVpce condition key can be used in supported resource policies to restrict access based on the VPC endpoint through which a request arrives. For example, an S3 bucket policy can deny access unless requests originate from an approved VPC endpoint. This is useful when an organization wants private application traffic to reach an S3 bucket only through designated network paths. The aws:SecureTransport condition evaluates whether transport encryption is being used, while object-related conditions evaluate object properties. SourceVpce specifically provides network-path-based access control.<\/span><\/p>\n<h3><b>Question 265<\/b><\/h3>\n<p><b>Which KMS operation schedules a customer managed key for removal?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DisableKey<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CancelKeyDeletion<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ScheduleKeyDeletion<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RetireGrant<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The KMS ScheduleKeyDeletion operation places a customer managed KMS key into a pending-deletion state for the configured waiting period. The key is not immediately destroyed, giving administrators an opportunity to cancel the deletion if it was requested accidentally. During the waiting period, the key cannot normally be used for cryptographic operations. DisableKey temporarily prevents key use without deleting the key, CancelKeyDeletion reverses a pending deletion, and RetireGrant concerns retiring a grant. ScheduleKeyDeletion is therefore the API operation specifically used to initiate KMS key deletion.<\/span><\/p>\n<h3><b>Question 266<\/b><\/h3>\n<p><b>Which KMS action can reverse a key that is awaiting deletion?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CancelKeyDeletion<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EnableKeyRotation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RetireGrant<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CreateAlias<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">CancelKeyDeletion can cancel a KMS key deletion that is still in the pending-deletion period. This provides an important recovery mechanism if administrators discover that a key was scheduled for deletion unintentionally. Once a key has actually been deleted, recovery is not available through this operation. EnableKeyRotation controls key rotation, RetireGrant removes a grant&#8217;s authorization relationship, and CreateAlias creates a friendly reference to a key. The ability to cancel scheduled deletion is especially important because applications may depend on existing ciphertext that requires the key for future decryption.<\/span><\/p>\n<h3><b>Question 267<\/b><\/h3>\n<p><b>Which IAM policy type is evaluated for a resource rather than an identity?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Identity-based policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Permissions boundary<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource-based policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Session policy<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Resource-based policies are attached to supported AWS resources and specify which principals can access those resources and what actions they may perform. Examples include S3 bucket policies, KMS key policies, and certain other service-specific resource policies. Identity-based policies are attached to users, groups, or roles, while permissions boundaries limit the maximum permissions an identity can receive. Session policies can further restrict permissions during a temporary session. Resource-based policies are particularly useful when access decisions need to be defined directly at the protected resource.<\/span><\/p>\n<h3><b>Question 268<\/b><\/h3>\n<p><b>Which STS capability lets an application request temporary credentials for a role?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AssumeRole<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GetCallerIdentity<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DecodeAuthorizationMessage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GetFederationToken<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS STS AssumeRole allows a trusted principal to obtain temporary security credentials for an IAM role. The resulting credentials include an access key ID, secret access key, and session token and are valid only for the configured session duration. AssumeRole is widely used for cross-account access, workload identity, and temporary administrative sessions. GetCallerIdentity returns information about the current caller, DecodeAuthorizationMessage helps decode certain authorization failure messages, and GetFederationToken provides temporary credentials under a different federation model. AssumeRole is the standard mechanism for obtaining temporary credentials associated with an IAM role.<\/span><\/p>\n<h3><b>Question 269<\/b><\/h3>\n<p><b>Which IAM mechanism can require a request to originate from a specific AWS Region?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PrincipalOrgID<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">aws<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">aws<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">aws<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The aws:RequestedRegion global condition key can be used in IAM policies to restrict API requests according to the AWS Region targeted by the request. Organizations can use this condition to prevent identities from performing certain actions outside approved Regions. This can support data-residency requirements, governance standards, and regional deployment strategies. PrincipalOrgID evaluates whether the principal belongs to a specified AWS Organization, PrincipalType identifies the principal type, and UserId relates to the calling identity. RequestedRegion is the condition key specifically designed for evaluating the target Region of an AWS request.<\/span><\/p>\n<h3><b>Question 270<\/b><\/h3>\n<p><b>Which Organizations policy can limit actions across member accounts?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IAM policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SCP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Session policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bucket policy<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Service Control Policies, or SCPs, are AWS Organizations policies that establish permission guardrails for accounts within an organization or organizational unit. An SCP does not grant permissions by itself. Instead, it defines the maximum available permissions that identities in affected accounts can use when combined with applicable identity and resource policies. This makes SCPs useful for centrally preventing actions such as disabling security controls or using unsupported Regions. IAM policies grant permissions to identities, session policies restrict temporary sessions, and bucket policies control access to S3 resources. SCPs provide organization-level permission boundaries.<\/span><\/p>\n<h3><b>Question 271<\/b><\/h3>\n<p><b>Which condition key can restrict access to principals belonging to an AWS Organization?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">aws<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">aws<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">aws<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">aws<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The aws:PrincipalOrgID global condition key can be used in supported resource policies to restrict access to principals that belong to a specified AWS Organization. This is useful for centralized resource sharing where an organization wants to permit access from its own member accounts while excluding unrelated external accounts. SourceIp evaluates the requester&#8217;s source IP address, VpcSourceIp can evaluate certain VPC-originated request contexts, and CalledVia provides information about service-mediated requests. PrincipalOrgID is specifically intended to establish an organization-based trust condition.<\/span><\/p>\n<h3><b>Question 272<\/b><\/h3>\n<p><b>Which AWS service helps detect unintended resource sharing outside an organization?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Shield<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Backup<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IAM Access Analyzer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon CloudFront<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">IAM Access Analyzer can analyze resource-based policies and identify external access that may not be intended. It can help security teams discover resources that are accessible from outside an organization or account boundary and investigate whether that access is justified. This capability is useful for maintaining least privilege and reducing accidental data exposure. Shield protects against DDoS attacks, Backup protects recovery data, and CloudFront delivers content through edge locations. Access Analyzer is therefore the relevant service for analyzing resource-sharing relationships and identifying potentially unintended external access.<\/span><\/p>\n<h3><b>Question 273<\/b><\/h3>\n<p><b>Which S3 feature preserves previous object versions after an overwrite?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Versioning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lifecycle expiration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transfer Acceleration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Inventory configuration<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">S3 Versioning maintains multiple versions of an object in the same bucket. When an object is overwritten or deleted, previous versions can remain available instead of being immediately lost. This provides an important recovery mechanism for accidental modifications and deletions. Versioning is also commonly combined with Object Lock and replication for stronger data-protection architectures. Lifecycle rules can manage old versions, Transfer Acceleration improves transfer performance, and Inventory provides object metadata reports. Versioning specifically provides the historical object versions that allow organizations to recover earlier copies of data.<\/span><\/p>\n<h3><b>Question 274<\/b><\/h3>\n<p><b>Which S3 Object Lock mode allows authorized users to bypass governance retention?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Compliance mode<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Governance mode<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Legal hold mode<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Versioning mode<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">S3 Object Lock Governance mode protects objects from modification or deletion during a retention period while allowing specially authorized users to bypass the retention controls. This provides strong protection while retaining administrative flexibility for approved personnel. Compliance mode is stricter because protected versions cannot be overwritten or deleted during the retention period even by users with elevated permissions. Legal holds provide indefinite protection until explicitly removed but are not a retention mode themselves. Versioning is an S3 data-management feature rather than an Object Lock mode. Governance mode is therefore the correct choice for controlled administrative bypass.<\/span><\/p>\n<h3><b>Question 275<\/b><\/h3>\n<p><b>Which CloudFront control restricts direct access to an S3 origin?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Origin Access Control<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Signed cookie<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cache policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Response headers policy<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">CloudFront Origin Access Control, or OAC, allows CloudFront to securely access an Amazon S3 origin while the bucket policy can restrict direct access from unauthorized sources. OAC supports signing requests to the S3 origin and is the recommended mechanism for many modern CloudFront-to-S3 architectures. Signed cookies control viewer access to private content, cache policies determine caching behavior, and response headers policies modify HTTP response headers. OAC specifically addresses the origin-access relationship between CloudFront and S3, helping prevent users from bypassing CloudFront and accessing the bucket directly.<\/span><\/p>\n<h3><b>Question 276<\/b><\/h3>\n<p><b>Which AWS service can inspect network traffic using stateful and stateless rules?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon GuardDuty<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Network Firewall<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS WAF<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Shield<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS Network Firewall is a managed network firewall service that supports both stateless and stateful rule groups. Stateless rules can make filtering decisions independently for each packet, while stateful rules can evaluate traffic with connection context and more advanced inspection capabilities. AWS WAF focuses on web application traffic such as HTTP and HTTPS requests, Shield provides DDoS protection, and GuardDuty detects suspicious activity. Network Firewall is therefore the service designed for centralized inspection and filtering of network traffic at the VPC level using both stateless and stateful controls.<\/span><\/p>\n<h3><b>Question 277<\/b><\/h3>\n<p><b>Which AWS service can enforce security policies on resources created in new accounts?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Control Tower<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Macie<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS CloudTrail<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Inspector<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS Control Tower helps establish governance for newly created and existing accounts in a multi-account AWS environment. It can apply organizational controls and guardrails intended to maintain consistent security and compliance requirements across governed accounts. This is useful when organizations want newly provisioned accounts to inherit standardized governance rather than relying on administrators to configure every security control manually. Macie focuses on sensitive data, CloudTrail records AWS activity, and Inspector evaluates supported workloads for vulnerabilities. Control Tower is therefore relevant when account provisioning and centralized governance are part of the security requirement.<\/span><\/p>\n<h3><b>Question 278<\/b><\/h3>\n<p><b>Which service can encrypt and protect a database password used by an application?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Route 53<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Secrets Manager<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Inspector<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Artifact<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS Secrets Manager provides secure storage for database passwords and other sensitive application credentials. Applications can retrieve secrets at runtime through authenticated API calls rather than embedding passwords directly in source code or configuration files. Secrets Manager also supports rotation workflows for supported use cases, helping organizations reduce reliance on long-lived credentials. Route 53 manages DNS, Inspector performs vulnerability assessment, and Artifact provides compliance documentation. Secrets Manager is therefore appropriate when an application needs centralized, encrypted storage and controlled retrieval of a database password or similar sensitive credential.<\/span><\/p>\n<h3><b>Question 279<\/b><\/h3>\n<p><b>Which AWS service records resource configuration history for supported resources?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Config<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Security Hub<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Detective<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Artifact<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS Config records configuration information for supported AWS resources and can maintain configuration history over time. This allows administrators to investigate how resource settings changed and evaluate resources against compliance rules. Configuration history can be useful during security investigations because it helps establish when a security-sensitive configuration changed and what the previous state was. Security Hub centralizes findings, Detective supports investigation of security activity, and Artifact provides compliance documentation. AWS Config is specifically designed to provide resource configuration visibility and historical tracking.<\/span><\/p>\n<h3><b>Question 280<\/b><\/h3>\n<p><b>Which AWS capability helps preserve forensic evidence by preventing backup deletion?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 Transfer Acceleration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Backup Vault Lock<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CloudFront caching<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route 53 Resolver<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS Backup Vault Lock can help protect recovery points from deletion or retention reduction according to configured retention controls. This is valuable for forensic and incident-response scenarios because backup copies can provide preserved versions of systems and data after a security incident. Strong retention controls can reduce the possibility that an attacker who compromises administrative credentials will immediately destroy recovery evidence. Transfer Acceleration concerns S3 data transfer, CloudFront caching concerns content delivery, and Route 53 Resolver provides DNS resolution. Backup Vault Lock directly supports protected, retention-controlled backup storage.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Amazon AWS Certified Security &#8211; Specialty SCS-C02 Exam Dumps and Practice Test Dumps &nbsp; Question 261 Which IAM feature lets administrators define reusable access assignments for workforce users? IAM user groups Resource policies Permission sets Inline role policies Correct Answer: 4 Explanation: IAM Identity Center permission sets provide reusable permission definitions that administrators [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/17260"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=17260"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/17260\/revisions"}],"predecessor-version":[{"id":17261,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/17260\/revisions\/17261"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=17260"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=17260"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=17260"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}