{"id":17258,"date":"2026-09-21T07:23:51","date_gmt":"2026-09-21T07:23:51","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=17258"},"modified":"2026-09-21T07:23:51","modified_gmt":"2026-09-21T07:23:51","slug":"amazon-aws-certified-security-specialty-scs-c02-practice-test-questions-and-exam-dumps-part13-q241-260","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/amazon-aws-certified-security-specialty-scs-c02-practice-test-questions-and-exam-dumps-part13-q241-260\/","title":{"rendered":"Amazon AWS Certified Security &#8211; Specialty SCS-C02 Practice Test Questions and Exam Dumps Part13 Q241-260"},"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 241<\/b><\/h3>\n<p><b>Which IAM credential type is intended for applications running on AWS resources?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Root account password<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IAM access key<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IAM role credentials<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Security group token<\/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 roles provide temporary security credentials that applications running on AWS resources can use to access other AWS services. For example, an EC2 instance can obtain credentials through an attached instance role rather than storing permanent access keys on the server. Temporary credentials reduce the risk associated with long-lived secrets and support better credential lifecycle management. Access keys are long-term programmatic credentials when used as standard IAM user credentials. Root credentials should not be used by applications, while security groups control network traffic rather than provide authentication credentials. IAM roles are therefore the preferred mechanism for granting AWS workloads temporary service permissions.<\/span><\/p>\n<h3><b>Question 242<\/b><\/h3>\n<p><b>Which STS option identifies the original caller when temporary credentials are used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SourceIdentity<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RoleAlias<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">KeyReference<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SessionBoundary<\/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 STS source identity allows an identity to pass identifying information when assuming a role. The source identity can then help administrators trace actions performed with temporary credentials back to the original caller. This is particularly valuable for auditing and incident investigations involving federated users or cross-account role assumptions. The information can appear in CloudTrail records, providing additional context about who initiated activity. Role aliases and key references are not STS mechanisms for preserving caller attribution, while a session boundary is not an AWS feature that identifies the originating principal.<\/span><\/p>\n<h3><b>Question 243<\/b><\/h3>\n<p><b>Which IAM policy element restricts access based on request context?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Effect<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Condition<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Action<\/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 Condition element in an IAM policy allows access decisions to depend on specific request attributes or contextual information. Conditions can evaluate factors such as source IP address, requested Region, principal tags, MFA usage, secure transport, or other supported condition keys. This provides a way to make permissions more precise than simply allowing an action on a resource. The Action element identifies permitted or denied API operations, Resource specifies the affected resources, and Effect determines whether the statement allows or denies access. Condition is therefore the policy element used for contextual access restrictions.<\/span><\/p>\n<h3><b>Question 244<\/b><\/h3>\n<p><b>Which mechanism can require MFA before an IAM role is assumed?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource tag<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MFA condition key<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">KMS grant<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPC endpoint route<\/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;\">IAM policies can use the aws:MultiFactorAuthPresent condition key to require multi-factor authentication for supported requests. For role assumption, administrators can incorporate an MFA condition into the role&#8217;s trust policy so that the principal must authenticate with MFA before receiving temporary role credentials. This is useful for sensitive administrative roles where an additional authentication factor is required. Resource tags provide metadata, KMS grants delegate cryptographic permissions, and VPC endpoint routes concern network connectivity. The MFA condition key specifically enables identity policies to enforce authentication context requirements.<\/span><\/p>\n<h3><b>Question 245<\/b><\/h3>\n<p><b>Which AWS service provides managed hardware security modules for dedicated cryptographic processing?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS CloudHSM<\/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 Config<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Detective<\/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 CloudHSM provides dedicated hardware security modules that allow customers to generate, store, and use cryptographic keys within hardware designed for secure key operations. Unlike fully managed KMS key storage, CloudHSM gives organizations more direct control over the HSM environment and cryptographic operations. It can be useful when regulatory or architectural requirements call for dedicated hardware-backed key management. Macie focuses on sensitive data discovery, Config evaluates resource configurations, and Detective supports security investigations. CloudHSM is therefore the appropriate choice when an organization specifically requires dedicated HSM infrastructure for cryptographic workloads.<\/span><\/p>\n<h3><b>Question 246<\/b><\/h3>\n<p><b>Which AWS technology isolates sensitive computation inside a hardware-based environment?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Nitro Enclaves<\/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 Firewall Manager<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CloudTrail Lake<\/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 Nitro Enclaves provide isolated compute environments designed to protect sensitive data and applications from unauthorized access by the parent EC2 instance. Enclaves use the Nitro system to create isolated environments without persistent storage, networking, or direct administrative access from the parent instance. They can be useful for sensitive workloads such as processing confidential information or cryptographic operations. Inspector scans workloads for vulnerabilities, Firewall Manager manages supported security policies, and CloudTrail Lake analyzes activity records. Nitro Enclaves specifically address the need for isolated processing of highly sensitive workloads.<\/span><\/p>\n<h3><b>Question 247<\/b><\/h3>\n<p><b>Which VPC feature provides private connectivity to AWS services without using an internet gateway?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Internet gateway<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">NAT gateway<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPC endpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Elastic IP address<\/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;\">VPC endpoints allow resources inside a VPC to privately access supported AWS services without requiring traffic to traverse an internet gateway. Depending on the endpoint type, connectivity can use private IP addresses or AWS PrivateLink. Endpoint policies can also provide additional control over which actions or resources are accessible through the endpoint. An internet gateway provides internet connectivity, a NAT gateway allows private resources to reach external destinations, and an Elastic IP is a public IPv4 address. VPC endpoints are therefore appropriate when applications need private service connectivity while reducing exposure to public network paths.<\/span><\/p>\n<h3><b>Question 248<\/b><\/h3>\n<p><b>Which VPC endpoint type uses AWS PrivateLink to connect privately to supported services?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Gateway endpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Interface endpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route-table endpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transit endpoint<\/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;\">Interface VPC endpoints use AWS PrivateLink to establish private connectivity between a VPC and supported AWS services or endpoint services. They create elastic network interfaces within selected subnets and use private IP addresses for communication. Security groups can control traffic to these interfaces, providing another layer of network access control. Gateway endpoints are commonly used for services such as Amazon S3 and DynamoDB and are configured through route tables. The interface endpoint model is specifically associated with PrivateLink-based private connectivity through elastic network interfaces.<\/span><\/p>\n<h3><b>Question 249<\/b><\/h3>\n<p><b>Which AWS service provides DNS query filtering for VPC workloads?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route 53 Resolver DNS Firewall<\/span><\/li>\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;\">Amazon Inspector<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Private CA<\/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;\">Route 53 Resolver DNS Firewall allows organizations to control and filter DNS queries originating from VPC resources. Administrators can create rule groups containing domain lists and determine whether matching queries should be allowed or blocked. This can help prevent workloads from resolving domains associated with known malicious activity or destinations that violate organizational policies. AWS Shield focuses on DDoS protection, Inspector identifies vulnerabilities, and Private CA manages private certificates. DNS Firewall operates specifically at the DNS-resolution layer, providing a preventive control for outbound domain lookups from VPC environments.<\/span><\/p>\n<h3><b>Question 250<\/b><\/h3>\n<p><b>Which Network Firewall rule group type evaluates traffic using stateful inspection?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stateless rule group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stateful rule group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route policy group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Endpoint policy group<\/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 Network Firewall supports stateful rule groups that inspect network traffic while maintaining context about connections. Stateful rules can evaluate traffic using more advanced inspection logic, including Suricata-compatible rules for supported use cases. Stateless rule groups evaluate packets independently without maintaining connection state and are useful for simpler filtering decisions. Route policies and endpoint policies are not Network Firewall rule-group types. Stateful inspection is particularly valuable when security controls need to understand traffic in the context of established network connections rather than examining each packet in isolation.<\/span><\/p>\n<h3><b>Question 251<\/b><\/h3>\n<p><b>Which AWS service centrally distributes supported security policies across accounts and resources?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Firewall Manager<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon ECR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Artifact<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon S3 Inventory<\/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 Firewall Manager helps security administrators centrally configure and manage supported firewall policies across multiple AWS accounts and resources. It integrates with AWS Organizations and can enforce consistent security controls throughout an organization&#8217;s environment. This centralized model is valuable when individual application teams should not independently determine the baseline firewall posture. ECR manages container images, Artifact provides compliance documentation, and S3 Inventory reports object information. Firewall Manager is specifically designed to reduce policy drift and maintain consistent supported security protections across an organization&#8217;s AWS accounts.<\/span><\/p>\n<h3><b>Question 252<\/b><\/h3>\n<p><b>Which S3 feature can reduce AWS KMS request volume for SSE-KMS objects?<\/b><\/p>\n<ol>\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;\">S3 Batch Operations<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 Bucket Keys<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 Object Lambda<\/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;\">S3 Bucket Keys can reduce the number of requests made to AWS KMS when S3 objects are encrypted using SSE-KMS. Instead of making a separate KMS request for every object encryption operation, S3 can use a bucket-level key hierarchy to reduce direct interaction with KMS. This can lower KMS request costs and reduce request volume while maintaining encryption through the configured KMS key. Inventory produces object reports, Batch Operations performs bulk actions, and Object Lambda modifies retrieved data through Lambda functions. Bucket Keys specifically address efficiency when using SSE-KMS encryption at scale.<\/span><\/p>\n<h3><b>Question 253<\/b><\/h3>\n<p><b>Which S3 capability restricts access to objects through named application endpoints?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 Access Points<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 Glacier Vaults<\/span><\/li>\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;\">S3 Inventory Reports<\/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 Access Points provide named network endpoints with their own access policies for applications or groups that need access to a shared S3 bucket. Each access point can be configured for a particular use case, allowing administrators to avoid placing every application&#8217;s permissions into one complex bucket policy. This approach can simplify management of large shared datasets. Transfer Acceleration is intended to improve long-distance upload and download performance, while Inventory Reports provide object metadata. Access Points specifically address the security and management challenge of providing separate controlled access paths to a common bucket.<\/span><\/p>\n<h3><b>Question 254<\/b><\/h3>\n<p><b>Which S3 control prevents public access through multiple account-level and bucket-level settings?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Object Lock<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Block Public Access<\/span><\/li>\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;\">Replication Time Control<\/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;\">Amazon S3 Block Public Access provides centralized controls that help prevent buckets and objects from becoming publicly accessible through common ACL and bucket-policy configurations. The controls can be applied at the account, bucket, or access-point level, allowing organizations to establish broad safeguards against accidental public exposure. Object Lock focuses on immutability and retention, Versioning preserves multiple object versions, and Replication Time Control concerns replication performance objectives. Block Public Access is therefore the appropriate control when the primary requirement is preventing unintended public access to S3 data.<\/span><\/p>\n<h3><b>Question 255<\/b><\/h3>\n<p><b>Which CloudTrail option helps detect modification or deletion of log files?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Log file validation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Event selector<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Insight selector<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Trail alias<\/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;\">CloudTrail log file validation uses digital signatures and digest files to help determine whether CloudTrail log files have been modified or deleted after delivery. This provides an integrity-checking mechanism that is useful when logs are required for security investigations, compliance, or forensic analysis. Event selectors determine which events a trail records, while CloudTrail Insights identifies unusual API activity patterns. A trail alias is not the mechanism used for validating log integrity. Organizations handling security-sensitive audit records can use log validation to strengthen confidence that collected CloudTrail files remain unchanged.<\/span><\/p>\n<h3><b>Question 256<\/b><\/h3>\n<p><b>Which CloudTrail event category records API activity involving individual S3 objects?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Management events<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data events<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Billing events<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Organization events<\/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;\">CloudTrail data events can record operations involving specific data resources, such as S3 object-level API activity. Examples include object reads and writes, depending on the configured event selectors or advanced event selectors. Management events instead record control-plane operations such as creating, modifying, or deleting AWS resources. Billing and organization events are not the CloudTrail categories used to capture S3 object-level API operations. Enabling appropriate data-event logging is important when security teams need visibility into access to individual objects rather than only changes made to the S3 bucket itself.<\/span><\/p>\n<h3><b>Question 257<\/b><\/h3>\n<p><b>Which AWS service can detect unusual API behavior using CloudTrail-related activity?<\/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 Artifact<\/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;\">Amazon EFS<\/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;\">Amazon GuardDuty analyzes supported AWS activity and other security data sources to identify suspicious behavior and potential threats. Its findings can include unusual API activity associated with compromised credentials or potentially malicious behavior. GuardDuty is designed for threat detection rather than simply storing audit records. Artifact supplies compliance documents, Backup provides data protection and recovery capabilities, and EFS provides managed file storage. When the requirement is to detect suspicious patterns in AWS account activity rather than merely record those activities, GuardDuty provides the relevant managed security capability.<\/span><\/p>\n<h3><b>Question 258<\/b><\/h3>\n<p><b>Which AWS service continuously evaluates supported workloads for software vulnerabilities?<\/b><\/p>\n<ol>\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;\">Amazon Route 53<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Organizations<\/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;\">Amazon Inspector continuously assesses supported AWS workloads for software vulnerabilities and exposure conditions. Depending on the supported resource type, it can evaluate EC2 instances, container images in Amazon ECR, and Lambda functions. Findings can identify vulnerable packages or other security issues that require remediation. Audit Manager focuses on collecting compliance evidence, Route 53 provides DNS services, and Organizations manages accounts and organizational policies. Inspector is therefore the service intended for automated vulnerability assessment of supported AWS compute and application resources.<\/span><\/p>\n<h3><b>Question 259<\/b><\/h3>\n<p><b>Which AWS Backup feature can enforce a retention policy that administrators cannot shorten?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Backup Vault Lock<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Backup plan tag<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Recovery point label<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Backup dashboard<\/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 Backup Vault Lock can help enforce retention controls on recovery points stored in a backup vault. When configured appropriately, Vault Lock supports a governance model designed to prevent protected backups from being deleted or retention periods from being reduced before the configured minimum retention requirements are satisfied. This provides stronger protection against accidental deletion and certain malicious actions affecting backups. Backup plans define how backups are created, tags help identify resources, and dashboards provide visibility. Vault Lock specifically addresses the immutability and retention-enforcement requirements of protected backup repositories.<\/span><\/p>\n<h3><b>Question 260<\/b><\/h3>\n<p><b>Which cross-account backup approach improves resilience against compromise of the source account?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Local backup copies only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cross-account backup copies<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary EBS volumes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unencrypted snapshots<\/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;\">Cross-account backup copies provide an additional security boundary by storing backup data in a separate AWS account from the original workload. This separation can reduce the impact of a compromise in the production account, particularly when the backup account has tightly restricted administrative access and additional retention protections. Keeping backups only in the source account leaves them more exposed to account-level destructive actions. Temporary EBS volumes are not a backup strategy, and unencrypted snapshots weaken data protection. A properly secured cross-account backup architecture therefore strengthens recovery capabilities during security incidents.<\/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 241 Which IAM credential type is intended for applications running on AWS resources? Root account password IAM access key IAM role credentials Security group token Correct Answer: 3 Explanation: IAM roles provide temporary security credentials that applications running [&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\/17258"}],"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=17258"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/17258\/revisions"}],"predecessor-version":[{"id":17259,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/17258\/revisions\/17259"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=17258"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=17258"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=17258"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}